Re: [O] mailto link for the #+email keyword: Suppressing backslash and braces "escaping" for latex exports

John Kitchin writes: > I posted this on your stack exchange question: > > #+latex_class: report > #+options: author:nil email:nil > #+latex_header: \author{Some user > \thanks{\href{mailto:b...@comp.org}{b...@comp.org}}} Perfect, thanks a lot John! Hmm, I'm asking now

Re: [O] Expose value-begin and value-end instead of just value in org-element API

Nicolas Goaziou writes: > Hello, > > John Kitchin writes: > >> +1 on this. >> >> I also have some janky code to do things like go to the beginning/end of >> the value in a src block. Here is my solution to mark the code in a src >> block. >> >> (defun

[O] Bug: Bulk re-scheduling to a relative offset doesn't work [9.1.6 (9.1.6-48-gfe7619-elpa @ c:/Users/micha/.emacs.d/elpa/org-20180212/)]

I previously asked a question about this on emacs-orgmode but it seems more likely that this is a bug. https://lists.gnu.org/archive/html/emacs-orgmode/2018-02/msg00183.html I am bulk re-scheduling items in an agenda view. I would like all the selected items to be re-scheduled to a year later

[O] Exploring picolisp

I'm looking at picolisp -- and wondering how it works, or better, why it doesn't really work work with babel. First problem, I couldn't get any form of picolisp to work in Emacs -- until I stopped starting Emacs with emacsclient -c -a '' which sets up my daemon first. Got abstruse error -- and

Re: [O] src-blocks with captions do not respect attr_latex :placement options

Nicolas Goaziou writes: > Hello, > > John Kitchin writes: > >> A block like this: >> >> #+attr_latex: :placement [H] >> >> #+caption: A test block >> #+BEGIN_SRC ipython >> >> 'hello' >> #+END_SRC >> >> exports to latex as: >> >> \begin{listing}[htbp] >>

[O] question on org-element-interpret-data and when it works

I am trying to find some ways to programatically modify org-elements that use fewer regexps and motion commands. It seems like org-dp ( https://github.com/tj64/org-dp) was intended to do that but it is not clear enough how you might use it, and it also doesn't seem to support plain-lists yet.

Re: [O] mailto link for the #+email keyword: Suppressing backslash and braces "escaping" for latex exports

I posted this on your stack exchange question: #+latex_class: report #+options: author:nil email:nil #+latex_header: \author{Some user \thanks{\href{mailto:b...@comp.org}{ b...@comp.org}}} That is basically what ox-latex expands those keywords into. John ---

Re: [O] [RFC] Could we get rid of Org specific "mark ring"

On 2/25/18, Nicolas Goaziou wrote: > Hello, > > Samuel Wales writes: > >> in org maint, i can click on a link and, without any cognitive >> overhead, and with certainty, run a command to get back to the link i >> clicked on. to me this seems like

Re: [O] Removing ding each time I type TAB when not after a structure template with org-tempo enabled

Hi Nicolas, Thanks. This is close, but not completely fixed: When I have the point at the start of a line in a Org file, and type the TAB key, it does not move like it should up underneath the prior heading. See annotated screenshot: https://i.imgur.com/zUH28W0.png I'll have to re-instate my

[O] mailto link for the #+email keyword: Suppressing backslash and braces "escaping" for latex exports

Dear orgers, I'd like to have a clickable mailto link in a latex pdf export (of a report) for the #+email:-keyword's content. I assume this is not achievable with latex commands, for example #+email: \href{mailto:a...@b.com}{a...@b.com} because org escapes here backslashes and the braces:

Re: [O] Editing in two columns

On Sat, Feb 24, 2018, at 7:26 PM, Peter Davis wrote: > > On Sat, Feb 24, 2018, at 7:18 PM, Peter Neilson wrote: > > On Sat, 24 Feb 2018 19:01:25 -0500, Peter Davis > > wrote:> > > > > Is there a way to edit with two columns displayed so I’m only > > > editing> > > and

Re: [O] [RFC] Could we get rid of Org specific "mark ring"

Hello, Samuel Wales writes: > in org maint, i can click on a link and, without any cognitive > overhead, and with certainty, run a command to get back to the link i > clicked on. to me this seems like basic hypertext ability, such as > you might find in info or the back