re created using regexp-opt fails in an org agenda command

this bug is strange because it appears as if regexp-opt is broken, but the only likely difference is an org upgrade via git clone. in an org agenda command, the same set of org todo kw works if a regexp was created using mapconcat, but not with regexp-opt. i expected that regexp-opt with 'words i

Re: Org-mode ASCII Export to support numbered references for links

you can also use inline footnotes.google[fn::https://google.com] which will be exported like you like as a kludge if there is noe. On 12/12/21, Samuel Wales wrote: > idk but you can put them in place using org-ascii-links-to-notes for a > dry effect. > > On 12/12/21, Husain Alshehhi wrote: >> Or

Re: Org-mode ASCII Export to support numbered references for links

idk but you can put them in place using org-ascii-links-to-notes for a dry effect. On 12/12/21, Husain Alshehhi wrote: > Org-mode's ascii export uses the link's description to create a reference to > it at the end of the document. For example, a link to google will look like > this: > > , > |

Org-mode ASCII Export to support numbered references for links

Org-mode's ascii export uses the link's description to create a reference to it at the end of the document. For example, a link to google will look like this: , | This is a [link to google]. | | [link to google] ` Is there a way to modify this behavior to using a

Video: Org for Non-Users

Hi all, A few months ago I finally understood why I have always found Org so difficult to learn, and I started to work on a way to use eev - a package that I wrote - to create notes on Org that would complement the official docs "exactly in the way that I needed". I recorded a video about that, an

Re: oc-biblatex and biblatex substyles

Aloha Nicolas, Nicolas Goaziou writes: "Thomas S. Dye" writes: IIUC, the map in 'org-cite-biblatex-styles' is correct for biblatex-chicago. biblatex-chicago introduces new LaTeX commands. Does that mean those can be ignored? If the goal is to support the styles and variants in org-ci

Re: oc-biblatex and biblatex substyles

"Thomas S. Dye" writes: > IIUC, the map in 'org-cite-biblatex-styles' is correct for > biblatex-chicago. biblatex-chicago introduces new LaTeX commands. Does that mean those can be ignored? Regards,

Re: oc-biblatex and biblatex substyles

Aloha Nicolas, Nicolas Goaziou writes: "Thomas S. Dye" writes: Hmm, I can't find 'org-cite-biblatex-styles' in main. Do you mean the map represented by the nested pcase in org-cite-biblatex-export-citation function, or something else? You need to update main. `org-cite-biblatex-styles' i

Re: oc-biblatex and biblatex substyles

"Thomas S. Dye" writes: > Hmm, I can't find 'org-cite-biblatex-styles' in main. > > Do you mean the map represented by the nested pcase in > org-cite-biblatex-export-citation function, or something else? You need to update main. `org-cite-biblatex-styles' is a recent addition to oc-biblatex.el.

Re: oc-biblatex and biblatex substyles

Aloha Nicolas, Nicolas Goaziou writes: Hello, "Thomas S. Dye" writes: Nicolas Goaziou writes: Another possibility it to write, e.g., "oc-biblatex-chicago.el" and define a new ‘biblatex-chicago’ export processor, re-using most functions from "oc-biblatex.el". It would probably only be

Re: oc-biblatex and biblatex substyles

Hello, "Thomas S. Dye" writes: > Nicolas Goaziou writes: > >> Another possibility it to write, e.g., "oc-biblatex-chicago.el" and >> define a new ‘biblatex-chicago’ export processor, re-using most >> functions from "oc-biblatex.el". It would probably only be necessary >> to >> re-define ‘org-ci