unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Leo Liu <sdl.web@gmail.com>
Cc: 22338@debbugs.gnu.org
Subject: bug#22338: 25.0.50; deactivate-mark regression
Date: Sat, 16 Jan 2016 10:24:46 +0200	[thread overview]
Message-ID: <8337tyextd.fsf@gnu.org> (raw)
In-Reply-To: <m1si26yd6u.fsf@gmail.com> (message from Leo Liu on Sat, 09 Jan 2016 23:39:37 +0800)

> From: Leo Liu <sdl.web@gmail.com>
> Date: Sat, 09 Jan 2016 23:39:37 +0800
> 
> 1. Emacs -q
> 2. Open a file and mark an active region
> 3. (revert-buffer nil t t)
> 
> The mark is still active after the buffer revert. This isn't the case
> for emacs 24.5.

When I try this with different files and different changes actually
made to the file behind Emacs's back, I see the region deactivate
every time I revert and the file on disk was really changed.  Maybe it
doesn't always deactivate the region, but it certainly doesn't always
keep it active, except when the file on disk didn't change at all.

Do you really see the region remain active every revert, no matter
what the changes to the file on disk?  Can you show a detailed recipe
for that?

Anyway, since the documentation never says what will happen with the
region, I tend to consider this behavior unspecified: why should Lisp
programs expect anything specific to happen to the region during a
revert?

> The trouble is if the file has changed on disk (e.g. by another process
> such as vim), the mark is still active after the revert.

Why is that trouble?

Thanks.





  reply	other threads:[~2016-01-16  8:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-09 15:39 bug#22338: 25.0.50; deactivate-mark regression Leo Liu
2016-01-16  8:24 ` Eli Zaretskii [this message]
2016-01-21 10:13   ` Leo Liu
2016-01-21 16:08     ` Eli Zaretskii
2016-02-01 11:02       ` Leo Liu
2016-02-01 19:08         ` Eli Zaretskii
2016-02-02  1:36           ` Leo Liu
2016-02-16  7:06             ` Lars Ingebrigtsen
2016-02-16  7:27               ` Leo Liu
2016-02-18 10:14                 ` Leo Liu
2016-02-19 21:00                   ` Eli Zaretskii
2022-02-15 10:45                     ` Lars Ingebrigtsen

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=8337tyextd.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=22338@debbugs.gnu.org \
    --cc=sdl.web@gmail.com \
    /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).