From: Ted Zlatanov <tzz@lifelogs.com>
To: info-gnus-english@gnu.org
Subject: Re: What's a killed article ?
Date: Mon, 08 Dec 2008 09:46:22 -0600 [thread overview]
Message-ID: <864p1ek6up.fsf@lifelogs.com> (raw)
In-Reply-To: <m2prk6e2t9.fsf@gmail.com>
On Fri, 05 Dec 2008 22:21:06 +0100 Francis Moreau <francis.moro@gmail.com> wrote:
FM> Ted Zlatanov <tzz@lifelogs.com> writes:
>> On Thu, 04 Dec 2008 22:46:32 +0100 Francis Moreau <francis.moro@gmail.com> wrote:
>>
FM> It's sad to see that such notion [killed articles] are left
FM> undefined until a late section (SCORING).
>>
>> To me it was obvious, but I had been using tin for many years when I
>> tried Gnus, and in tin the names are similar IIRC. Things like score
>> files, threads, and article marks are often assumed to be basic
>> knowledge in newsreader manuals.
FM> So are you meaning that Gnus is for user that already had an
FM> experience with another newsreader ?
No, only that the manual assumes some basic knowledge.
>> I don't know if the Gnus manuals should remedy that or point to an
>> external reference for these terms.
FM> Yes definitely.
I don't know if the reference should be external or internally
contained, though. Any opinions?
FM> That said, it's not the only point where I find the documenation
FM> obscure or not enough detailed: what's a very wide mail reply for
FM> example. I can find ton of such example where you need to dig very
FM> deeply the documentation to find such basic things, if the
FM> documentation exists at all.
OK, we can certainly put together a glossary and use the Texinfo
facilities to link terms to their definitions (I don't remember if
that's specifically supported but I'm sure something can be arranged).
Can you provide a list of terms you personally found challenging?
Remember, most readers of the Gnus mailing list and newsgroups are not
good test subjects for manual readability :)
Thanks
Ted
next prev parent reply other threads:[~2008-12-08 15:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-03 19:41 Francis Moreau
2008-12-03 19:47 ` Reiner Steib
2008-12-04 9:06 ` Francis Moreau
2008-12-04 19:33 ` Reiner Steib
2008-12-04 21:46 ` Francis Moreau
2008-12-05 17:48 ` Ted Zlatanov
2008-12-05 21:21 ` Francis Moreau
2008-12-05 22:19 ` Glyn Millington
[not found] ` <mailman.2031.1228517278.26697.info-gnus-english@gnu.org>
2008-12-06 13:49 ` Francis Moreau
2008-12-08 15:46 ` Ted Zlatanov [this message]
2008-12-08 18:05 ` Giorgos Keramidas
2008-12-15 19:21 ` Francis Moreau
2008-12-16 2:30 ` Giorgos Keramidas
2008-12-18 20:00 ` harven
2008-12-23 8:17 ` Giorgos Keramidas
2008-12-23 22:51 ` Ted Zlatanov
2009-01-09 11:25 ` Francis Moreau
2009-01-09 11:30 ` Francis Moreau
2009-01-09 11:17 ` Francis Moreau
2009-01-09 11:28 ` Francis Moreau
2008-12-15 19:21 ` Francis Moreau
2008-12-16 17:17 ` Ted Zlatanov
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=864p1ek6up.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=info-gnus-english@gnu.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).