From: "Drew Adams" <drew.adams@oracle.com>
To: "'Lennart Borgman'" <lennart.borgman@gmail.com>,
"'Kim F. Storm'" <storm@cua.dk>
Cc: Help-gnu-emacs@gnu.org, 'Dirk80' <dirk@dirkundsari.de>
Subject: RE: C-Ret: cua and icicles
Date: Mon, 24 May 2010 15:08:23 -0700 [thread overview]
Message-ID: <31B7D5DF50C84ECE9ACA11AC1914C8F8@us.oracle.com> (raw)
In-Reply-To: <AANLkTilcHwmPIOs5N7k-VaalyKTxFS9Dd0QrTHc_q6Ag@mail.gmail.com>
Listen, I am not trying to say anything about how CUA mode should be
implemented. I only questioned whether it really should make C-RET in the
minibuffer be `cua-set-rectangle-mark' (which question you snipped). I cannot
say it should or should not, since I don't use CUA mode and am no expert on it.
I just raised the question based on the command name: I don't imagine rectangles
in the minibuffer (but why not?).
> > (since CUA-mode lays hold C-RET ubiquitously).
>
> I think that is a problem. It is used to start rectangle editing which
> surely is a nice feature for those who needs it, but it is IMO not
> important enough to steel the C-RET key. You can customize it in cua,
> but I think the default should be some less important key.
>
> And this is part of cua-mode just because Kim wrote it ;-)
>
> It is nice but not included in what I talk about when I mention
> cua-mode. I think it should be moved to a global minor mode on its own
> (not an emulation minor mode).
That may be (or not be). It's not for me to say. Whether C-RET should be bound
by CUA mode by default or included in CUA mode at all is a different question.
I did not question that. That apparently is your topic (not mine or the OP's).
I just asked whether - assuming it _should_ bind C-RET in general, that binding
is also appropriate for the minibuffer. And that too is not for me to say - I
do not know.
I am in no way objecting to the CUA design or how it is implemented. I simply
tried to reply to your comment that Icicles should automatically take care of
the kind of customization that the user wanted. I hope I was clear.
> > The only way to take back C-RET for the minibuffer is to
> > remap the CUA-imposed command to a command that DTRT,
> > distinguishing the minibuffer. Fortunately, it
> > is trivial for an Icicles user to do that using Customize.
>
> You can customize the binding in cua-mode too. That is what I
> have done.
Your point was that users should not have to deal with such customization, that
"Icicles should of course try to do this, not you". Now you are saying that a
user can take care of it himself by customizing cua-mode. That's no doubt good
for users to know, but it does not speak to your point.
> cua-mode should NOT do that but the key and command we are talking
> about should not be in cua-mode.
>
> I think all who knows about cua-mode on the devel list are aware of
> this. It is just a matter of time, someone must have time to fix it. I
> have included Kim in the receivers here if he has a different opinion.
Dunno, but it seems to me you've sidetracked the thread. The OP just wanted to
let others know about a simple customization to be able to use C-RET for Icicles
in the minibuffer while still using CUA mode. You stated that Icicles should do
that for him. I tried to explain the interaction among the keymaps etc. Now
you're onto another question for CUA development of whether C-RET should even be
part of CUA mode. What's next?
next prev parent reply other threads:[~2010-05-24 22:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-22 11:07 C-Ret: cua and icicles Dirk80
2010-05-22 15:35 ` Drew Adams
2010-05-24 19:54 ` Dirk80
2010-05-24 20:02 ` Lennart Borgman
2010-05-24 21:22 ` Drew Adams
2010-05-24 21:46 ` Lennart Borgman
2010-05-24 22:08 ` Drew Adams [this message]
2010-05-24 22:33 ` Lennart Borgman
2010-05-24 22:53 ` Drew Adams
2010-05-24 23:06 ` Lennart Borgman
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=31B7D5DF50C84ECE9ACA11AC1914C8F8@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=Help-gnu-emacs@gnu.org \
--cc=dirk@dirkundsari.de \
--cc=lennart.borgman@gmail.com \
--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.
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).