org-ref-cite

2021-07-27 Thread John Kitchin
Hi all,

I have a pretty complete working version of org-ref-cite now at
https://github.com/jkitchin/org-ref-cite. This is the evolution of what I
previously called oc-bibtex.

This set of cite processors focuses on using bibtex-completion with ivy for
insertion and actions, a hydra menu for following, and natbib + bibtex for
export.

it still requires running org-mode from a git repo, and is not yet on
MELPA, so if you just want to see it in action, here is an updated video:
https://www.youtube.com/watch?v=puZMxooyDms

If you see any issues, let me know at
https://github.com/jkitchin/org-ref-cite/issues.

Thanks everyone who made this new cite syntax possible!

John

---
Professor John Kitchin (he/him/his)
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu


Re: virtual-fill mode in mail buffers, with orgalist-mode, prefix is not considered when virtual-fill is on

2021-07-27 Thread Nicolas Goaziou
Hello,

Uwe Brauer  writes:

> Not sure whether this is off topic, but it concerns orgalist-mode:
>
> When I use virtual-fill-mode together with orgalist-mode in mail buffers:  
> When I turn virtual-auto-fill-mode off and auto-fill-mode on, the lists are 
> nicely filled as:
>
>
>
> 1. The first item blab bladnka bladnfkand adnfkaj kjkajdkfj ablkadf
>kj kajldjf adfkjaksdfjl
>
>
> While with auto-fill-mode off and visual-auto-fill-mode on the are displayed 
> as
>
> 1. The first item blab bladnka bladnfkand adnfkaj kjkajdkfj ablkadf 
> kj kajldjf adfkjaksdfjl
>
>
>
> So the prefix is not taken into account. Anybody seeing this and knows
> a solution?

Orgalist mode does not handle virtual indentation. Patches welcome,
however.

Regards,
-- 
Nicolas Goaziou



Re: [PATCH] [BUG] Bad fontification in full displayed links

2021-07-27 Thread Nicolas Goaziou
Hello,

Juan Manuel Macías  writes:

> You are right, I think that solution is much simpler. I attach a
> new patch and I have included your name in the commit message, for the
> suggestion. Thanks!

Applied. Thank you.

Regards,
-- 
Nicolas Goaziou



Re: Bug: duplicated \texttt in LaTeX export

2021-07-27 Thread Nicolas Goaziou
Hello,

Maxim Nikulin  writes:

> It seems, something goes wrong with LaTeX export at least in git master
>
>  >8 
>
> #+PROPERTY: header-args :eval never-export :exports code :results silent
>
> src_elisp{(delete-dups nil)}
>  8< 
>
> Export as LaTeX buffer:
>
>  \texttt{\texttt{(delete-dups nil)}}
>
> I see no reason why \texttt should be doubled this case. Expectation: e.g.
>
>  \texttt{(delete-dups nil)}

Fixed. Thank you.

Regards,
-- 
Nicolas Goaziou



Re: Bug: :match filter fails on columnview dblock when :maxlevel present [9.4.6 (9.4.6-gab9f2a @ /Users/pabfr/.emacs.d/elpa/org-9.4.6/)]

2021-07-27 Thread Nick Dokos
I have submitted a patch to allow both match and maxlevel to be specified:

https://orgmode.org/list/87h7h0w5nz@alphaville.usersys.redhat.com/

but it has not been reviewed, tested or merged yet. Maybe you can test it
and report? That should help move it forward.

-- 
Nick

"There are only two hard problems in computer science: cache
invalidation, naming things, and off-by-one errors." -Martin Fowler




Re: a repeater doesn't increment

2021-07-27 Thread Jude DaShiell
I couldn't figure a way to make the field columns work for this many
different items.


On Tue, 27 Jul 2021, Nick Dokos wrote:

