From: Richard Stallman <rms@gnu.org>
Cc: juri@jurta.org, occitan@esperanto.org, monnier@iro.umontreal.ca,
emacs-devel@gnu.org
Subject: Re: Changes to emacs/lisp/progmodes/grep.el
Date: Sat, 03 Jul 2004 14:20:47 -0400 [thread overview]
Message-ID: <E1Bgp83-0003bM-IQ@fencepost.gnu.org> (raw)
In-Reply-To: <x53c4b70xo.fsf@lola.goethe.zz> (message from David Kastrup on 02 Jul 2004 01:38:43 +0200)
"GUI-happy" users are mostly surprised of its stickiness: they tend
to expect that it is just active when you mark regions with a mouse,
or use a special marking sequence.
We are getting closer with temporary transient-mark-mode on
mouse-drag, but I don't think we are "there" yet with regard to
"expected" behavior.
Can you name some specific "unexpected" behaviors that we
might look for ways to change?
But the "expected behavior" for such users is that both
region-beginning and region-end are independent from point, so it's
a non-trivial change.
That does sound thoroughly incompatible with Emacs. However, the
programs I've seen don't seem to cancel the selection when you move
point. That would not be difficult, and is what we now do
after a mouse drag.
next prev parent reply other threads:[~2004-07-03 18:20 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1BdGt8-0003Tg-Qb@lists.gnu.org>
2004-06-24 23:16 ` Changes to emacs/lisp/progmodes/grep.el Juri Linkov
2004-06-25 20:03 ` Daniel Pfeiffer
2004-06-26 0:03 ` Juri Linkov
2004-06-27 10:43 ` Daniel Pfeiffer
2004-06-26 6:03 ` Richard Stallman
2004-06-27 10:33 ` Daniel Pfeiffer
2004-06-27 11:58 ` Adrian Aichner
2004-06-28 2:23 ` Richard Stallman
2004-06-28 2:37 ` Miles Bader
2004-06-28 4:44 ` David Kastrup
2004-06-28 8:40 ` Daniel Pfeiffer
2004-06-28 18:00 ` Eli Zaretskii
2004-06-28 21:22 ` Daniel Pfeiffer
2004-06-29 5:10 ` Eli Zaretskii
2004-06-29 20:08 ` Daniel Pfeiffer
2004-06-29 21:19 ` Eli Zaretskii
2004-06-30 5:16 ` Juri Linkov
2004-07-01 22:20 ` Daniel Pfeiffer
2004-06-30 5:08 ` Juri Linkov
2004-07-02 21:58 ` Daniel Pfeiffer
2004-07-01 23:31 ` Stefan
2004-07-01 23:38 ` David Kastrup
2004-07-01 23:46 ` Stefan
2004-07-03 18:20 ` Richard Stallman [this message]
2004-07-04 10:47 ` Mark handling (Was: Changes to emacs/lisp/progmodes/grep.el) Daniel Pfeiffer
2004-07-05 16:56 ` Richard Stallman
2004-07-05 19:57 ` Daniel Pfeiffer
2004-07-06 22:00 ` Richard Stallman
2004-07-07 19:47 ` Daniel Pfeiffer
2004-07-08 23:18 ` Richard Stallman
2004-07-10 19:54 ` Daniel Pfeiffer
2004-07-06 22:00 ` Richard Stallman
2004-07-07 20:58 ` Richard Stallman
2004-07-02 0:20 ` Transient mark mode (was: " Paul Pogonyshev
2004-07-03 8:28 ` Changes to emacs/lisp/progmodes/grep.el Daniel Pfeiffer
2004-07-02 9:07 ` Juri Linkov
2004-07-03 11:35 ` Daniel Pfeiffer
2004-07-02 8:48 ` Juri Linkov
2004-07-06 16:55 ` Juri Linkov
2004-07-06 18:16 ` Luc Teirlinck
2004-07-07 20:57 ` Richard Stallman
2004-06-30 18:52 ` Richard Stallman
2004-07-01 5:08 ` Juri Linkov
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=E1Bgp83-0003bM-IQ@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=juri@jurta.org \
--cc=monnier@iro.umontreal.ca \
--cc=occitan@esperanto.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).