From: Kevin Greiner <kevin.greiner@vignette.com>
Subject: Re: Gnus losing information about what has been read
Date: Thu, 23 Sep 2004 08:28:34 -0500 [thread overview]
Message-ID: <u4qlpazct.fsf@vignette.com> (raw)
In-Reply-To: <citvm1$qj7$1@sea.gmane.org>
Ralf Angeli <dev.null@iwi.uni-sb.de> writes:
> * Kevin Greiner (2004-09-23) writes:
>
>> My patch was defective. I had tested physical unplugging rather than
>> gnus "unplugged". I've updated gnus-int.el again.
>
> Now the marks are updated correctly. Thank you very much.
>
> I don't know if it is related to your patch, but I get an error after
> changing to "Unplugged" state, entering a group, reading some articles
> and trying to leave the group with `q'. Here is the backtrace:
>
> Debugger entered--Lisp error: (wrong-type-argument stringp nil)
> expand-file-name(nil "/home/angeli/News/marks/news.individual.net/de/comp/text/tex/")
> nntp-open-marks("de.comp.text.tex" "news.individual.net")
> nntp-request-set-mark("de.comp.text.tex" (((172683) add (read))) "news.individual.net")
> gnus-request-set-mark("nntp+news.individual.net:de.comp.text.tex" (((172683) add (read))))
> gnus-update-read-articles("nntp+news.individual.net:de.comp.text.tex" nil)
> gnus-summary-update-info()
> gnus-summary-exit()
> call-interactively(gnus-summary-exit)
>
> Doing an `M-: (setq nntp-marks-file-name ".marks")' allows me to leave
> the group again.
It almost certainly is related. I can not reproduce the problem using
the sequence provided. Can you load the lisp files so that we get a
better stacktrace? Just do the following before running gnus.
M-x load-library<ret>gnus-int.el<ret>
M-x load-library<ret>gnus-agent.el<ret>
M-x load-library<ret>nntp.el<ret>
Kevin
next prev parent reply other threads:[~2004-09-23 13:28 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-04 16:18 Jan Rychter
2004-09-20 23:18 ` Jan Rychter
2004-09-21 6:39 ` Jonas Steverud
2004-09-22 17:20 ` Jan Rychter
2004-09-23 6:32 ` Xavier Maillard
2004-09-21 8:52 ` Ralf Angeli
2004-09-22 3:12 ` Kevin Greiner
2004-09-22 13:21 ` Ralf Angeli
2004-09-23 0:59 ` Kevin Greiner
2004-09-23 7:59 ` Ralf Angeli
2004-09-23 13:28 ` Kevin Greiner [this message]
2004-09-23 14:00 ` Ralf Angeli
2004-09-24 3:52 ` Kevin Greiner
2004-09-24 7:43 ` Ralf Angeli
2004-09-24 12:22 ` Kevin Greiner
2004-09-24 12:32 ` Ralf Angeli
2004-09-24 13:41 ` Kevin Greiner
2004-09-24 16:29 ` Kevin Greiner
2004-09-24 16:30 ` Ralf Angeli
2004-09-23 20:07 ` Jan Rychter
2004-09-24 3:58 ` Kevin Greiner
2004-10-11 20:22 ` Jan Rychter
2004-10-13 3:01 ` Kevin Greiner
2004-10-15 1:12 ` Jan Rychter
2004-09-22 17:13 ` Jan Rychter
2004-09-22 16:29 ` Xavier Maillard
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=u4qlpazct.fsf@vignette.com \
--to=kevin.greiner@vignette.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).