unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Juri Linkov'" <juri@jurta.org>, <mail@justinbogner.com>
Cc: emacs-devel@gnu.org
Subject: RE: C-n and C-a
Date: Sat, 31 Jan 2009 14:35:28 -0800	[thread overview]
Message-ID: <000601c983f4$387e7400$0200a8c0@us.oracle.com> (raw)
In-Reply-To: <873aez5tp8.fsf@jurta.org>

> >> I think `C-up' and `C-down' are better keys for real line 
> >> motion commands when `up'/`C-p' and `down'/`C-n' are used
> >> for screen line motion commands.
> >
> > C-up and C-down are too far away from the regular position 
> > of fingers to be useful as the only option for anything, one
> > needs a C-p/C-n like equivalent binding.
> 
> If we can't find key bindings equivalent to C-n/C-p/C-a/C-e/C-k
> for real line commands in visual line mode then we should find
> a key sequence to toggle visual line mode easily.

1. I don't use this mode and am ignorant of it. But when it is active, do you
still also need the ordinary line movement bindings? If not, then why not
reuse/co-opt those when the mode is active?

2. If you must use a binding for the mode toggle, then please set that binding
only by visual-line mode itself. Let some command in the mode initialize the
binding for the mode command (even if that binding is in the global map), so
that users who never use the mode do not lose that binding to it. Somewhat a la
mode `ffap-bindings'.

> I propose `C-x n v' (similar to the related key `C-x C-n' plus `v'
> that stands for "visual") or `C-x l v' (with the mnemonics of
> "line visual").

3. C-x n is the narrowing/widening prefix. This seems unrelated to narrowing.

C-x n d		narrow-to-defun
C-x n n		narrow-to-region
C-x n p		narrow-to-page
C-x n w		widen
...               (future)

4. C-x l is count-lines-page.






  reply	other threads:[~2009-01-31 22:35 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 [this message]
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='000601c983f4$387e7400$0200a8c0@us.oracle.com' \
    --to=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=juri@jurta.org \
    --cc=mail@justinbogner.com \
    /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).