Gnus development mailing list
 help / color / mirror / Atom feed
From: Karl Kleinpaste <karl@jprc.com>
Subject: Re: *scratch* buffer modeline wrong after exit
Date: 26 Nov 1997 11:30:47 -0500	[thread overview]
Message-ID: <vxkk9dvk47c.fsf@pocari-sweat.jprc.com> (raw)
In-Reply-To: Karl Kleinpaste's message of "26 Nov 1997 09:31:28 -0500"

An addendum to my previous observations:

The extraneous modeline bits get dumped on whatever buffer is lying
around to be picked up as "current" when Gnus exits.  It doesn't seem
to matter at all whether it's *scratch*, .emacs, foo.c, or anything else.

Also, maybe it's my imagination, but it seems to me that there's an
inordinately long pause at exit, between the saving of .newsrc.eld and
the removal of the *Group* buffer, returning to whatever buffer is
underneath, now with a screwed modeline.  But I can't say I noticed
this pause much until this morning, so I can't say whether this is new
in 0.15 or 0.16, versus previous behavior from 0.14 (when the modeline
damage was not occurring).

--karl


  parent reply	other threads:[~1997-11-26 16:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-11-26 14:31 Karl Kleinpaste
1997-11-26 16:20 ` Dan Christensen
1997-11-26 16:30 ` Karl Kleinpaste [this message]
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=vxkk9dvk47c.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).