unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: help-gnu-emacs@gnu.org
Subject: Re: visual line mode
Date: Thu, 29 Nov 2012 08:49:41 -0500	[thread overview]
Message-ID: <jwvk3t44j81.fsf-monnier+gmane.emacs.help@gnu.org> (raw)
In-Reply-To: CAJELnLFAsV4F=+MQt8oyYWCaVh6Bnxpv2kUscB3tuXyS3izwvQ@mail.gmail.com

>> What fringe indicators?  You mean, if visual-line-fringe-indicators
>> are customized?
> Why does visual-line-mode turn off fringe indicators by default?

Good, question, I can't remember the answer, tho.
I can guess at a few possibilities:
- "knee-jerk" reaction along the lines of "so you want word wrapping
  like the other crap editors?  well, I'll give you just that, then".
  I don't think we were so thoughtless, but there might have been
  the reasoning that "since other word-wrapping editors don't show
  indicators, it should be OK if we do the same".
- if you have "one logical line per paragraph", then your fringes would
  be pretty much full of indicators everywhere, except at paragraph
  boundaries, which ends up being neither pretty nor convenient.

For the "most lines are long" case mentioned in point 2, a better
approach would be to put a fringe indicator only at
paragraph boundaries.


        Stefan




  parent reply	other threads:[~2012-11-29 13:49 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-12  6:56 visual line mode drain
2012-10-12  8:23 ` Tassilo Horn
2012-10-12  8:24 ` Eli Zaretskii
2012-10-12  8:48   ` Tassilo Horn
2012-10-12 10:35     ` drain
2012-10-12 10:45       ` Peter Dyballa
2012-10-12 10:48         ` drain
2012-10-12 11:27           ` Peter Dyballa
2012-10-12 11:36             ` Tassilo Horn
2012-10-12 13:32               ` Eli Zaretskii
2012-11-28 15:06                 ` Matt McClure
2012-11-28 17:43                   ` Eli Zaretskii
2012-11-29  3:34                     ` Matt McClure
2012-11-29 13:49                   ` Stefan Monnier [this message]
2012-12-01  3:28                     ` Matt McClure
2012-10-12 15:51               ` Peter Dyballa
2012-10-12 13:28             ` Eli Zaretskii
2012-10-12 15:46               ` Peter Dyballa
2012-10-12 16:29                 ` Eli Zaretskii
2012-10-12 22:06                   ` Peter Dyballa
2012-10-13  7:41                     ` Eli Zaretskii
2012-10-13 21:54                       ` Peter Dyballa
2012-10-14  1:56                         ` Bob Proulx
2012-10-14  5:44                         ` Eli Zaretskii
2012-10-16 18:38                           ` drain
2012-10-12 15:55               ` Peter Dyballa
2012-10-12 16:30                 ` Eli Zaretskii
2012-10-12 21:40                   ` Peter Dyballa
2012-10-13  7:36                     ` Eli Zaretskii
2012-10-13 15:26                       ` Peter Dyballa
2012-10-13 15:39                         ` Eli Zaretskii
2012-10-12 11:03       ` Eli Zaretskii
2012-10-12 11:31       ` Tassilo Horn
2012-10-12 11:46         ` drain
2012-10-12 13:30           ` Tassilo Horn
2012-10-12 14:32             ` drain

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.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwvk3t44j81.fsf-monnier+gmane.emacs.help@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=help-gnu-emacs@gnu.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.
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).