From: Ralf Angeli <dev.null@iwi.uni-sb.de>
Subject: Re: Flags/marks not being updated
Date: Mon, 28 Jun 2004 14:41:08 +0200 [thread overview]
Message-ID: <cbp3kd$4so$1@sea.gmane.org> (raw)
In-Reply-To: <ilusmcfzyrc.fsf@latte.josefsson.org>
* Simon Josefsson (2004-06-28) writes:
> Ralf Angeli <dev.null@iwi.uni-sb.de> writes:
>
>> Under certain circumstances flags or marks are not being updated
>> anymore.
[...]
>> Looking through lisp/ChangeLog I saw that in midth May some new code
>> related to marks was checked in and the default of
>> `gnus-agent-synchronize-flags' was set to nil. So I tried to
>> synchronize the flags manually by issueing J-Y in the group buffer
>> but this produced an error with the following backtrace:
>>
>> Debugger entered--Lisp error: (wrong-type-argument stringp nil)
[...]
> Does it help to (setq gnus-agent-synchronize-flags 'ask)?
Yes, this helps. I thought that I would get the error mentioned
above if I set it to 'ask, so I didn't check it. (c% Thank you!
> I really
> think that value should be the default, as you will lose flags with a
> `nil' setting. I don't know/understand why the default was changed.
What I find interesting is that after setting it to 'ask, Gnus is
actually asking for the synchronization. I don't recall that I ever
had to answer such a question before, even when the default was 'ask.
Before all the strange behavior started, Gnus only asked if I would
like to switch servers into online status upon typing J-j; no
synchronization question. (I know that I can set it to t in order to
suppress the question.)
> The bug yielding the backtrace should be fixed independently of this,
> though.
Maybe it helps if I add that I issued J-Y with the agent in unplugged
state.
--
Ralf
next prev parent reply other threads:[~2004-06-28 12:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-28 10:32 Ralf Angeli
2004-06-28 11:51 ` Simon Josefsson
2004-06-28 12:41 ` Ralf Angeli [this message]
2004-06-28 16:09 ` Simon Josefsson
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='cbp3kd$4so$1@sea.gmane.org' \
--to=dev.null@iwi.uni-sb.de \
--cc=angeli@iwi.uni-sb.de \
/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).