unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Miles Bader <miles@lsi.nec.co.jp>
Cc: Juanma Barranquero <lektu@terra.es>,
	rms@gnu.org, Takaaki.Ota@am.sony.com, emacs-devel@gnu.org
Subject: Re: keymap in yank-excluded-properties
Date: 04 Sep 2002 17:02:17 +0900	[thread overview]
Message-ID: <buok7m2ji7q.fsf@mcspd15.ucom.lsi.nec.co.jp> (raw)
In-Reply-To: <5xznuyjg87.fsf@kfs2.cua.dk>

storm@cua.dk (Kim F. Storm) writes:
> > > [I guess CUA mode already has something like this, but it'd be nice to
> > > have it for everyone.]
> > 
> > It'd be cool to be able to use the wonderful rectangle support from CUA
> > mode without having to activate all the rest.
> 
> Isn't that exactly what you get by setting cua-enable-cua-keys to nil ?
> If not, what's wrong with it?

It still leaves other wierd CUA stuff enabled, e.g., shift-key-selection
(maybe that's what Juanma wants but I don't).

Also, it's quite ugly to have to explicitly disable parts of CUA mode
and then turn on CUA mode to get nice rectangle support -- as far as I
can tell there's no _reason_ to intertwine the two except history.

It would be cleaner to have two separate modes, with CUA using rectangle
mode if appropriate (is it?  I almost never use a real CUA system, so I
don't know if they have such a thing...).  [and also for other cua
features that probably should as well; I don't remember which ones there
are, but we discussed this a while ago.]

Of course it would take some work to disentangle them, and I'm not
suggesting that you have to do it... but it would be nice if someone
did.  :-)

-miles
-- 
`Cars give people wonderful freedom and increase their opportunities.
 But they also destroy the environment, to an extent so drastic that
 they kill all social life' (from _A Pattern Language_)

  reply	other threads:[~2002-09-04  8:02 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-23  0:31 keymap in yank-excluded-properties Tak Ota
2002-08-23  1:55 ` Miles Bader
2002-08-23 22:21   ` Tak Ota
2002-08-23 22:29     ` Stefan Monnier
2002-08-23 23:04       ` Tak Ota
2002-08-23  9:52 ` Kim F. Storm
2002-08-25  5:25 ` Richard Stallman
2002-08-25 22:49   ` Kim F. Storm
2002-08-30 19:43     ` Tak Ota
2002-09-01 13:14       ` Richard Stallman
2002-09-02 15:02         ` Kim F. Storm
2002-09-03 13:26           ` Richard Stallman
2002-09-03 20:36             ` Tak Ota
2002-10-23 13:53               ` Kim F. Storm
2002-10-24 20:27                 ` Tak Ota
2002-09-04  1:11           ` Miles Bader
2002-09-04  6:32             ` Juanma Barranquero
2002-09-04  8:45               ` Kim F. Storm
2002-09-04  8:02                 ` Miles Bader [this message]
2002-09-04  8:50                   ` Juanma Barranquero
2002-09-04  8:49                 ` Juanma Barranquero
2002-09-04 12:48                   ` Kim F. Storm
2002-09-04 14:10                     ` Juanma Barranquero
2002-09-04 10:34                 ` Per Abrahamsen
2002-09-04 12:35                   ` Kim F. Storm
2002-09-05  1:10                     ` Miles Bader
2002-09-05 13:18                       ` Robert J. Chassell
2002-09-05 15:00                         ` Kim F. Storm
2002-09-05 14:34                           ` Per Abrahamsen
2002-09-05 15:15                           ` Robert J. Chassell
2002-09-06  1:09                           ` Miles Bader
2002-09-05  2:46             ` Richard Stallman
2002-09-05 14:48               ` Robert J. Chassell
2002-09-06  1:05                 ` Miles Bader
2002-09-06 11:30                   ` Andreas Schwab
2002-09-06 11:57                   ` Modes: major, minor, context specific Robert J. Chassell
2002-09-06 20:03                   ` keymap in yank-excluded-properties Richard Stallman
2002-09-01 13:15     ` Richard Stallman

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=buok7m2ji7q.fsf@mcspd15.ucom.lsi.nec.co.jp \
    --to=miles@lsi.nec.co.jp \
    --cc=Takaaki.Ota@am.sony.com \
    --cc=emacs-devel@gnu.org \
    --cc=lektu@terra.es \
    --cc=miles@gnu.org \
    --cc=rms@gnu.org \
    /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).