From: David Kastrup <dak@gnu.org>
Cc: Luc Teirlinck <teirllm@dms.auburn.edu>,
k.stevens@ieee.org, ispell-el-bugs@itcorp.com,
emacs-devel@gnu.org, juri@jurta.org, eliz@gnu.org
Subject: Re: ispell-region with M-$ in transient-mark-mode
Date: Thu, 20 Jan 2005 09:45:10 +0100 [thread overview]
Message-ID: <x5r7kgfq09.fsf@lola.goethe.zz> (raw)
In-Reply-To: <m3y8eo344q.fsf@kfs-l.imdomain.dk> (Kim F. Storm's message of "Thu, 20 Jan 2005 09:18:29 +0100")
storm@cua.dk (Kim F. Storm) writes:
> Luc Teirlinck <teirllm@dms.auburn.edu> writes:
>
>> What is wrong with `C-x C-u'? The region case commands are not used
>> that often that two keystrokes is too much.
>
> Because they are not used very often, it is hard to remember two
> different bindings for upcase.
>
> M-u in a region would mean "upcase every word in the region".
>
> M-$ in a region would mean "ispell every word in the region".
>
> That is simple and intuitive (IMO), at least with
> transient-mark-mode.
I am not so sure about that. It is simple and intuitive if you have
_temporary_ transient-mark-mode enabled, possibly by using the mouse.
In this case we have an explicit act that set up the region. However,
for people that use pc-selection-mode or just transient-mark-mode,
there often is an _unintended_ transient region. I am not so sure
that it is intuitive in that case if it affects the word commands.
Now I am of the opinion that _permanent_ transient-mark-mode and its
cousins are an abomination in user interface design if I ever saw one.
But they are something we _also_ need to think of when saying
something like "at least with transient-mark-mode".
With _temporary_ transient-mark-mode, I share your opinion. But not
with the permanent one.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2005-01-20 8:45 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-18 10:48 ispell-region with M-$ in transient-mark-mode Juri Linkov
2005-01-18 11:42 ` David Kastrup
2005-01-19 0:28 ` Juri Linkov
2005-01-18 19:40 ` Eli Zaretskii
2005-01-19 0:33 ` Juri Linkov
2005-01-19 4:46 ` Eli Zaretskii
2005-01-19 7:46 ` Juri Linkov
2005-01-19 9:06 ` Kim F. Storm
2005-01-19 18:02 ` Eli Zaretskii
2005-01-19 21:30 ` Luc Teirlinck
2005-01-19 22:03 ` Kim F. Storm
2005-01-20 0:19 ` Luc Teirlinck
2005-01-20 8:18 ` Kim F. Storm
2005-01-20 8:45 ` David Kastrup [this message]
2005-01-20 9:44 ` Kim F. Storm
2005-01-21 8:34 ` Kai Großjohann
2005-01-19 17:58 ` Eli Zaretskii
2005-01-20 0:40 ` Luc Teirlinck
2005-01-20 21:32 ` Richard Stallman
2005-01-20 22:00 ` Geoff Kuenning
2005-01-20 22:17 ` David Kastrup
2005-01-20 22:23 ` Geoff Kuenning
2005-01-20 23:11 ` Luc Teirlinck
2005-01-21 16:26 ` Eli Zaretskii
2005-01-22 2:53 ` Richard Stallman
2005-01-20 22:43 ` Luc Teirlinck
2005-01-20 22:36 ` Han Boetes
2005-01-21 20:10 ` Richard Stallman
2005-01-21 20:44 ` Han Boetes
2005-01-21 21:25 ` Luc Teirlinck
2005-01-20 2:14 ` 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=x5r7kgfq09.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=ispell-el-bugs@itcorp.com \
--cc=juri@jurta.org \
--cc=k.stevens@ieee.org \
--cc=teirllm@dms.auburn.edu \
/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).