From: tg@gmplib.org (Torbjörn Granlund)
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Another Emacs incompatibilty
Date: Mon, 17 Aug 2020 22:16:20 +0200 [thread overview]
Message-ID: <86blj9xc2z.fsf@shell.gmplib.org> (raw)
In-Reply-To: <83imdhgsqo.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 17 Aug 2020 19:08:31 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
It would help if you'd tell what changes in how region works you are
alluding to. I use Emacs for the last 30 years, and the way region
works for me didn't change at all, AFAICT. So I'm really puzzled by
what you say here.
Mark a region, immediately press e.g. "A". The region is zapped and
replaced by an A.
That used to insert an A at the insert point since TECO emacs until a
few releases back.
(There is also an implicit mode in the new behavioutr: Only regions just
created exhibit the incompatible zap behavioutr.)
In any case, whenever a backward-incompatible change happens, there's
usually a way, called out in NEWS, to get back old behavior.
How about keeping the accepted interface and document in NEWS how to
make it work in a new, incompatible way?
--
Torbjörn
Please encrypt, key id 0xC8601622
next prev parent reply other threads:[~2020-08-17 20:16 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-16 20:57 Another Emacs incompatibilty Torbjörn Granlund
2020-08-16 21:17 ` Stefan Monnier
2020-08-16 23:02 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-08-17 8:12 ` On the rate of change [was: Another Emacs incompatibilty] tomas
2020-08-17 14:21 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-08-17 15:20 ` tomas
2020-08-17 17:44 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-08-17 15:14 ` Another Emacs incompatibilty Torbjörn Granlund
2020-08-17 15:54 ` Robert Pluim
2020-08-17 16:08 ` Eli Zaretskii
2020-08-17 20:16 ` Torbjörn Granlund [this message]
2020-08-17 20:42 ` Stefan Monnier
2020-08-17 21:22 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-08-17 22:00 ` Gregory Heytings via Users list for the GNU Emacs text editor
2020-08-17 22:18 ` Eric Abrahamsen
2020-08-17 23:00 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-08-18 0:25 ` Eric Abrahamsen
2020-08-18 4:16 ` Stefan Monnier
2020-08-18 4:47 ` Eli Zaretskii
2020-08-18 5:27 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-08-18 5:36 ` Eli Zaretskii
2020-08-23 20:10 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-08-24 6:43 ` Alan Davis
2020-08-24 6:55 ` Eli Zaretskii
2020-08-24 23:21 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-08-24 14:31 ` Drew Adams
2020-08-24 23:24 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-08-25 0:53 ` Alan Davis
2020-08-25 4:09 ` Drew Adams
2020-08-25 4:14 ` Drew Adams
2020-08-25 4:30 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-08-25 5:04 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-08-25 5:46 ` Drew Adams
2020-08-25 6:07 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-08-25 5:51 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-08-24 15:31 ` Stefan Monnier
2020-08-24 23:14 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-08-18 15:47 ` Drew Adams
2020-08-18 16:45 ` Eric Abrahamsen
2020-08-18 16:52 ` Drew Adams
2020-08-18 17:50 ` Eric Abrahamsen
2020-08-18 17:10 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-08-17 16:31 ` Gregory Heytings via Users list for the GNU Emacs text editor
2020-08-17 16:49 ` Perry Smith
2020-08-17 16:54 ` Gregory Heytings via Users list for the GNU Emacs text editor
2020-08-17 17:22 ` Eli Zaretskii
2020-08-17 17:28 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-08-17 17:11 ` Eli Zaretskii
2020-08-17 17:16 ` Emanuel Berg via Users list for the GNU Emacs text editor
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=86blj9xc2z.fsf@shell.gmplib.org \
--to=tg@gmplib.org \
--cc=eliz@gnu.org \
--cc=help-gnu-emacs@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.
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).