From: Lennart Borgman <lennart.borgman@gmail.com>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: 5765@debbugs.gnu.org, "Kim F. Storm" <no-spam@cua.dk>,
emacs-devel@gnu.org, "Kim F. Storm" <storm@cua.dk>
Subject: bug#5765: Strange things happens with C-v in read-file-name
Date: Thu, 29 Apr 2010 17:45:12 +0200 [thread overview]
Message-ID: <g2oe01d8a51004290845na9909469x5cc5e7d3ce540810__4022.89985581792$1272556560$gmane$org@mail.gmail.com> (raw)
In-Reply-To: <8739ye1d08.fsf@stupidchicken.com>
On Thu, Apr 29, 2010 at 5:42 PM, Chong Yidong <cyd@stupidchicken.com> wrote:
> no-spam@cua.dk (Kim F. Storm) writes:
>
>>> Nothing happened to this so I am sending this again. Could this please
>>> be fixed before the release?
>>>
>>> Kim, could you perhaps comment on this? Could the line
>>>
>>> (setq cua-inhibit-cua-keys t)
>>>
>>> be removed?
>>
>> IIRC, the reason for this was the following binding in ido file mode:
>>
>> (define-key map "\C-v" 'ido-toggle-vc)
>>
>> If cua-mode is enabled, C-v is processed by cua (as paste), shadowing the
>> above command.
>>
>> I guess nobody really uses that specific feature of ido.
>> I used to use it a lot back when I wrote ido, but never uses it these days.
>>
>> So the best thing to do would be to remove the above binding - then you
>> can also remove the setting of cua-inhibit-cua-keys.
>
> Done.
>
> (In the trunk, not in the branch; this is not serious enough to make an
> exception to the regressions-only policy).
Thanks.
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.)
next prev parent reply other threads:[~2010-04-29 15:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <e01d8a51001271416i56a286ffy983fbca024284e75@mail.gmail.com>
2010-02-02 12:23 ` bug#5511: Strange things happens with C-v in read-file-name Lennart Borgman
2010-03-24 12:37 ` Lennart Borgman
2010-03-24 17:09 ` bug#5765: " Chong Yidong
[not found] ` <87eij9r6hu.fsf@stupidchicken.com>
2010-03-24 18:28 ` Lennart Borgman
[not found] ` <e01d8a51003241128x60fc5a2g5322c71225a4aa2e@mail.gmail.com>
2010-03-24 20:44 ` Chong Yidong
[not found] ` <87iq8l1mbc.fsf@stupidchicken.com>
2010-03-25 1:17 ` Lennart Borgman
[not found] ` <e01d8a51003241817u2ac17846mf370517dfdec5bfe@mail.gmail.com>
2010-04-29 1:23 ` Lennart Borgman
[not found] ` <o2ke01d8a51004281823t88e495f8t18e175956941a684@mail.gmail.com>
2010-04-29 11:37 ` Kim F. Storm
[not found] ` <877hnqpk08.fsf@kfs-lx.rd.rdm>
2010-04-29 15:42 ` Chong Yidong
[not found] ` <8739ye1d08.fsf@stupidchicken.com>
2010-04-29 15:45 ` Lennart Borgman [this message]
[not found] ` <g2oe01d8a51004290845na9909469x5cc5e7d3ce540810@mail.gmail.com>
2010-04-29 22:51 ` Stefan Monnier
[not found] ` <jwv6339q3d3.fsf-monnier+emacs@gnu.org>
2010-04-29 23:54 ` Lennart Borgman
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='g2oe01d8a51004290845na9909469x5cc5e7d3ce540810__4022.89985581792$1272556560$gmane$org@mail.gmail.com' \
--to=lennart.borgman@gmail.com \
--cc=5765@debbugs.gnu.org \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--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).