unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Miles Bader <miles.bader@necel.com>
To: "Adrian Robert" <adrian.b.robert@gmail.com>
Cc: emacs- devel <emacs-devel@gnu.org>
Subject: Re: Patch: enhanced mark navigation commands
Date: Wed, 05 Mar 2008 15:19:18 +0900	[thread overview]
Message-ID: <buoy78xelqx.fsf@dhapc248.dev.necel.com> (raw)
In-Reply-To: <55f7df060803042112w380b5170qe964002c6c06ab01@mail.gmail.com> (Adrian Robert's message of "Wed, 5 Mar 2008 08:12:35 +0300")

"Adrian Robert" <adrian.b.robert@gmail.com> writes:
> Specifically, the keys M-p and M-n are bound to move forwards and
> backwards through the mark history.  Also, immediately after popping a
> global mark, e.g., with C-x C-SPC, then the global mark ring is used.

GIven that M-n and M-p are widely used bindings, I don't think you'll
win many fans by adding global bindings for them, unless the new
bindings clearly don't conflict or interact in strange ways with other
uses.

For instance, comint uses M-n and M-p; is the new functionality not
useful in comint buffers?  Also, given the possibility for moving
between buffers (with global marks), it would be very disconcerting if,
a user was repeatedly hitting, say M-n, and suddenly things "stopped
working" as soon as he popped into a comint (etc) buffer.

Gnus is another heavy user of M-n/M-p.

-Miles

-- 
White, adj. and n. Black.




  reply	other threads:[~2008-03-05  6:19 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-05  5:12 Patch: enhanced mark navigation commands Adrian Robert
2008-03-05  6:19 ` Miles Bader [this message]
2008-03-05 12:23   ` paul r
2008-03-05  6:41 ` Dan Nicolaescu
2008-03-06  0:57   ` Juri Linkov
2008-03-06  1:47     ` Dan Nicolaescu
2008-03-06  7:18       ` Drew Adams
2008-03-06 10:09       ` Juri Linkov
2008-03-09 21:55     ` Juri Linkov
2008-03-05 16:11 ` Ted Zlatanov
2008-03-05 19:20   ` Stefan Monnier
2008-03-05 19:48     ` Ted Zlatanov
2008-03-05 22:10       ` Miles Bader
2008-03-10 13:09         ` Ted Zlatanov
2008-03-10 22:34           ` Juri Linkov
2008-03-11 15:08             ` Ted Zlatanov
2008-03-06  0:54 ` Juri Linkov

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=buoy78xelqx.fsf@dhapc248.dev.necel.com \
    --to=miles.bader@necel.com \
    --cc=adrian.b.robert@gmail.com \
    --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).