From: Jean Louis <bugs@gnu.support>
To: Drew Adams <drew.adams@oracle.com>
Cc: "60741@debbugs.gnu.org" <60741@debbugs.gnu.org>,
Juri Linkov <juri@linkov.net>
Subject: bug#60741: 29.0.60; 'M-c' shadowed in the minibuffer
Date: Thu, 19 Jan 2023 08:34:05 +0300 [thread overview]
Message-ID: <Y8jWTYjK4kGy3qgh@protected.localdomain> (raw)
In-Reply-To: <SJ0PR10MB54880603271F2894CC14BD6DF3C79@SJ0PR10MB5488.namprd10.prod.outlook.com>
* Drew Adams <drew.adams@oracle.com> [2023-01-18 21:48]:
> > > 'M-c' is bound globally to 'capitalize-word', but this keybinding
> > > is shadowed in the minibuffer, thus making it impossible to
> > > capitalize words.
>
> Is this something new in Emacs 29? I don't see it
> in previous versions (I don't have 29). What is
> `M-c' bound to now in the minibuffer keymaps?
>
> Why should we lose this longstanding, useful key
> binding? Users should be able to use most normal
> editing keys in the minibuffer - it's first and
> foremost an editing buffer.
I use that key all the time in the minibuffer, and can't without
it. I give you the practical example:
- PDF book in Dired is called:
21252030 agenda for sustainable development web.pdf
- I click and wish to index the book, so initial prompt for the title
will be:
21252030 agenda for sustainable development web.pdf
- I delete 21252030 with M-d and use M-c to get following:
Agenda For Sustainable Development
- then I press RET to record information
Without M-c in minibuffer I would need to re-assign key binding.
But it works, I did not know something changed.
--
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
In support of Richard M. Stallman
https://stallmansupport.org/
next prev parent reply other threads:[~2023-01-19 5:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 19:54 bug#60741: 29.0.60; 'M-c' shadowed in the minibuffer Juri Linkov
2023-01-18 18:06 ` Juri Linkov
2023-01-18 18:46 ` Drew Adams
2023-01-18 18:52 ` Juri Linkov
2023-01-18 18:59 ` Drew Adams
2023-01-19 5:34 ` Jean Louis [this message]
2023-01-19 7:25 ` Eli Zaretskii
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=Y8jWTYjK4kGy3qgh@protected.localdomain \
--to=bugs@gnu.support \
--cc=60741@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=juri@linkov.net \
/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).