emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Thorsten Jolitz <tjolitz@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: c-c ' strips final newline or adds blank line, but never neither
Date: Sat, 26 Jul 2014 12:23:58 +0200	[thread overview]
Message-ID: <8738dopge9.fsf@gmail.com> (raw)
In-Reply-To: CAJcAo8u2ofk+ubrrLiPRfeunPKOq=XtFMsfiaGnCwW1gtY9EXQ@mail.gmail.com

Samuel Wales <samologist@gmail.com> writes:

hi Samuel,

> did you try it?

no, that was just a hint.

But I know what you are talking about, since I had these problems with
Outorg too - whitespace changes in the conversion process between
programming language mode and org-mode although no editing at all took

The following chain of actions should not change the original (say
emacs-lisp) buffer:

1. M-# # (outorg-edit-as-org) in emacs-lisp buffer 

2. 2x C-c ' on emacs-lisp src-block

3. M-# in *outorg-edit-buffer*

since only 4 conversions but no editing at all took place. But depending
on your config (or the org defaults) and maybe org/outorg bugs
indentation and newlines might have been added removed.

In outorg I have e.g.

| outorg-remove-trailing-blank-lines
| outorg-unindent-active-source-blocks

to deal with this issue. IIRC I always first remove all
trailing-blank-lines, and then add one.

Isn't that even an 'upstream' issue? It seems Emacs itself inserts
trailing blank lines in buffers if they are missing, at least I had to deal
with this in the outorg conversion process.

I vaguley remember having read something about 'by default every buffer
should end with a trailing blank line, and this is enforced by Emacs',
but could not find any info about this nor related config vars.

> On 7/25/14, Thorsten Jolitz <tjolitz@gmail.com> wrote:
>> Samuel Wales <samologist@gmail.com> writes:
>>> i find that when i do c-c ' on a source block, it either strips the
>>> final newline in the editing buffer or adds an unwanted blank line in
>>> the source block.
>>> i like to have final newlines in all of my buffers, including editing
>>> buffers.  what setting allows this without introducing a blank line at
>>> the end of a source block?
>> ,----[ C-h v org-src-strip-leading-and-trailing-blank-lines RET ]
>> | org-src-strip-leading-and-trailing-blank-lines is a variable defined
>> | in `org-src.el'.  Its value is nil
>> |
>> | Documentation:
>> | If non-nil, blank lines are removed when exiting the code edit buffer.
>> `----
>> --
>> cheers,
>> Thorsten


  reply	other threads:[~2014-07-26 10:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-24 22:48 c-c ' strips final newline or adds blank line, but never neither Samuel Wales
2014-07-25  8:01 ` Thorsten Jolitz
2014-07-25 22:45   ` Samuel Wales
2014-07-26 10:23     ` Thorsten Jolitz [this message]
2014-07-26 21:54       ` Samuel Wales
2014-07-25 22:47   ` Samuel Wales
2014-07-27 11:50 ` Bastien

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:

  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=8738dopge9.fsf@gmail.com \
    --to=tjolitz@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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).