> Jude DaShiell  writes:
>
> > What I'm trying to do is more complex than that.
> > * Reorder pills
> > ** TODO order hctz, lisinipril, metformin, provacol, claritin, Co-q10,
> >Deadline: <8-2-2021 +4w>
> > ** TODO order Colase
> >Deadline: <10-13-2021 +14w>
> > ** TODO order Turmerick
> >Deadline: <8-30-2021 +8w>
> >
> > On Thu, 22 Jul 2021, Nick Dokos wrote:
> >
> >> Jude DaShiell  writes:
> >>
> >> > Does enough material exist on werg tutorials that document how to get a
> >> > repeater operational?  That or maybe I don't understand repeaters.  Had
> >> > the repeater I tried to use worked correctly it would have advanced the
> >> > original date by 4 weeks when that date got copied down to another cell.
> >> > I selected the whole line including both verticals and perhaps this works
> >> > when only a time stamp is copied.
> >> >
> >> >> I am likely doing this wrong but will describe what has been done.
> >> >> I put an agenda time stamp into a field in test.org and add +4w to the 
> >> >> end
> >> >> of the time stamp inside the >.
> >> >> I get on the left of the field column on the vertical character and type
> >> >> control-space to set mark.
> >> >> I move to the end of the field on the > sign and type space and another
> >> >> vertical to close the column entry for that field.
> >> >> Next I do control-c+x+v and am told strings are copied to the kill ring.
> >> >> Next I move down one line and type control-y to yank those strings out 
> >> >> of
> >> >> the kill buffer and paste them on that line.
> >> >> When this is done, I expected the time stamp to increment by 4 weeks.
> >> >> What happened was the same information got copied down and it didn't
> >> >> increment.
> >> >> What am I doing wrong?
> >> >>
>
> I still don't understand: in your most recent response (at the top of this 
> thread)
> you are talking about headlines with DEADLINE added (which seems the right 
> approach
> to me: is there a problem with it?) But in your original mail, as well as in 
> the followup, you are
> taling about "field columns" and "vertical characters" and "cop[ying] down to 
> another cell",
> which seems to imply that you have an Org mode table somewhere.
>
> Maybe you can elaborate a bit?
>



Re: what would cause failure in template for org capture?

2021-07-27 Thread No Wayman



Thanks for doing the bisect.
I was in the process of doing it myself and comparing disassembled 
byte-code when I saw the patch had been pushed.
For anyone curious, this particular bug was a byte compilation 
error.
When byte-compiled, org-capture-fill-template was attempting to 
compare strings
via a jump-table-eq bytecode instruction instead of a 
jump-table-equal.


Resolved on Emacs master as of 
949dd41c31dab69f7a5067bba324c28bb2cfbf8e




Re: a repeater doesn't increment

2021-07-27 Thread Nick Dokos
Jude DaShiell  writes:

> What I'm trying to do is more complex than that.
> * Reorder pills
> ** TODO order hctz, lisinipril, metformin, provacol, claritin, Co-q10,
>Deadline: <8-2-2021 +4w>
> ** TODO order Colase
>Deadline: <10-13-2021 +14w>
> ** TODO order Turmerick
>Deadline: <8-30-2021 +8w>
>
> On Thu, 22 Jul 2021, Nick Dokos wrote:
>
>> Jude DaShiell  writes:
>>
>> > Does enough material exist on werg tutorials that document how to get a
>> > repeater operational?  That or maybe I don't understand repeaters.  Had
>> > the repeater I tried to use worked correctly it would have advanced the
>> > original date by 4 weeks when that date got copied down to another cell.
>> > I selected the whole line including both verticals and perhaps this works
>> > when only a time stamp is copied.
>> >
>> >> I am likely doing this wrong but will describe what has been done.
>> >> I put an agenda time stamp into a field in test.org and add +4w to the end
>> >> of the time stamp inside the >.
>> >> I get on the left of the field column on the vertical character and type
>> >> control-space to set mark.
>> >> I move to the end of the field on the > sign and type space and another
>> >> vertical to close the column entry for that field.
>> >> Next I do control-c+x+v and am told strings are copied to the kill ring.
>> >> Next I move down one line and type control-y to yank those strings out of
>> >> the kill buffer and paste them on that line.
>> >> When this is done, I expected the time stamp to increment by 4 weeks.
>> >> What happened was the same information got copied down and it didn't
>> >> increment.
>> >> What am I doing wrong?
>> >>

I still don't understand: in your most recent response (at the top of this 
thread)
you are talking about headlines with DEADLINE added (which seems the right 
approach
to me: is there a problem with it?) But in your original mail, as well as in 
the followup, you are
taling about "field columns" and "vertical characters" and "cop[ying] down to 
another cell",
which seems to imply that you have an Org mode table somewhere.

Maybe you can elaborate a bit?
-- 
Nick

"There are only two hard problems in computer science: cache
invalidation, naming things, and off-by-one errors." -Martin Fowler




