Gnus development mailing list
 help / color / mirror / Atom feed
From: Dave Abrahams <dave@boostpro.com>
To: Tassilo Horn <tassilo@member.fsf.org>
Cc: ding@gnus.org, John Wiegley <johnw@boostpro.com>
Subject: [Workaround/Solved] This bug is killing me!
Date: Tue, 30 Aug 2011 01:33:52 -0800	[thread overview]
Message-ID: <m2bov7jla7.fsf_-_@boostpro.com> (raw)
In-Reply-To: <87pqjnqt5k.fsf@thinkpad.tsdh.de> (Tassilo Horn's message of "Tue, 30 Aug 2011 09:01:59 +0200")


[long story short, you _need_ gnus-propagate-marks on]

on Mon Aug 29 2011, Tassilo Horn <tassilo-AT-member.fsf.org> wrote:

> Dave Abrahams <dave@boostpro.com> writes:
>
> Hi Dave,
>
>> This is very serious: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=9386GNU> As an emergency workaround, I've rebound `M-g' to `gnus-summary-exit'.
>> And a friend of mine remarked,
>>
>> ,----
>> | I never, ever, use M-g within a summary buffer.  I have seen enough
>> | unpredictable behavior with it through the years that I instinctively stopped
>> | trusting it.  Nowadays I exit the summary buffer, hit 'g', then go back in.
>> `----
>
> Strange, I use M-g quite frequently and never had problems.  Concerning
> your bug report, I've just ticked your article and hit M-g.  What I got
> was a summary with your still ticked article plus the other unread
> articles.  That's how it's supposed to work.
>
> Reading your bug report, it seems that the mark is not propagated to the
> server.  But even in that case, the mark should be stored locally (in
> .newsrc.eld or whatever variable holds the marks at runtime).  So
> probably the local marks not saved before exiting summary while
> propagating marks to the remote server is done immediately, which would
> explain your issue and why it works for me.
>
> Could you check if it works for you if you enable propagating marks?

Yes, it works!!  Not only that, but all the ticks on older articles that
used to persist in Gnus, but had suddenly disappeared from Gnus' view of
my server came back!

> BTW: I think, that the default of this variable should be t nowadays,
> where it's pretty common that people use different clients for accessing
> their mail (Gnus on "real" computers, Whatever on their phones, the web
> interfaces of their mail providers, etc.).

OMG, yes, please!!!

-- 
Dave Abrahams
BoostPro Computing
http://www.boostpro.com



  parent reply	other threads:[~2011-08-30  9:33 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-29 21:51 Dave Abrahams
2011-08-30  7:01 ` Tassilo Horn
2011-08-30  9:27   ` Robert Pluim
2011-08-30 10:12     ` Tassilo Horn
2011-08-30  9:33   ` Dave Abrahams [this message]
2011-08-30 10:18     ` [Workaround/Solved] " Tassilo Horn
2011-08-30 10:33       ` Dave Abrahams
2011-08-30 11:20         ` Tassilo Horn
2011-08-30 18:09           ` Dave Abrahams
2011-08-30 18:17             ` Tassilo Horn
2011-09-10 21:59         ` Lars Magne Ingebrigtsen
2011-08-30 10:39       ` Dave Abrahams
2011-08-30 11:50         ` Tassilo Horn
2011-08-30 18:40           ` Dave Abrahams
2011-08-30 15:04     ` James Cloos
2011-08-30 19:02       ` Dave Abrahams
2011-08-30 19:19         ` Tassilo Horn
2011-08-30 19:53           ` Dave Abrahams
2011-08-30 22:07           ` [The saga continues...] " Dave Abrahams
2011-09-10 22:01             ` Lars Magne Ingebrigtsen
2011-08-30 21:36         ` [Workaround/Solved] " James Cloos
2011-08-31  6:40           ` Dave Abrahams
2011-08-31  7:51           ` Tassilo Horn
2011-08-31  8:27             ` James Cloos
2011-08-31 16:51 ` Andrew Cohen
2011-08-31 19:49   ` Dave Abrahams
2011-08-31 20:05     ` Andrew Cohen
2011-09-10 22:01   ` Lars Magne Ingebrigtsen
2011-09-10 22:12     ` Andrew Cohen
2011-09-10 22:11       ` 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=m2bov7jla7.fsf_-_@boostpro.com \
    --to=dave@boostpro.com \
    --cc=ding@gnus.org \
    --cc=johnw@boostpro.com \
    --cc=tassilo@member.fsf.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.
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).