From: Juri Linkov <juri@jurta.org>
To: Miles Bader <miles@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: C-n and C-a
Date: Thu, 12 Feb 2009 12:05:12 +0200 [thread overview]
Message-ID: <87mycs53q3.fsf@jurta.org> (raw)
In-Reply-To: <87ljscifbc.fsf@catnip.gol.com> (Miles Bader's message of "Thu, 12 Feb 2009 11:01:27 +0900")
> 3. Add a wrap-prefix that indents the wrapped lines a lot so that
> they're in the filename column (maybe indented extra within that
> column).
That would be very nice. Setting `wrap-prefix' in Dired to a string of
50 spaces (handling variable widths is possible in `insert-directory')
produces a good-looking result. However, when `word-wrap' is non-nil
then the result is weird: there are many empty lines for every wrapped
file name. Seems like a bug. I'll create a bug report later.
>> For the same reason I think we should not set word-mode in
>> visual-line-mode.
>
> This seems bizarre -- AFAICS, like 95% of the goal of visual-line-mode
> is to make it easy to enable a word-wrapped mode for editing
> paragraphs-end-in-newline text (i.e., a display-time version of
> longlines-mode).
The problem is that currently by default C-n/C-p moves by visual lines,
but C-a/C-e moves by real lines. `visual-line-mode' is the only way to
cause C-a/C-e to move by visual lines. But it forces `word-wrap' to be
t even in buffers where word-wrap should be nil (where word wrap gives
sub-optimal results).
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2009-02-12 10:05 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-29 14:32 C-n and C-a Richard M Stallman
2009-01-29 15:10 ` Tassilo Horn
2009-01-29 16:09 ` Harald Hanche-Olsen
2009-01-29 17:15 ` Tassilo Horn
2009-01-29 19:40 ` Adrian Robert
2009-01-30 0:32 ` Juri Linkov
2009-01-30 1:20 ` Stefan Monnier
2009-01-30 9:45 ` Eli Zaretskii
2009-01-31 17:45 ` Juri Linkov
2009-01-31 19:47 ` Stefan Monnier
2009-02-02 1:45 ` Juri Linkov
2009-01-31 20:33 ` Chong Yidong
2009-02-02 1:47 ` Juri Linkov
2009-01-30 7:25 ` Richard M Stallman
2009-01-29 18:24 ` Karl Fogel
2009-01-29 18:48 ` Harald Hanche-Olsen
2009-01-29 21:41 ` Stefan Monnier
2009-01-30 16:07 ` Sascha Wilde
2009-01-31 20:34 ` Chong Yidong
2009-01-30 0:29 ` Juri Linkov
2009-01-30 6:12 ` mail
2009-01-31 17:45 ` Juri Linkov
2009-01-31 22:35 ` Drew Adams
2009-02-01 20:11 ` Leo
2009-02-03 15:11 ` Carsten Dominik
2009-02-02 1:54 ` Juri Linkov
2009-02-02 2:25 ` Drew Adams
2009-02-02 9:45 ` Juri Linkov
2009-02-06 0:45 ` Juri Linkov
2009-02-06 16:04 ` Chong Yidong
2009-02-08 0:48 ` Juri Linkov
2009-02-08 20:08 ` Stefan Monnier
2009-02-09 21:22 ` Christian Schlauer
2009-02-09 22:02 ` Drew Adams
2009-02-10 2:05 ` Stefan Monnier
2009-02-10 3:11 ` Drew Adams
2009-02-11 22:45 ` Juri Linkov
2009-02-12 2:01 ` Miles Bader
2009-02-12 10:05 ` Juri Linkov [this message]
2009-02-12 11:04 ` Miles Bader
2009-02-13 6:33 ` Richard M Stallman
2009-02-07 1:52 ` Stefan Monnier
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=87mycs53q3.fsf@jurta.org \
--to=juri@jurta.org \
--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).