From: Thorsten Jolitz <firstname.lastname@example.org>
Subject: Re: c-c ' in babel source blocks strips final newline or adds blank line upon returning, but never neither
Date: Sun, 27 Jul 2014 00:07:29 +0200 [thread overview]
Message-ID: <email@example.com> (raw)
Samuel Wales <firstname.lastname@example.org> writes:
> i think there are several misunderstanding here.
> first, i am not talking about outorg at all. i am talking about babel
> source code blocks. i have changed the subject header to make that
> more obvious. outorg is not relevant to this thread, as far as i can
Me too, but I had to deal with this because doing C-c ' in babel
src-blocks in an *outorg-edit-buffer* might introduce
newlines/indentation even if no editing takes place, and these unwanted
changes cause problems because they are propagated to the original
source file in the outorg conversion process.
So I would say we talk about the same thing, just in a different
> second, emacs behavior is not built in. it depends on
> require-final-newline. if babel would respect require-final-newline,
> i would be happy. however, it does not. so it is not an emacs issue
> in this respect.
Ah, `require-final-newline' was the var I was looking for when dealing
with this. Thx for the tip.
> third, before posting the original post, i fully tested both the
> variable that you suggested and require-final-newline. the value of
> the former determines which bug occurs.
Just gave a hint at the risk that you might be aware of it already.
> i hope that's enough to get us all on the same page. i have very
> severe rsi so i limit typing to less than 4 minutes at a time. i
> won't be able to reply for some time.
Anyway, the issue deserves some attention.
prev parent reply other threads:[~2014-07-26 22:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-26 21:51 c-c ' in babel source blocks strips final newline or adds blank line upon returning, but never neither Samuel Wales
2014-07-26 22:07 ` Thorsten Jolitz [this message]
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).