From: Leo Liu <sdl.web@gmail.com>
To: 22338@debbugs.gnu.org
Subject: bug#22338: 25.0.50; deactivate-mark regression
Date: Mon, 01 Feb 2016 19:02:08 +0800 [thread overview]
Message-ID: <m260y8y9qn.fsf@gmail.com> (raw)
In-Reply-To: <m1si26yd6u.fsf@gmail.com>
On 2016-01-21 18:08 +0200, Eli Zaretskii wrote:
> Would you mind showing a more detailed recipe, including the file you
> used and the exact procedure to change the file behind Emacs's back?
> Also, how do you check that the mark is still active after the revert?
> I feel there are some fine details that are different between our
> attempts to reproduce the issue, because I cannot reproduce it no
> matter what I do. There's some factor here that I don't get. I hope
> it's not some stupid oversight on my part.
I am now using GNU Emacs 25.0.90 built on 2016-01-31 and the problem
seems getting better. My current observation is this (revert-buffer nil
t t) only keeps the active mark if the file has not changed at all but
deactivates it otherwise. I modified the file by appending a line to it
using shell command.
> Well, if we are talking about users, why would a user invoke
> revert-buffer in such a strange way? And if the region is active, but
> not highlighted, doesn't "C-x C-x" show it highlighted?
Obviously not directly. It can be part of a hook. For example I am using
a package to refactor erlang which writes to disk and send emacs the
list of files that may have changed.
HTH,
Leo
next prev parent reply other threads:[~2016-02-01 11:02 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
2016-01-21 10:13 ` Leo Liu
2016-01-21 16:08 ` Eli Zaretskii
2016-02-01 11:02 ` Leo Liu [this message]
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=m260y8y9qn.fsf@gmail.com \
--to=sdl.web@gmail.com \
--cc=22338@debbugs.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).