From: "Berry, Charles" <ccberry@health.ucsd.edu>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Bug: org-tempo expansion comments out the following src block when org-src-tabs-natively is 't [9.3 (release_9.3 @ /home/yantar92/.emacs.d/straight/build/org/)]
Date: Thu, 19 Dec 2019 01:15:43 +0000 [thread overview]
Message-ID: <1FDF2AC8-7B81-4D31-A422-BD36F333CA49@ucsd.edu> (raw)
In-Reply-To: <87immdn5n4.fsf@yantar92-laptop.i-did-not-set--mail-host-address--so-tickle-me>
> On Dec 18, 2019, at 5:07 AM, Ihor Radchenko <yantar92@gmail.com> wrote:
>
> Recipe:
>
> 1. emacs -Q
> 2. Execute the following lisp code:
>
> (setq org-src-tab-acts-natively t)
> (require 'org-tempo)
I did not need to add this line to confirm the behavior:
> (push (cons "el" "src emacs-lisp") org-structure-template-alist)
>
> 3. Create the following org file:
>
> <point>
>
> #+begin_src emacs-lisp
> #+end_src
>
> 4. Put the point before the code block
>
> 5.1. Type <s TAB
>
> Observed behaviour:
>
> #+begin_src
>
>
> #+begin_src emacs-lisp
> #+end_src
>
Right. The issue seems to be that `org-tempo-add-block' puts `>' elements in its recipe for converting `org-structure-template-alist' to `tempo-org-template-*' values.
Those are innocuous when `org-src-tab-acts-natively' is nil.
But when `org-src-tab-acts-natively' is `t', an attempt is made to indent within the src block, which I guess is where the trouble lies as an error occurs which prevents the remainder of the template from being inserted.
If you really need `<s', then this is a problem (and a bug).
You might use `C-c C-,' as long as you have no other templates defined.
HTH,
Chuck
next prev parent reply other threads:[~2019-12-19 1:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-18 13:07 Bug: org-tempo expansion comments out the following src block when org-src-tabs-natively is 't [9.3 (release_9.3 @ /home/yantar92/.emacs.d/straight/build/org/)] Ihor Radchenko
2019-12-19 1:15 ` Berry, Charles [this message]
2019-12-19 14:16 ` Ihor Radchenko
2022-10-15 4:46 ` Ihor Radchenko
Reply instructions:
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1FDF2AC8-7B81-4D31-A422-BD36F333CA49@ucsd.edu \
--to=ccberry@health.ucsd.edu \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).