From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: emacs-devel@gnu.org
Subject: Re: tramp and diff-mode results in Emacs crash
Date: Wed, 28 Feb 2007 10:48:26 -0500 [thread overview]
Message-ID: <jwv3b4qjntd.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87hct73vpw.fsf@stupidchicken.com> (Chong Yidong's message of "Tue\, 27 Feb 2007 20\:40\:59 -0500")
>> - ~/software/emacs22/bin/emacs -q
>> - C-x C-f /10.0.1.169:foo.rej RET
>> - C-c C-u
>>
>> I see only "Back to top level." The diff is unmodified by the
>> command. Menus stop working, C-x C-b says "Back to top level." or
>> nothing, C-x b alternates between "S" and "Back to top level." in the
>> minibuffer without ever letting me change buffers, etc.
> I checked in a fix for this.
> (It's not a great fix, but it's the safest one I could think of. The
> problem arises when combine-after-change-calls is on. The Tramp
> filename handlers can be called (by lock_file) just before Emacs is
> about to combine after-change calls, but those filename handlers can
> themselves produce after-change calls because they scribble in temp
> buffers. It is possible to get Emacs into a confused state in this
> way. I simply made the Tramp handlers bind inhibit-modification-hooks
> to avoid this problem. We may want to revisit the interaction of file
> modification hooks with combine-after-change-calls after the release.)
Maybe the workaround is OK, but I still don't understand what is the bug.
When using combine-after-change-calls, if changes are made in different
buffers, then the after-change-functions are run each time modifications are
done on a different buffer.
Oh, wait, you're saying that the problem is that when
combine-after-change-execute is run it begins by calling lock_file, which
causes more changes? Hmm... I still don't see why that would be a problem.
Can you show some backtraces?
Stefan
next prev parent reply other threads:[~2007-02-28 15:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070222120757.GA28434@morgase.caliginous.net>
[not found] ` <E1HKXaQ-00006I-DL@fencepost.gnu.org>
[not found] ` <20070223235449.GA29688@morgase.caliginous.net>
[not found] ` <E1HLAeR-0008Kg-DI@fencepost.gnu.org>
[not found] ` <20070225052253.GA13725@morgase.caliginous.net>
2007-02-25 19:30 ` tramp and diff-mode results in Emacs crash Richard Stallman
2007-02-25 22:14 ` Dale Sedivec
2007-02-27 21:50 ` Michael Albinus
2007-02-28 1:40 ` Chong Yidong
2007-02-28 15:48 ` Stefan Monnier [this message]
2007-02-28 16:28 ` Chong Yidong
2007-02-28 20:13 ` Stefan Monnier
2007-02-28 22:27 ` Chong Yidong
2007-03-01 5:23 ` Stefan Monnier
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=jwv3b4qjntd.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@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).