all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Eli Zaretskii'" <eliz@gnu.org>
Cc: 13273@debbugs.gnu.org
Subject: bug#13273: 24.3.50; [PATCH] enhancement request: repeatable `visual-line-mode' line	movements
Date: Tue, 25 Dec 2012 21:59:46 -0800	[thread overview]
Message-ID: <366B6F4FCD994713A19D8B772843D329@us.oracle.com> (raw)
In-Reply-To: <83k3s6ni5u.fsf@gnu.org>

> >    * `home' - `beginning-of-line'
> >    * `end'  - `end-of-line'
> >    * `C-a'  - `beginning-of-visual-line'
> >    * `C-e'  - `end-of-visual-line'
> 
> I think it would be better the other way around: leave C-a and C-e
> move by physical lines, and make Home and End move by visual lines,
> which I think is consistent with other applications.

OK, go for it, please.  Doesn't matter to me either way.  I was thinking of
`home' and `end' as being the stronger, more distant movements, based on their
names and based on (I guess misunderstanding) some of the discussion in
emacs-devel.  I am certainly no expert on what the "standard"/"conventional"
meanings are.






  reply	other threads:[~2012-12-26  5:59 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-24 22:27 bug#13273: 24.3.50; [PATCH] enhancement request: repeatable `visual-line-mode' line movements Drew Adams
2012-12-25 17:41 ` Eli Zaretskii
2012-12-26  5:59   ` Drew Adams [this message]
2012-12-26  6:32   ` Drew Adams
2012-12-27 10:08     ` Vitalie Spinu
2012-12-27 16:16       ` Drew Adams
2012-12-27 19:13         ` Vitalie Spinu
2012-12-27 19:35           ` Drew Adams
2012-12-28 18:06 ` Vitalie Spinu
2012-12-28 18:51   ` Drew Adams
2012-12-28 19:22     ` Vitalie Spinu
2012-12-28 19:36       ` Eli Zaretskii
2012-12-28 19:55         ` Vitalie Spinu
2012-12-28 20:13           ` Eli Zaretskii
2012-12-28 20:04       ` Drew Adams
2012-12-28 20:33         ` Vitalie Spinu
2012-12-28 21:05           ` Drew Adams
2019-06-27 12:04 ` Lars Ingebrigtsen

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

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

  git send-email \
    --in-reply-to=366B6F4FCD994713A19D8B772843D329@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=13273@debbugs.gnu.org \
    --cc=eliz@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.