From: Bill White <billw@wolfram.com>
Cc: ding@gnus.org
Subject: Re: gnus-point-at-bol
Date: Mon, 12 Jan 2004 17:57:05 -0600 [thread overview]
Message-ID: <ruozncs7mb2.fsf@billw2lx.wolfram.com> (raw)
In-Reply-To: <ufzeny57p.fsf@boost-consulting.com> (David Abrahams's message of "Sat, 10 Jan 2004 14:27:22 -0500")
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. See the lisp/ dir changelog:
2004-01-05 Jesper Harder <harder@ifa.au.dk>
[...]
* gnus-util.el (gnus-point-at-bol, gnus-point-at-eol): Remove.
Replace with point-at-{eol,bol} throughout all files.
Cheers -
bw
--
Bill White . billw@wolfram.com . http://members.wri.com/billw
"No ma'am, we're musicians."
next prev parent reply other threads:[~2004-01-12 23:57 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 ` Bill White [this message]
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 ` gnus-point-at-bol Kevin Greiner
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=ruozncs7mb2.fsf@billw2lx.wolfram.com \
--to=billw@wolfram.com \
--cc=ding@gnus.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).