I'm using outorg to convert an elisp file to an org file and then back to an elisp file via
(outorg-convert-back-to-code). When I do this conversion I notice that it looks like there is an extra newline between headlines and source blocks. On the image below the left is my original elisp file and the right is after the conversions. It seems as if the conversion added an extra newline between the comment and the code. However, when saving the contents of the buffers before and after conversion and testing for this via
(string= original-buffer-contents after-conversion-contents) I get
t. So the buffer contents are the same.
Upon further investigation, I can't move the cursor over the "extra newline". It always skips it. I suspect that there is no actual newline added to the buffer contents and this is some sort of visual (bug?) thing.
What's happening here? And how can I prevent this "extra newline" from displaying?
This is what is displayed when I use
describe-char just before the (nonexistent?) newline. The character is described as a newline.
Another thing I found interesting is what happens when I try to delete it (e.g. by putting my curser before the
(defvar and pressing backspace). If the extra newline existed, pressing backspace twice should leave the commented line on the line above
(defvar line. However when I press backspace twice (the right window in the picture below) the two lines are joined on the same line indicating the extra new line is not really there.
The left window is the result of pressing backspace one time on the original buffer.