From: Kevin Greiner <kgreiner@xpediantsolutions.com>
Subject: Re: gnus-point-at-bol
Date: Tue, 13 Jan 2004 20:17:29 -0500 [thread overview]
Message-ID: <uk73v49cm.fsf@xpediantsolutions.com> (raw)
In-Reply-To: <ullobq10f.fsf@boost-consulting.com>
David Abrahams <dave@boost-consulting.com> writes:
> Bill White <billw@wolfram.com> writes:
>
>> On Sat Jan 10 2004 at 13:27, David Abrahams <dave@boost-consulting.com> said:
>>
>>> An update of gnus from CVS this morning produces the following error
>>> when I do `M-g' in a summary buffer:
>>>
>>> gnus-point-at-bol()
>>> gnus-agent-save-group-info((nnimap "www.stlport.com" (nnimap-address "www.stlport.com") (nnimap-stream ssl) (nnimap-authenticator login)) "INBOX" (20000 . 54842))
>>> gnus-group-get-new-news-this-group(1)
>>> gnus-summary-reselect-current-group(nil t)
>>> gnus-summary-rescan-group(nil)
>>> * call-interactively(gnus-summary-rescan-group)
>>> recursive-edit()
>>> byte-code("Æ.Ç !? ?\n!?Â
>>
>> Perhaps you have code in your .gnus that uses gnus-point-at-bol? I
>> did.
>
> I did not, so the errors were coming from elsewhere.
Check the last modified time of the gnus-agent.elc file. Is it newer,
or older, than when you updated from CVS? If it is older, manually
delete it (actually it would be best to delete all .elc files) then
run make again.
Kevin
prev parent reply other threads:[~2004-01-14 1:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-10 19:27 gnus-point-at-bol David Abrahams
2004-01-10 21:05 ` gnus-point-at-bol Christoph Conrad
2004-01-11 5:58 ` gnus-point-at-bol David Abrahams
[not found] ` <7coetbyq1v.fsf@nature.tsukuba.ac.jp>
2004-01-11 6:30 ` gnus-point-at-bol Steve Youngs
2004-01-12 23:57 ` gnus-point-at-bol Bill White
2004-01-13 16:14 ` gnus-point-at-bol David Abrahams
2004-01-13 16:31 ` gnus-point-at-bol Jesper Harder
2004-01-14 1:17 ` Kevin Greiner [this message]
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=uk73v49cm.fsf@xpediantsolutions.com \
--to=kgreiner@xpediantsolutions.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).