Re: what would cause failure in template for org capture?

2021-07-27 Thread Gregor Zattler
Hi No, Eric,

* No Wayman  [2021-07-23; 23:03]:
>> from an earlier thread, I recall you mentioned you were using
>> native
>> compilation? This is almost certainly the cause of your problem.
>
> This does smell like a byte-compilation problem.
> Seems to be a failure with any interactive, single-character
> %-escaped patterns in a template string (e.g. %^g, %^C, %^t).
> I've narrowed it down to a call to pcase in
> `org-capture-fill-template'.
> As Eric mentions, the problem disappears if the function is
> re-evaluated/instrumented.
> I have disabled native compilation and the problem persists with
> just a freshly byte-compiled elc of org-capture.
> Tested this with the following recipe:
>
> 1. eval the following:
> (org-capture-fill-template "%^t") ;fails with `unrecognized
> template placeholder: %^t`
> 2. eval org-capture-fill-template's definition, and then re-eval
> the above. Works properly. User is prompted for a time.
> 3. byte compile org-capture-fill-template: (byte-compile
> #'org-capture-fill-template)
> 4. eval (org-capture-fill-template "%^t") ; error is back
>
>
> Running Emacs 28.0.50
> Repository revision: 903ecd7bea7d8f99a7dc84150728219283d79bf0
> Repository branch: master

this is now emacs bug 49746
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=49746

Because of No's email I did a git bisect and found a commit
which changes the byte compiler.

Ciao; Gregor
--
 -... --- .-. . -.. ..--.. ...-.-




Re: Dynamic block tables: adding prefix of "id:" to %ID

2021-07-27 Thread Ihor Radchenko
Karl Voit  writes:
> Thanks, this sounds clever and I think I understand the code.
> Although I would have preferred not to overwrite a function. I
> always have a fear that this leads to nasty side-effects with future
> updates.

That's not overwriting. org-columns-modify-value-for-display-function is
not a function, but a custom variable defaulting to nil. You have all
rights to set it to whatever you wish.

> Without deeper knowledge, I was astonished that C-h f
> org-columns-modify-value-for-display-function did not lead to a
> matching function and C-h v ... to a matching variable.

Hmm. You are right. This should be a bug. It happens because
org-colview.el is only loaded after you actually run column view or
corresponding dblock. Before that, Emacs is not aware about this
variable (unless you require org-colview manually in your config).

> When I applied the new change to update a table in a file of 71k
> lines of org, I had to cancel the process after over two hours
> without a result. Before the change, updating this table took
> roughly 20 minutes.

That's probably because the function I provided tries to compute the
description part of the link by querying the headline for each result.
You may get much better performance using the following version:

(defun yant/org-columns-custom-formatter (column-title value)
  "Format column values for columns with ID-LINK title as proper Org mode id: 
link."
  (pcase column-title
("ID-LINK"
 (format "[[id:%s]]" value))
(_ nil)))

Best,
Ihor



Re: Dynamic block tables: adding prefix of "id:" to %ID

2021-07-27 Thread Karl Voit
Hi Ihor,

* Ihor Radchenko  wrote:
> Karl Voit  writes:
>
>> I do have a dynamic block table like this:
>> ...
>> | NEXT| [0/0] proj bar | bar | :bar:project: |
>>
>> Is there a way to get the ID column with working ID links such as:
>> ...
>> | NEXT| [0/0] proj bar | id:bar | :bar:project: |
>
> You may customise org-columns-modify-value-for-display-function:
>
> (defun yant/org-columns-custom-formatter (column-title value)
>   "Format column values for columns with ID-LINK title as proper Org mode id: 
> link."
>   (pcase column-title
> ("ID-LINK"
>  (format "[[id:%s][%s]]"
>value
>(org-with-point-at (org-id-find value 'marker)
>(org-get-heading t t t t
> (_ nil)))
> (setq org-columns-modify-value-for-display-function 
> #'yant/org-columns-custom-formatter)
>
> Then, you can use the following dblock. Note that I renamed the column
> name to "ID-LINK"
>
> #+BEGIN: columnview :id global :match 
> "+project-focus/!+STARTED|+NEXT|+WAITING" :format "%TODO(State) %ITEM(What) 
> %ID(ID-LINK) %TAGS(Tags)"
> #+END:

Thanks, this sounds clever and I think I understand the code.
Although I would have preferred not to overwrite a function. I
always have a fear that this leads to nasty side-effects with future
updates.

Without deeper knowledge, I was astonished that C-h f
org-columns-modify-value-for-display-function did not lead to a
matching function and C-h v ... to a matching variable.

However, I set up following test file and it worked:

#+BEGIN: columnview :id global :match 
"+project+focus/!+STARTED|+NEXT|+WAITING" :format "%TODO(State) %ITEM(What) 
%ID(ID-LINK) %TAGS(Tags)"
| State | What   | ID-LINK| Tags|
|---+++-|
| NEXT  | [/] focus proj | [[id:2021-07-27-focus-proj][[/] focus proj]] | 
:focus:project: |
#+END:

* Test

** NEXT [/] focus proj  
 :focus:project:
:PROPERTIES:
:CREATED:  [2021-07-27 Tue 13:59]
:COOKIE_DATA: todo recursive
:ID:   2021-07-27-focus-proj
:END:

** NEXT [/] non-focus proj  
:project:
:PROPERTIES:
:CREATED:  [2021-07-27 Tue 13:59]
:COOKIE_DATA: todo recursive
:ID:   2021-07-27-non-focus-proj
:END:

When I applied the new change to update a table in a file of 71k
lines of org, I had to cancel the process after over two hours
without a result. Before the change, updating this table took
roughly 20 minutes.

Therefore, this somehow makes a poor performance even worse.

-- 
get mail|git|SVN|photos|postings|SMS|phonecalls|RSS|CSV|XML into Org-mode:
   > get Memacs from https://github.com/novoid/Memacs <
Personal Information Management > http://Karl-Voit.at/tags/pim/
Emacs-related > http://Karl-Voit.at/tags/emacs/




Re: [BUG] Citations in tables are not exported

2021-07-27 Thread Matt Price
re: captions, a quick hack is to change line 1373 of oc.el to

((memq type '(nil paragraph keyword)))

This makes my life quite a bit easier.

No doubt this is a bit too broad, though I am not entirely clear on why
there are any restrictions at all on inserting cites.

On Sun, Jul 18, 2021 at 7:29 PM John Kitchin 
wrote:

> I also see this behavior. I think this should be considered a bug, it is
> pretty common to see citations in a table cell.
>
> Additionally, I cannot insert a citation in a caption that is above a
> table (or a figure), I get
> "user-error: Cannot insert a citation here". That should be considered a
> bug in org-cite--allowed-p  I think. It fails because in the caption the
> context is a table, and it has :post-affiliated item which causes
> org-cite--allowed-p  to return nil.
>
> If I put a citation in the caption anyway, it does seem to get exported
> correctly.
>
> I am not sure why the cites don't export inside the table cell though.
>
> Thanks,
>
> Timothy  writes:
>
> > Hi,
> >
> > I've just started playing with citations, but it seems that I've
> > stumbled across a bug where if the citation is in a table cell it will
> > be left "raw". See the following example
> >
> > #+begin_org
> > ,#+begin_src bibtex :tangle activedoc.bib
> > @article{SchulteActiveOrg,
> >  author={Schulte, Eric and Davison, Dan},
> >  journal={Computing in Science Engineering},
> >  title={Active Documents with Org-Mode},
> >  year={2011},
> >  volume={13},
> >  number={3},
> >  pages={66-73},
> >  doi={10.1109/MCSE.2011.41}}
> > ,#+end_src
> >
> > ,#+bibliography: activedoc.bib
> > ,#+print_bibliography:
> >
> > [cite/a:@SchulteActiveOrg]
> >
> > | [cite/a:@SchulteActiveOrg] |
> > #+end_org
> >
> > When exporting to ASCII, I see this:
> >
> > #+begin_example
> > Schulte, Eric, and Dan Davison. 2011. “Active Documents with Org-Mode.”
> > /Computing in Science Engineering/ 13 (3):66–73.
> >
> > (Schulte and Davison 2011)
> >
> > 
> >  [cite/a:@SchulteActiveOrg]
> > 
> > #+end_example
> >
> > I hope that's enough to go off.
>
>
> --
> Professor John Kitchin
> Doherty Hall A207F
> Department of Chemical Engineering
> Carnegie Mellon University
> Pittsburgh, PA 15213
> 412-268-7803
> @johnkitchin
> http://kitchingroup.cheme.cmu.edu
> Pronouns: he/him/his
>
>