all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Stefan Monnier'" <monnier@iro.umontreal.ca>
Cc: 10382@debbugs.gnu.org
Subject: bug#10382: 24.0.92; gratuituous `file-supersession' error for `menu-bar-update-hook'
Date: Mon, 16 Jan 2012 08:22:31 -0800	[thread overview]
Message-ID: <C1443239335F4D3DAE1115CC893FC1F3@us.oracle.com> (raw)
In-Reply-To: <jwv39bf6372.fsf-monnier+emacs@gnu.org>

> I think we'll need a backtrace at the time of the "really edit
> the buffer?" prompt in order to debug this.  Tho, I suspect 
> it won't be easy to get one since this is in the middle of 
> menu-bar-update-hook, so redisplay might be inhibited.

Right.  I don't know how to obtain that.  And as I said, this does not seem to
happen all the time.

Perhaps it would be more helpful to take a look at recent changes to the code.
Perhaps the code which issues this "file supersession" prompt (I've never seen
that before) or the revert code.  Dunno.

Or perhaps the display code?  One question is why I do not see the message, and
Emacs seems to hang, until I hit C-g.  It is only after canceling out of the
(presumed) revert-confirmation dialog that I can see the prompt for that
confirmation.

And why I would be prompted at all when I use this no-confirmation command is
another question.  (revert-buffer t t) should not be asking for confirmation.






  reply	other threads:[~2012-01-16 16:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-27 21:41 bug#10382: 24.0.92; gratuituous `file-supersession' error for `menu-bar-update-hook' Drew Adams
2011-12-27 21:44 ` Drew Adams
2012-01-16  0:03 ` Drew Adams
2012-01-16 16:11   ` Stefan Monnier
2012-01-16 16:22     ` Drew Adams [this message]
2012-01-16 21:37       ` Stefan Monnier
2014-02-10  5:02       ` Lars Ingebrigtsen
2015-12-25 23:13         ` 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

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

  git send-email \
    --in-reply-to=C1443239335F4D3DAE1115CC893FC1F3@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=10382@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.