unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: storm@cua.dk (Kim F. Storm)
To: Miles Bader <miles@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Visual line movement inconsistency
Date: Fri, 29 Aug 2008 14:02:47 +0200	[thread overview]
Message-ID: <87vdxkghaw.fsf@kfs-lx.rd.rdm> (raw)
In-Reply-To: <87prnsmywh.fsf@catnip.gol.com> (Miles Bader's message of "Fri\, 29 Aug 2008 09\:46\:06 +0900")

Miles Bader <miles@gnu.org> writes:

> Tassilo Horn <tassilo@member.fsf.org> writes:
>> But is this inconsistent behavior of C-n/C-p and C-a/C-e really the
>> intended default?  I think it would be better if C-a/C-e respected the
>> value of `line-move-visual', too.  Then the default would be like
>> visual-line-mode without word-wrapping.
>
> It was discussed and the current behavior seemed to be the consensus
> choice.
>
> I agree that it can be confusing, but I think it's much more dangerous
> to change the default behavior of C-a/C-e, because people depend a lot
> more on their precise behavior (whereas C-n/C-p are more often used in
> conjunction with visual feedback).

I mostly agree, but then it is all the more important that the fringe
indicators are used to show that lines are word wrapped (i.e. continued).
Otherwise, there is no visible clue to what a given line-oriented command
will actually do.

IMO, it would make sense to have a new pair of fringe bitmaps
for word wrapped lines that are a bit less in your face than the
normal continued/continuation bitmaps.

These bitmaps would be used on lines which are word wrapped, in
contrast to lines which are really continued (typically because there
is no suitable space character in the wrap margin, so a word has to be
cut in two).

I previously proposed a new fringe bitmap (showing ...) for continued
lines, but it may be even more appropritate for word wrap.

I know it is feature freeze, but I feel this aspect of word wrap
has not been fully addressed so far.

-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk





  parent reply	other threads:[~2008-08-29 12:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-28 13:45 Visual line movement inconsistency Tassilo Horn
2008-08-29  0:46 ` Miles Bader
2008-08-29  7:18   ` Tassilo Horn
2008-08-29  7:54     ` Lennart Borgman (gmail)
2008-08-29 12:02   ` Kim F. Storm [this message]
2008-08-29 14:59     ` Miles Bader
2008-08-29 18:13       ` Kim F. Storm
2008-08-29 23:53         ` Miles Bader
2008-08-30 15:35           ` Kim F. Storm
2008-08-30 23:53             ` Chong Yidong

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=87vdxkghaw.fsf@kfs-lx.rd.rdm \
    --to=storm@cua.dk \
    --cc=emacs-devel@gnu.org \
    --cc=miles@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.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).