unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 3447@debbugs.gnu.org, Kevin Ryde <user42@zip.com.au>
Subject: bug#3447: suggest minibuffer M-< go to start of text
Date: Wed, 13 Nov 2019 23:16:16 +0200	[thread overview]
Message-ID: <87eeyblbof.fsf@mail.linkov.net> (raw)
In-Reply-To: <871rucv4o3.fsf@gnus.org> (Lars Ingebrigtsen's message of "Wed, 13 Nov 2019 04:25:16 +0100")

>> This still doesn't work with <C-home>.  This can be fixed
>> by remapping beginning-of-buffer in the patch below.
>>
>> Like 'C-a' goes to the end of the prompt exactly like <home>,
>> there is no reason not to do the same for 'M-<' and <C-home>.
>
> Looks good to me.
>
>> Moreover, we don't add defcustoms for simple key bindings
>> because keybinding are configured with the help of define-key.
>
> Eli wanted the behaviour not to change by default.

Eli, do you think it would be better to change the default
because 'C-a' and <home> already go to the end of the prompt?

0.01% of users who for some unknown reasons might prefer it
to go to the beginning of the minibuffer, could easily rebind
the key back with define-key one-liner.





  reply	other threads:[~2019-11-13 21:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-01 23:42 bug#3447: suggest minibuffer M-< go to start of text Kevin Ryde
2019-09-30  8:23 ` Lars Ingebrigtsen
2019-09-30  8:53   ` Eli Zaretskii
2019-10-01 11:58     ` Lars Ingebrigtsen
2019-10-01 12:28       ` Eli Zaretskii
2019-10-01 13:02         ` Lars Ingebrigtsen
2019-10-01 13:24           ` Eli Zaretskii
2019-11-12 22:04   ` Juri Linkov
2019-11-13  3:25     ` Lars Ingebrigtsen
2019-11-13 21:16       ` Juri Linkov [this message]
2019-11-14 13:44         ` Eli Zaretskii
2019-11-15  7:47           ` Lars Ingebrigtsen
2019-11-15  8:43             ` Eli Zaretskii
2019-11-23 12:51               ` Lars Ingebrigtsen
2019-11-16 20:15             ` 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=87eeyblbof.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=3447@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=user42@zip.com.au \
    /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).