all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Ryan Johnson <scovich@gmail.com>
Cc: 25119@debbugs.gnu.org
Subject: bug#25119: Acknowledgement (Hard freeze when switching to indirect buffer)
Date: Mon, 05 Dec 2016 22:25:10 +0200	[thread overview]
Message-ID: <83h96ijf89.fsf@gnu.org> (raw)
In-Reply-To: <ed6399fe-484b-e939-f116-f37dd284224e@gmail.com> (message from Ryan Johnson on Mon, 5 Dec 2016 13:14:59 -0700)

> Cc: 25119@debbugs.gnu.org
> From: Ryan Johnson <scovich@gmail.com>
> Date: Mon, 5 Dec 2016 13:14:59 -0700
> 
> > This looks like Emacs asking you whether to steal the lock from
> > another Emacs session that is editing the same file.
> The message from the lisp backtrace was:
> > AlphaTree.cpp changed on disk; really edit the buffer? (y, n, r or C-h)
> 
> I'm pretty sure the lock-stealing message is rather different from that, 
> mentioning the PID of the other emacs... but I don't remember off the 
> top of my head because I very rarely point two emacsen at the same file.

No, I think you are right, it's the message saying that the file on
disk changed by some other program.  It could be that we somehow goof
with indirect buffers in that case.





  reply	other threads:[~2016-12-05 20:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-05 16:46 bug#25119: Hard freeze when switching to indirect buffer Ryan Johnson
     [not found] ` <handler.25119.B.148095640113649.ack@debbugs.gnu.org>
2016-12-05 17:37   ` bug#25119: Acknowledgement (Hard freeze when switching to indirect buffer) Ryan Johnson
2016-12-05 18:44     ` Eli Zaretskii
2016-12-05 20:14       ` Ryan Johnson
2016-12-05 20:25         ` Eli Zaretskii [this message]
2016-12-08  2:00         ` Ryan Johnson
2018-05-09 23:12           ` bug#25119: Hard freeze when switching to indirect buffer Noam Postavsky

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83h96ijf89.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=25119@debbugs.gnu.org \
    --cc=scovich@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.