From: Karl Kleinpaste <karl@jprc.com>
Subject: *scratch* buffer modeline wrong after exit
Date: 26 Nov 1997 09:31:28 -0500 [thread overview]
Message-ID: <vxkn2irk9q7.fsf@pocari-sweat.jprc.com> (raw)
I'm sending this note on Lars' request/suggestion, after a `C-c C-b'
bug report of mine proved not to be reliably reproducible.
In q0.15 and q0.16, I am irregularly encountering the bizarre effect
that, upon exit from Gnus, my modeline looks like this:
--** [gnus glyph] *scratch* [0] {1 more} (Lisp Interaction)-----L1--All---
Note the *Summary*-style bits that remain in a *scratch* buffer. Note
also that the buffer claims to be modified, though attempting to
execute `undo' fails, with a complaint that no more undo info is
available.
If I start killing buffers with `C-x C-k', eventually *scratch* is
reconstituted and has a normal modeline, lacking the gnus glyph and
summary counters.
As for the circumstance which leads to this error, I am not sure
precisely what it is that does this. I have tried:
1. Both M-x gnus and M-x gnus-no-server.
2. Exiting immediately after start.
3. Reading entirely through a couple groups until they show no unread
articles.
4. Reading partially through a group so that some unread articles
remain.
5. Sending (and not sending) replies to articles being seen.
So far, I have no reliably reproducible circumstance. It seems to
happen (guestimating) about 1-in-5 exits from Gnus.
Is anyone else seeing this in the most recent release or two?
My configuration:
XEmacs 19.16 under Linux (recent RH).
I change gnus-{group,summary,tree}-line-format, but have no
customizations regarding modelines.
All my customization is in .emacs; I don't use .gnus at all.
Clues, or at least corroborating failures, would be most welcome.
--karl
next reply other threads:[~1997-11-26 14:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-11-26 14:31 Karl Kleinpaste [this message]
1997-11-26 16:20 ` Dan Christensen
1997-11-26 16:30 ` Karl Kleinpaste
1997-11-26 18:30 ` Lars Magne 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=vxkn2irk9q7.fsf@pocari-sweat.jprc.com \
--to=karl@jprc.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.
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 NNTP newsgroup(s).