unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Bozhidar Batsov" <bozhidar@batsov.com>
To: emacs-devel@gnu.org
Subject: Re: project prefix and mark-page
Date: Wed, 21 Jul 2021 14:16:54 +0300	[thread overview]
Message-ID: <97d188b6-a2c7-417c-bdce-09e2e56e97a3@www.fastmail.com> (raw)
In-Reply-To: <cd02fb4c-0b32-c062-6dc0-bf2634f70697@inventati.org>

[-- Attachment #1: Type: text/plain, Size: 1309 bytes --]

The mark-* keybindings are all over the place and they are hardly consistent (e.g. check out the bindings for sexp, defun and paragraph), but I guess in the case of mark-page the "p" in C-x C-p does carry some meaning. It would have been nice if all of those used some consistent prefix (e.g. how easy-kill does things), but I think this ship has sailed, as a lot of people are quite used to the current keybindings.

On Wed, Jul 21, 2021, at 1:43 PM, Manuel Uberti wrote:
> On 21/07/21 11:20, Bozhidar Batsov wrote:
> > I think a simple solution for you would be to just rebind `C-x C-p` (I assume 
> > you don't need it) or add local bindings `C-c p`  and `C-c C-p`. I'm a big fan 
> > of such "symmetric" keybindings and I use them all the time.
> 
> Yes, like I said I am disabling C-x C-p in my configuration.
> 
> C-c p and C-c C-p are nice suggestions, though, thanks. I was using them with 
> Projectile before, but I have to say nowadays I try to stick with the default 
> key bindings as much as possible in order to better understand what is going 
> before re-binding built-in functionalities to different keys.
> 
> Anyway, if there are historical reasons for C-x C-p I understand completely and 
> I can work around my problem in my init.el.
> 
> -- 
> Manuel Uberti
> www.manueluberti.eu
> 
> 

[-- Attachment #2: Type: text/html, Size: 1882 bytes --]

  reply	other threads:[~2021-07-21 11:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-21  7:49 project prefix and mark-page Manuel Uberti
2021-07-21  9:20 ` Bozhidar Batsov
2021-07-21 10:43   ` Manuel Uberti
2021-07-21 11:16     ` Bozhidar Batsov [this message]
2021-07-21 12:28       ` Eli Zaretskii
2021-07-21 12:43         ` Bozhidar Batsov
2021-07-21 13:05           ` Eli Zaretskii
2021-07-21 15:02             ` Pankaj Jangid
2021-07-21 15:40             ` Manuel Uberti
2021-07-22  5:32               ` Bozhidar Batsov

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=97d188b6-a2c7-417c-bdce-09e2e56e97a3@www.fastmail.com \
    --to=bozhidar@batsov.com \
    --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).