From: Lennart Borgman <lennart.borgman@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 5765@debbugs.gnu.org, Chong Yidong <cyd@stupidchicken.com>,
emacs-devel@gnu.org, "Kim F. Storm" <no-spam@cua.dk>,
"Kim F. Storm" <storm@cua.dk>
Subject: bug#5765: Strange things happens with C-v in read-file-name
Date: Fri, 30 Apr 2010 01:54:34 +0200 [thread overview]
Message-ID: <v2se01d8a51004291654v72c85b5dp346da189bce4d5f1@mail.gmail.com> (raw)
In-Reply-To: <jwv6339q3d3.fsf-monnier+emacs@gnu.org>
On Fri, Apr 30, 2010 at 12:51 AM, Stefan Monnier
<monnier@iro.umontreal.ca> wrote:
>> But maybe it is serious enough for the release because CUA keys does
>> not work in the minibuffer at all without this change. (And I doubt it
>> can break anything.)
>
> It's been that way for a long time, so there's no hurry to fix it.
Normally I would agree with that reasoning, but not here. The reason
it has been this way for a long time is probably because cua-mode has
not got much attention. It has been kind of a second class citizen.
Perhaps no one really expected it to work. I think it would be good to
show that we care about this.
Doesn't this change only affect cua-mode users? I think those desire
this change.
next prev parent reply other threads:[~2010-04-29 23:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-27 22:16 Strange things happens with C-v in read-file-name Lennart Borgman
[not found] ` <e01d8a51002020423k4127fea3m2fd5f66c5691ff2d@mail.gmail.com>
2010-03-24 12:37 ` Lennart Borgman
2010-03-24 17:09 ` bug#5765: " Chong Yidong
2010-03-24 18:28 ` Lennart Borgman
2010-03-24 20:44 ` Chong Yidong
2010-03-25 1:17 ` Lennart Borgman
2010-04-29 1:23 ` Lennart Borgman
2010-04-29 11:37 ` Kim F. Storm
2010-04-29 15:42 ` Chong Yidong
2010-04-29 15:45 ` Lennart Borgman
2010-04-29 22:51 ` Stefan Monnier
2010-04-29 23:54 ` Lennart Borgman [this message]
2010-04-30 9:58 ` Kim F. Storm
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=v2se01d8a51004291654v72c85b5dp346da189bce4d5f1@mail.gmail.com \
--to=lennart.borgman@gmail.com \
--cc=5765@debbugs.gnu.org \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=no-spam@cua.dk \
--cc=storm@cua.dk \
/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).