From: Jeremie Juste <email@example.com> To: Nick Dokos <firstname.lastname@example.org> Cc: email@example.com Subject: Re: org-tempo question Date: Thu, 24 Sep 2020 20:18:04 +0200 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> Hello Nick, Thanks for the feedback. I'm not sure I understand your setting entirely. I have reproduced the behaviour of tempo inside an org src block below. I don't have any comma before the source block expansion unless I type it. Any character except space or tab on the line of the expansion destroys it. For example item 2 below. I have noted that the example block on item 3 doesn not expand at all (item 3). My normal usage is generally the item 1 case and I get the expected behavior. #+BEGIN_SRC org * heading 1 (cursor position) <s - item 1 <e - item 2 , <s - item 3 , <e * heading 1 (expansion) #+BEGIN_SRC R #+end_src - item 1 #+begin_example #+end_example - item 2 , #+BEGIN_SRC #+end_src - item 3 , <e #+end_src HTH, Jeremie - GNU Emacs 28.0.50 - Org mode version 9.4 Nick Dokos <firstname.lastname@example.org> writes: > I can't say anything about indentation (I encounter problems that I > have not reported because of lack of time to investigate combined with > laziness - but I suspect they are, partly at least, of my own making). > > But when I do `<e TAB' inside a block, I get a properly quoted (though > badly indented) example block, with commas before the #+begin and the > #+end_example lines - OTOH, `<e TAB' outside a block gives me a > no-indent example block even if I have spaces before the `<e' - if I > have printable charactes before the `<e', it does not get expanded: > > #+NAME: third > #+begin_src org > > - an item > - subitem > > ,#+begin_example > > ,#+end_example > > #+end_src > > #+begin_example > > #+end_example > > > The commas are important: are you not getting them?
next prev parent reply other threads:[~2020-09-24 18:18 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-24 13:30 Bruno BEAUFILS 2020-09-24 16:54 ` Nick Dokos 2020-09-24 18:18 ` Jeremie Juste [this message] 2020-09-24 17:17 ` Jeremie Juste
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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: org-tempo question' \ /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
Code repositories for project(s) associated with this 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).