unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tassilo Horn <tassilo@member.fsf.org>
To: rms@gnu.org
Cc: emacs-devel@gnu.org
Subject: Re: C-n and C-a
Date: Thu, 29 Jan 2009 16:10:25 +0100	[thread overview]
Message-ID: <87bptqywpq.fsf@thinkpad.tsdh.de> (raw)
In-Reply-To: <E1LSXwC-0001K2-VZ@fencepost.gnu.org> (Richard M. Stallman's message of "Thu, 29 Jan 2009 09:32:12 -0500")

Richard M Stallman <rms@gnu.org> writes:

Hi Richard,

> The new definitions of C-n and C-p seem to work reasonably
> conveniently with the very long lines that non-Emacs-users often
> write.  However, it is very counterintuitive that C-a and C-e have not
> been changed in the same way.

I mentioned this inconsistencies before in
<874p55z20j.fsf@thinkpad.tsdh.de>.  I was told that the current behavior
was due to a consensus.  But still I don't like it, so I switch on
`visual-line-mode' where everything operates consistently on screen
lines.

IMHO without `visual-line-mode' everything should work on real lines,
with it turned on everything should work on screen lines (as it does
right now).  This half screen half real line behavior is somewhat
confusing.

> I think they too should be changed to operate on screen lines;
> that's a necessary part of the change that was already made.

You can have this by turning on `visual-line-mode'.

> If C-a and C-e are changed this way, we would want some way to go to
> the beginning and end of the real line.  Here are some ideas:
>
> * Make C-u C-a and C-u C-e do this.  I suspect nobody uses
> those combinations with their current meanings.

Yes, that would be ok.  A bit more convenient would be to type `C-a'
twice, which would toggle between screen and real line beginning.

> * Make M-{ and M-} treat each line as a paragraph.  That would be the
> right thing for them to do in such text.  This would require either a
> minor mode or detecting long-line text heuristically.

I wouldn't like that, because it would require that texts one writes
have to obey the convention that each paragraph has to be on one line.
Especially when working with others this cannot be enforced while an
empty line to mark paragraphs in pretty standard.

Bye,
Tassilo




  reply	other threads:[~2009-01-29 15:10 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 [this message]
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
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=87bptqywpq.fsf@thinkpad.tsdh.de \
    --to=tassilo@member.fsf.org \
    --cc=emacs-devel@gnu.org \
    --cc=rms@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).