From: Jambunathan K <kjambunathan@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, 04 Nov 2013 02:35:42 +0530 [thread overview]
Message-ID: <87a9hlxkk9.fsf@gmail.com> (raw)
In-Reply-To: <CF489715-5A5F-4761-968C-D582627E0D3B@gmail.com> (Dror Atariah's message of "Sun, 3 Nov 2013 21:28:09 +0100")
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.
cache-long-scans
Variable: Non-nil means that Emacs should use caches in attempt to
speedup buffer scans.
** `cache-long-line-scans' has been renamed to `cache-long-scans'
because it affects caching of paragraph scanning results as well.
----------------------------------------------------------------
Org files in sense paragraph oriented and not line-oriented. There was
some work on Org Merge Driver. (Search for it in the list). I had also
pointed out this LibreOffice GSoC project earlier -
http://gsoc-tzvetelina.blogspot.in/ - the ideas discussed therein could
be of some relevance to building a Org merge driver.
Dror Atariah <drorata@gmail.com> writes:
> 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
next prev parent reply other threads:[~2013-11-03 21:04 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 [this message]
2013-11-04 11:23 ` Bastien
2013-11-04 19:32 ` Samuel Wales
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=87a9hlxkk9.fsf@gmail.com \
--to=kjambunathan@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).