emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Kitchin <jkitchin@andrew.cmu.edu>
To: Vikas Rawal <vikaslists@agrarianresearch.org>
Cc: Nick Dokos <ndokos@gmail.com>,
	org-mode mailing list <emacs-orgmode@gnu.org>,
	Ken Mankoff <mankoff@gmail.com>
Subject: Re: Trouble with autofill mode
Date: Tue, 04 Aug 2015 08:47:14 -0400	[thread overview]
Message-ID: <m2r3nj6x0t.fsf@andrew.cmu.edu> (raw)
In-Reply-To: <71D66E68-DBC6-4909-9442-CBD46DAC5468@agrarianresearch.org>

I turned off auto-fill everywhere many years ago (it messed up my code
blocks in org-mode too much. I usually write them in org-mode, not the
programming mode). I use (global-visual-line-mode 1)

I cannot think of any issues that causes. I even have an
unfill-paragraph to fix what my students do ;) I cannot say I seen many
advantages with git with this, but we usually have one paragraph on a
line.  One day I just need to learn how to do word-based diffs/merge for
text, instead of line-based.

The only exception to auto-fill i can think of is in mu4e, where emails to get filled
so they fit in about an 80 character field.

Vikas Rawal writes:

>>
>>
>> On 2015-08-03 at 23:11, Vikas Rawal <vikaslists@agrarianresearch.org> wrote:
>>> But I guess one has to have some compromise somewhere :)
>>
>> Another compromise would be to stop using autofill mode and use visual-line-mode or something else. I recently made the switch after many years of auto-fill. It takes a bit of getting used to, but it works well.
>>
>>
>
> Yes, I have been thinking about this too. visual-line-mode with each sentence in a separate line would have many other advantages too. It would perhaps be better for git-like version control of documents written in orgmode. Isn’t it?
>
> Do others have an experience to share about this?
>
> Vikas

--
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu

  reply	other threads:[~2015-08-04 12:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-02 18:54 Trouble with autofill mode Vikas Rawal
2015-08-02 20:18 ` Nicolas Goaziou
2015-08-03  0:05   ` Vikas Rawal
2015-08-04  1:12     ` Nick Dokos
2015-08-04  3:11       ` Vikas Rawal
2015-08-04  3:39         ` Ken Mankoff
2015-08-04  4:22           ` Vikas Rawal
2015-08-04 12:47             ` John Kitchin [this message]
2015-08-04 14:08             ` Eric S Fraga
2015-08-05  8:17               ` Sebastien Vauban
2015-08-05  9:31                 ` Eric S Fraga
  -- strict thread matches above, loose matches on Subject: below --
2015-08-03  3:07 Vicente Vera
2015-08-03  3:12 ` Vikas Rawal
2015-08-04  1:04   ` Vikas Rawal
2015-08-04 14:10     ` John Kitchin

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=m2r3nj6x0t.fsf@andrew.cmu.edu \
    --to=jkitchin@andrew.cmu.edu \
    --cc=emacs-orgmode@gnu.org \
    --cc=mankoff@gmail.com \
    --cc=ndokos@gmail.com \
    --cc=vikaslists@agrarianresearch.org \
    /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).