GNU bug report logs -
#8978
No complete guide to article marks / gnus-summary-line-format underdocumented
Previous Next
Reported by: Dave Abrahams <dave <at> boostpro.com>
Date: Fri, 1 Jul 2011 17:24:02 UTC
Severity: normal
Fixed in version 24.1
Done: Lars Magne Ingebrigtsen <larsi <at> gnus.org>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 8978 in the body.
You can then email your comments to 8978 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
owner <at> debbugs.gnu.org, help-debbugs <at> gnu.org:
bug#8978; Package
debbugs.gnu.org.
(Fri, 01 Jul 2011 17:24:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Dave Abrahams <dave <at> boostpro.com>:
New bug report received and forwarded. Copy sent to
help-debbugs <at> gnu.org.
(Fri, 01 Jul 2011 17:24:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
The docs for gnus-summary-line-format mention that "%U" produces "R",
"K", "-", or " ". However, they fail to mention "r", for example. The
first clue I could find about that mark was in "9.18.4 Spam and Ham
Processors" of all places, where it drops the hint that "r" means
"explicit delete" (!). Users *really* need a little table that gives a
complete guide to the built-in marks, so that when they look at the
summary buffer, they know what it means.
Same goes for the other Gnus buffers that support marking, BTW. K and U
in the server browsing buffer are confusing as well.
Package: gnus
Version: 5.110018
No Gnus v0.18
GNU Emacs 23.3.1 (x86_64-apple-darwin, NS apple-appkit-1038.35)
of 2011-03-09 on black.porkrind.org
200 news.gmane.org InterNetNews NNRP server INN 2.5.1 ready (posting ok)
101 Capability list:
VERSION 2
IMPLEMENTATION INN 2.5.1
AUTHINFO USER
HDR
LIST ACTIVE ACTIVE.TIMES DISTRIB.PATS HEADERS NEWSGROUPS OVERVIEW.FMT
OVER
POST
READER
STARTTLS
.
[Message part 2 (application/emacs-lisp, inline)]
[Message part 3 (text/plain, inline)]
--
Dave Abrahams
BoostPro Computing
http://www.boostpro.com
bug marked as fixed in version 24.1, send any further explanations to
8978 <at> debbugs.gnu.org and Dave Abrahams <dave <at> boostpro.com>
Request was from
Lars Magne Ingebrigtsen <larsi <at> gnus.org>
to
control <at> debbugs.gnu.org.
(Sun, 03 Jul 2011 16:26:02 GMT)
Full text and
rfc822 format available.
Information forwarded
to
owner <at> debbugs.gnu.org, bugs <at> gnus.org:
bug#8978; Package
gnus.
(Sun, 03 Jul 2011 16:41:02 GMT)
Full text and
rfc822 format available.
Message #10 received at 8978 <at> debbugs.gnu.org (full text, mbox):
Dave Abrahams <dave <at> boostpro.com> writes:
> The docs for gnus-summary-line-format mention that "%U" produces "R",
> "K", "-", or " ". However, they fail to mention "r", for example. The
> first clue I could find about that mark was in "9.18.4 Spam and Ham
> Processors" of all places, where it drops the hint that "r" means
> "explicit delete" (!). Users *really* need a little table that gives a
> complete guide to the built-in marks, so that when they look at the
> summary buffer, they know what it means.
I've now made the doc string for that variable link to
"(gnus)Read Articles", which lists all the marks, I think.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
Information forwarded
to
owner <at> debbugs.gnu.org, bugs <at> gnus.org:
bug#8978; Package
gnus.
(Sun, 03 Jul 2011 20:31:01 GMT)
Full text and
rfc822 format available.
Message #13 received at 8978 <at> debbugs.gnu.org (full text, mbox):
on Sun Jul 03 2011, Lars Magne Ingebrigtsen <larsi-AT-gnus.org> wrote:
> Dave Abrahams <dave <at> boostpro.com> writes:
>
>> The docs for gnus-summary-line-format mention that "%U" produces "R",
>> "K", "-", or " ". However, they fail to mention "r", for example. The
>> first clue I could find about that mark was in "9.18.4 Spam and Ham
>> Processors" of all places, where it drops the hint that "r" means
>> "explicit delete" (!). Users *really* need a little table that gives a
>> complete guide to the built-in marks, so that when they look at the
>> summary buffer, they know what it means.
>
> I've now made the doc string for that variable link to
> "(gnus)Read Articles", which lists all the marks, I think.
Not a complete list. The following are not covered on that page:
"-"
" " (gnus-unread-mark)
"=" (gnus-unsendable-mark)
"%" (gnus-downloadable-mark")
"!" (gnus-ticked-mark)
"$" (gnus-spam-mark)
"?" (gnus-dormant-mark)
"E" (gnus-expirable-mark)
"A" (gnus-replied-mark) All articles that you have replied to or made a followup to
"*" Article is "[[info:gnus#Persistent%20Articles][persistent]]"
--
Dave Abrahams
BoostPro Computing
http://www.boostpro.com
Message #14 received at 8978-close <at> debbugs.gnu.org (full text, mbox):
Dave Abrahams <dave <at> boostpro.com> writes:
>> I've now made the doc string for that variable link to
>> "(gnus)Read Articles", which lists all the marks, I think.
>
> Not a complete list. The following are not covered on that page:
I've changed the link to "Marking Articles".
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
Message #15 received at 8978-close <at> debbugs.gnu.org (full text, mbox):
on Tue Jul 05 2011, Lars Magne Ingebrigtsen <larsi-AT-gnus.org> wrote:
> Dave Abrahams <dave <at> boostpro.com> writes:
>
>>> I've now made the doc string for that variable link to
>>> "(gnus)Read Articles", which lists all the marks, I think.
>>
>> Not a complete list. The following are not covered on that page:
>
> I've changed the link to "Marking Articles".
Thanks, but it doesn't address the most important part of this issue:
IMO users still need a complete and condensed guide to article marks. I
had to make my own by crawling through the docs.
--
Dave Abrahams
BoostPro Computing
http://www.boostpro.com
Message #16 received at 8978-close <at> debbugs.gnu.org (full text, mbox):
Dave Abrahams <dave <at> boostpro.com> writes:
>> I've changed the link to "Marking Articles".
>
> Thanks, but it doesn't address the most important part of this issue:
> IMO users still need a complete and condensed guide to article marks. I
> had to make my own by crawling through the docs.
I think all the nodes under that node should list all the marks. If any
are missing, that's a bug.
But listing all marks twice doesn't seem productive.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
Message #17 received at 8978-close <at> debbugs.gnu.org (full text, mbox):
on Wed Jul 06 2011, Lars Magne Ingebrigtsen <larsi-AT-gnus.org> wrote:
> Dave Abrahams <dave <at> boostpro.com> writes:
>
>>> I've changed the link to "Marking Articles".
>>
>> Thanks, but it doesn't address the most important part of this issue:
>> IMO users still need a complete and condensed guide to article marks. I
>> had to make my own by crawling through the docs.
>
> I think all the nodes under that node should list all the marks. If any
> are missing, that's a bug.
>
> But listing all marks twice doesn't seem productive.
Thanks for your patience; I think you are probably right about this.
For some reason I had the impression that the marks were scattered
throughout the docs, but the organization looks fine to me now.
--
Dave Abrahams
BoostPro Computing
http://www.boostpro.com
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org.
(Thu, 04 Aug 2011 11:24:05 GMT)
Full text and
rfc822 format available.
This bug report was last modified 12 years and 334 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.