From: Simon Josefsson <jas@extundo.com>
Subject: Re: NEWS entries
Date: Wed, 30 Apr 2003 04:42:06 +0200 [thread overview]
Message-ID: <ilullxsu2o1.fsf@latte.josefsson.org> (raw)
In-Reply-To: <m3el3kvjz6.fsf@defun.localdomain> (Jesper Harder's message of "Wed, 30 Apr 2003 03:42:53 +0200")
Jesper Harder <harder@myrealbox.com> writes:
>> This gives the appearance that Picons is a new feature, but isn't the
>> new part only that it has been reimplemented? Maybe that could be
>> stressed more.
>
> Maybe just switch the two paragraphs:
>
> ** Picons
> The picons code has been reimplemented to work in GNU Emacs -- some of
> the previous options have been removed or renamed.
>
> Picons are small "personal icons" representing users, domain and
> newsgroups, which can be displayed in the Article buffer. To enable
> picons, install the picons database from
>
> http://www.cs.indiana.edu/picons/ftp/index.html
>
> and point `gnus-picon-databases' to that location.
>
> ?
I like it.
>>> ** The new option `gnus-gcc-mark-as-read' automatically marks
>>> Gcc articles as read.
>>
>> We have:
>>
>> ** gnus-inews-mark-gcc-as-read has been renamed to gnus-gcc-mark-as-read.
>
> Hmm, but gnus-inews-mark-gcc-as-read was also new in Oort before it
> was renamed (I think). So maybe it's not mentioning it at all because
> it was never part of a released Gnus version?
Yes, replace it with your entry.
next prev parent reply other threads:[~2003-04-30 2:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-29 1:14 Jesper Harder
2003-04-29 2:29 ` Simon Josefsson
2003-04-30 1:42 ` Jesper Harder
2003-04-30 2:42 ` Simon Josefsson [this message]
2003-04-29 17:19 ` Reiner Steib
2003-04-30 1:45 ` Jesper Harder
2003-04-30 14:55 ` Reiner Steib
2003-04-30 18:26 ` Reiner Steib
2003-05-01 1:54 ` Jesper Harder
2003-05-01 6:40 ` Lars Magne Ingebrigtsen
2003-05-01 13:53 ` Raymond Scholz
2003-05-01 13:58 ` Lars Magne Ingebrigtsen
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=ilullxsu2o1.fsf@latte.josefsson.org \
--to=jas@extundo.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).