From: Samuel Wales <samologist@gmail.com>
To: Dror Atariah <drorata@gmail.com>
Cc: Emacs-orgmode@gnu.org
Subject: Re: Line breaks in org-mode having version control in mind
Date: Mon, 4 Nov 2013 12:32:24 -0700 [thread overview]
Message-ID: <CAJcAo8s7LQbhrVTyy5-HqRrc3dA4QyAUh3M11GZ1g2vL+woqTw@mail.gmail.com> (raw)
In-Reply-To: <CF489715-5A5F-4761-968C-D582627E0D3B@gmail.com>
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.
Samuel
On 11/3/13, Dror Atariah <drorata@gmail.com> 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.
next prev parent reply other threads:[~2013-11-04 19:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-03 20:28 Line breaks in org-mode having version control in mind Dror Atariah
2013-11-03 21:05 ` Jambunathan K
2013-11-04 11:23 ` Bastien
2013-11-04 19:32 ` Samuel Wales [this message]
2013-11-07 16:54 ` Eric S Fraga
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
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=CAJcAo8s7LQbhrVTyy5-HqRrc3dA4QyAUh3M11GZ1g2vL+woqTw@mail.gmail.com \
--to=samologist@gmail.com \
--cc=Emacs-orgmode@gnu.org \
--cc=drorata@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).