From: Tassilo Horn <tassilo@member.fsf.org>
To: emacs-devel@gnu.org
Subject: Re: C-n and C-a
Date: Thu, 29 Jan 2009 18:15:23 +0100 [thread overview]
Message-ID: <87zlhaxcd0.fsf@thinkpad.tsdh.de> (raw)
In-Reply-To: <20090129.170913.525581315788013895.hanche@math.ntnu.no> (Harald Hanche-Olsen's message of "Thu, 29 Jan 2009 17:09:13 +0100 (CET)")
Harald Hanche-Olsen <hanche@math.ntnu.no> writes:
> + Tassilo Horn <tassilo@member.fsf.org>:
>
>> A bit more convenient would be to type `C-a' twice, which would
>> toggle between screen and real line beginning.
>
> Or even more simply: If the cursor is at the beginning of a screen
> line, let C-a go to the beginning of the real line. Otherwise it goes
> to the beginning of the screen line. That way you don't have to
> remember any state. I am sure I could get used to this real quick.
> (Or was that in effect what you were suggesting already?)
Not exactly. I though that the first C-a would jump to the beginning of
the screen line, a second would jump to the beginning of the real line,
a third would jump back to the beginning of the previous screen line.
Of course this would have to me remembered.
But I think this toggling behavior is only convenient in very rare
cases, so I'd go with our simple approach. (To go back to the beginning
of the previous screen line only a few `next-line's are needed anyway.)
Bye,
Tassilo
--
A child of five could understand this! Fetch me a child of five!
next prev parent reply other threads:[~2009-01-29 17:15 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 [this message]
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=87zlhaxcd0.fsf@thinkpad.tsdh.de \
--to=tassilo@member.fsf.org \
--cc=emacs-devel@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).