From: Bram Adams <firstname.lastname@example.org>
To: Bastien <email@example.com>
Cc: Ihor Radchenko <firstname.lastname@example.org>, email@example.com
Subject: Re: Bug (with fix): org-tempo-add-block incorrectly inserts comma before next `#+begin_src' during expansion [9.3.2 (9.3.2-8-g47b104-elpaplus @ ~/.emacs.d/elpa/org-plus-contrib-20200127/)]
Date: Mon, 3 Feb 2020 13:18:56 -0500 [thread overview]
Message-ID: <7191F9F7-A62D-4859-903C-48F5AB7C3F45@polymtl.ca> (raw)
> Yes, you're right, my fix was wrong - I've followed your indication
> and removed the second occurrence of '>.
> What happens is this: the template expansion calls org-edit-src-code
> which gets the wrong source block boundaries, thus escaping "#+begin"
> with a comma.
> Looking at the second '>, I think there is no need for it here (it
> means: "indent the line"), so we're safe removing it without touching
> `org-edit-src-code' for now.
OK, makes sense, thanks!
> I still think org-edit-src-code should only be called interactively,
> not through internal calls. I'll see if this needs to be fixed too.
next prev parent reply other threads:[~2020-02-03 18:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-02 4:15 Bug (with fix): org-tempo-add-block incorrectly inserts comma before next `#+begin_src' during expansion [9.3.2 (9.3.2-8-g47b104-elpaplus @ ~/.emacs.d/elpa/org-plus-contrib-20200127/)] Bram Adams
2020-02-03 3:38 ` Ihor Radchenko
2020-02-03 4:35 ` Bram Adams
2020-02-03 12:13 ` Bastien
2020-02-03 15:08 ` Bram Adams
2020-02-03 15:45 ` Bastien
2020-02-03 16:23 ` Bram Adams
2020-02-03 17:33 ` Bastien
2020-02-03 18:18 ` Bram Adams [this message]
2020-04-08 15:50 ` Ihor Radchenko
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).