From: Jonas Bernoulli <jonasbernoulli@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: Org-Mode mailing list <emacs-orgmode@gnu.org>,
"Charles C. Berry" <ccberry@ucsd.edu>
Subject: Re: Something like #+BIND but for the destination buffer
Date: Sat, 14 Jan 2017 18:47:40 +0100 [thread overview]
Message-ID: <CA+7KPGeE2fAQ+h5NZq38PM3ADTHhKhJ9E5HK9smidz9zVmUFdA@mail.gmail.com> (raw)
In-Reply-To: <877f5xaedv.fsf@nicolasgoaziou.fr>
[-- Attachment #1: Type: text/plain, Size: 1579 bytes --]
I did notice myself that the two-space indentation for blocks that are part
of a list element are reserved and also that one can do what you are
suggesting here to keep the code-block as part of the list item while at
the same time not get those two extra spaces. (By the way, I don't like
that work-around.)
However for me that's what happened for example blocks only. For source
blocks I got an additional five spaces, for which I found no explanation.
(The only indentation in the Org source before the code-block lines are the
two part-of-a-list-element spaces.)
On Sat, Jan 14, 2017 at 3:46 PM, Nicolas Goaziou <mail@nicolasgoaziou.fr>
wrote:
> Hello,
>
> Jonas Bernoulli <jonasbernoulli@gmail.com> writes:
>
> > This seemed promising at first but let to all kinds of strange behavior.
> > Code-blocks that are part of a list item turned out to particularly
> > painful, as here "Finally, you can use ‘-i’ to preserve the indentation
> of
> > a specific code block" means that an additional five (if I remember
> > correctly) spaces appear out of nowhere (only for code-blocks,
> > example-blocks behaved as expected (or at least in an reasonable
> > way)).
>
> With -i, indentation is taken from column 0, so the five spaces didn't
> come out of nowhere, but probably from the indentation you gave to the
> contents of the source block, which is not necessary. E.g.,
>
> - Some list item
>
> #+BEGIN_SRC emacs-lisp -i
> This is the code, and it will not break list
> #+END_SRC
>
>
> Regards,
>
> --
> Nicolas Goaziou
>
[-- Attachment #2: Type: text/html, Size: 2140 bytes --]
next prev parent reply other threads:[~2017-01-14 17:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-31 14:17 Something like #+BIND but for the destination buffer Jonas Bernoulli
2016-12-31 14:40 ` Nicolas Goaziou
2017-01-03 13:52 ` Jonas Bernoulli
2017-01-03 13:59 ` Kaushal Modi
2017-01-03 14:43 ` Thomas S. Dye
2017-01-03 14:59 ` Nick Dokos
2017-01-03 15:53 ` Jonas Bernoulli
2017-01-03 17:00 ` Charles C. Berry
2017-01-14 13:42 ` Jonas Bernoulli
2017-01-14 14:46 ` Nicolas Goaziou
2017-01-14 17:47 ` Jonas Bernoulli [this message]
2017-01-14 17:52 ` Nicolas Goaziou
2017-01-14 19:50 ` Jonas Bernoulli
2017-01-14 22:11 ` Jonas Bernoulli
2017-01-14 22:20 ` Jonas Bernoulli
2017-01-14 21:48 ` Jonas Bernoulli
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=CA+7KPGeE2fAQ+h5NZq38PM3ADTHhKhJ9E5HK9smidz9zVmUFdA@mail.gmail.com \
--to=jonasbernoulli@gmail.com \
--cc=ccberry@ucsd.edu \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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).