From: Reiner Steib <reinersteib+gmane@imap.cc>
To: bug-gnu-emacs@gnu.org
Subject: bug#7854: 24.0.50; Buffer *temp* modified; kill anyway?
Date: Thu, 20 Jan 2011 12:39:48 +0000 (UTC) [thread overview]
Message-ID: <loom.20110120T131450-838@post.gmane.org> (raw)
In-Reply-To: <20110117164327.72fn7tc54w0ks8cs@imap.uni-ulm.de>
Reiner Steib writes:
> The bug happens before I can select the directory, so the specific
> directory doesn't matter.
>
> I neither can reproduce it on GNU/Linux, but on Windows, it is 100%
> reproducible. Any ideas how I can obtain more useful information from
> the debug buffer? Which *.el file should I load?
>
> One more data point: The problem also happens e.g. when starting
> Gnus. My guess is that it happen when Emacs reads a file (.cvsrc,
> ...) into a temp buffer.
After moving ~/.cvsrc away, the bug doesn't happen.
With a 0 byte ~/.cvsrc, the bug doesn't happen.
With this simple .cvsrc, the bug triggers again:
$ cat --show-all ~/.cvsrc
#
(i.e. only one character '#', no CR, no newline).
When I answer "no" at the prompt "Buffer *temp* modified; kill anyway?",
visit the buffer " *temp*", (point-max) is 2, and the mode line shows
iso-latin-1-dos as the coding system.
M-x describe-coding-system shows RET:
| Coding system for saving this buffer:
| Not set locally, use the default.
| Default coding system (for new files):
| 1 -- iso-latin-1-dos (alias: iso-8859-1-dos latin-1-dos)
Bye, Reiner.
next prev parent reply other threads:[~2011-01-20 12:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-17 15:43 bug#7854: 24.0.50; Buffer *temp* modified; kill anyway? Reiner Steib
2011-01-17 21:54 ` Stefan Monnier
2011-01-18 7:15 ` Reiner Steib
2011-01-20 12:39 ` Reiner Steib [this message]
2011-01-20 15:22 ` Stefan Monnier
2011-01-22 12:06 ` Reiner Steib
2011-01-24 20:36 ` Stefan Monnier
2011-02-03 14:12 ` bug#7854: emacs-23 (regression) - fix breaks `dired' (was: bug#7854: 24.0.50; Buffer *temp* modified; kill anyway?) Reiner Steib
2011-02-12 20:20 ` bug#7854: emacs-23 (regression) - fix breaks `dired' Chong Yidong
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=loom.20110120T131450-838@post.gmane.org \
--to=reinersteib+gmane@imap.cc \
--cc=bug-gnu-emacs@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 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.