* stale summary buffer after reading message
@ 2010-10-08 22:50 Mario Peter
2010-10-09 16:08 ` Lars Magne Ingebrigtsen
0 siblings, 1 reply; 5+ messages in thread
From: Mario Peter @ 2010-10-08 22:50 UTC (permalink / raw)
To: ding
Hello all,
when I close a summary buffer after reading a message, gnus leaves an
empty, writable summary buffer, which gets reused when selecting and
re-entering the group again. I have to kill the buffer to be able to
enter the group. Only entering the group without reading any message works
fine. This issue occurs on all backends. Gnus is recent from git.
Does anybody have the same behavior or can help me wth this issue?
Mario
--
Mario Peter
de,pl,en
http://www.mpeter.de
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: stale summary buffer after reading message
2010-10-08 22:50 stale summary buffer after reading message Mario Peter
@ 2010-10-09 16:08 ` Lars Magne Ingebrigtsen
2010-10-10 21:19 ` Mario Peter
0 siblings, 1 reply; 5+ messages in thread
From: Lars Magne Ingebrigtsen @ 2010-10-09 16:08 UTC (permalink / raw)
To: ding
Mario Peter <empee0@googlemail.com> writes:
> when I close a summary buffer after reading a message, gnus leaves an
> empty, writable summary buffer, which gets reused when selecting and
> re-entering the group again.
Do you have `gnus-kill-summary-on-exit' set to nil?
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: stale summary buffer after reading message
2010-10-09 16:08 ` Lars Magne Ingebrigtsen
@ 2010-10-10 21:19 ` Mario Peter
2010-10-11 18:02 ` Lars Magne Ingebrigtsen
0 siblings, 1 reply; 5+ messages in thread
From: Mario Peter @ 2010-10-10 21:19 UTC (permalink / raw)
To: ding
2010/10/9 Lars Magne Ingebrigtsen <larsi@gnus.org>:
> Mario Peter <empee0@googlemail.com> writes:
>
>> when I close a summary buffer after reading a message, gnus leaves an
>> empty, writable summary buffer, which gets reused when selecting and
>> re-entering the group again.
>
> Do you have `gnus-kill-summary-on-exit' set to nil?
no, gnus-kill-summary-on-exit is t
Mario
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: stale summary buffer after reading message
2010-10-10 21:19 ` Mario Peter
@ 2010-10-11 18:02 ` Lars Magne Ingebrigtsen
2010-10-31 22:10 ` Mario Peter
0 siblings, 1 reply; 5+ messages in thread
From: Lars Magne Ingebrigtsen @ 2010-10-11 18:02 UTC (permalink / raw)
To: ding
Mario Peter <empee0@googlemail.com> writes:
> no, gnus-kill-summary-on-exit is t
Looking through `gnus-summary-exit', the summary buffer is killed.
Perhaps you have some hooks running (or other code) that re-creates the
summary buffer?
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: stale summary buffer after reading message
2010-10-11 18:02 ` Lars Magne Ingebrigtsen
@ 2010-10-31 22:10 ` Mario Peter
0 siblings, 0 replies; 5+ messages in thread
From: Mario Peter @ 2010-10-31 22:10 UTC (permalink / raw)
To: ding
On Oct 11 2010, 20:02, Lars Magne Ingebrigtsen <larsi@gnus.org> wrote:
> Mario Peter <empee0@googlemail.com> writes:
>
>> no, gnus-kill-summary-on-exit is t
>
> Looking through `gnus-summary-exit', the summary buffer is killed.
>
> Perhaps you have some hooks running (or other code) that re-creates the
> summary buffer?
i've found the problem finally , i used an old version of tabbar.el,
what seemed to hold the buffer. Now everything works fine.
Mario
--
Mario Peter
de,pl,en
http://www.mpeter.de
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2010-10-31 22:10 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-10-08 22:50 stale summary buffer after reading message Mario Peter
2010-10-09 16:08 ` Lars Magne Ingebrigtsen
2010-10-10 21:19 ` Mario Peter
2010-10-11 18:02 ` Lars Magne Ingebrigtsen
2010-10-31 22:10 ` Mario Peter
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).