[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [O] Line breaks in org-mode having version control in mind

From: Samuel Wales
Subject: Re: [O] Line breaks in org-mode having version control in mind
Date: Mon, 4 Nov 2013 12:32:24 -0700

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 Org buffers.  There is also an intermittent
bug in bookmark jumping to Org.  These bugs occur without visual-line
or longlines modes.

Longlines-mode might make those bugs more prominent.  I don't know
about visual-line-mode.


On 11/3/13, Dror Atariah <address@hidden> wrote:
> 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, when
> I change one word in a paragraph, it affects only one line, and looking for
> differences between versions is easy. Otherwise, when using fill-paragraph
> for instance, one gets messy changes of the file, as the one word change can
> influence the whole paragraph.
> 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 when it comes to tables... What other
> issues are there? What do you do when you keep your org file under VC?
> Thanks in advance,
> Dror
> [1] http://tex.stackexchange.com/a/4378/412

The Kafka Pandemic: http://thekafkapandemic.blogspot.com

The disease DOES progress.  MANY people have died from it.  ANYBODY can get it.

Denmark: free Karina Hansen NOW.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]