Dror Atariah dror...@gmail.com writes:
[...]
Therefore, as I mentioned, in LaTeX I use visual-line-mode and I
insert manually line breaks at the end of sentences (or where *I* find
appropriate). What would be the best practice for org? I understand
that visual-line-mode has some problems
If you have really l...o...n...g lines you need to turn on some sort of
caching so that Emacs display doesn't start sucking.
I believe the variable you need is this. Just double check. I use
development version of Emacs so the details could differ for your
specific version.
Hi Dror,
Dror Atariah dror...@gmail.com writes:
What other issues are there? What do you do when you keep
your org file under VC?
Only a small part of the answer, but you might be interested
in the Git Org merge driver:
Ediff shows word-level changes. In principle, diff-mode does too.
My issue with visual-line-mode is that it disrespects fill-column. I
would use it if it did not. Longlines-mode is a possible workaround.
There is an intermittent bug in Magit maint where RET goes to the
wrong line in Elisp and
I am trying to extend my usage of org, and one of the things I want to
integrate is version controlling of my org files. This is obviously straight
forward, but I am wondering about the best line breaking approach to use. In my
LaTeX docs I maintain one physical line per sentence [1]. This way,
