From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: What now? (was: Forwarding Mail Messages)
Date: 02 Dec 1999 02:19:01 +0100 [thread overview]
Message-ID: <m3yabedtru.fsf_-_@quimbies.gnus.org> (raw)
In-Reply-To: <7s4se2uqao.fsf@brutus.mts.jhu.edu>
Nevin Kapur <nevin@jhu.edu> writes:
> i.e, create a virtual folder called "unreplied" by taking messages
> from "Inbox" which are unreplied and are not labeled "info". VM can
> slurp a subset of messages from a particular file or directory.
That does sound useful, but requires that Gnus have the ability to
label messages, and it can't, at present.
Client-side labels wouldn't be that difficult to implement, if someone
would want to do that. Perhaps as a shadow hierarchy of labels and
notes to go with the groups. (Client-side (i.e. Gnus) as opposed to
server-side (nn*) since that would mean just implementing these things
once.)
Anyway, I was thinking while in the shower -- what now? Pterodactyl
Gnus was kinda about MIME support and multilingualization. Along the
way, stuff like the article display revamp, nnimap, mail-fetching,
posting styles, and lotsa web-based interfaces was added.
But is there anything major, like MIME, left to implement. Is Gnus
(don't say it!) getting feature-complete?
I don't believe that for a second, but I've been asked a couple of
times -- what's next? And I can't really think of any biggies for the
O-named Gnus series.
Perhaps the next step should be to make Gnus usable^H^H^H^Her-friendly.
Nah.
I'm sure somebody will think of something. :-) Or one could start
working on that TODO list that's in the manual.
...
Nah.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~1999-12-02 1:19 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-24 0:06 Forwarding Mail Messages Brian May
1999-12-01 19:47 ` Lars Magne Ingebrigtsen
1999-12-02 0:42 ` Nevin Kapur
1999-12-02 1:19 ` Lars Magne Ingebrigtsen [this message]
1999-12-02 2:59 ` What now? Brian May
1999-12-02 16:23 ` Colin Marquardt
1999-12-02 16:56 ` Jody M. Klymak
1999-12-06 4:26 ` Lars Magne Ingebrigtsen
1999-12-06 5:31 ` Brian May
1999-12-07 5:36 ` William M. Perry
1999-12-07 5:59 ` Brian May
1999-12-07 16:09 ` William M. Perry
1999-12-08 8:02 ` nnimap URLs? (Was: What now?) Steinar Bang
1999-12-08 16:08 ` William M. Perry
1999-12-08 18:02 ` Simon Josefsson
1999-12-08 18:23 ` William M. Perry
1999-12-08 17:26 ` Simon Josefsson
1999-12-10 16:07 ` William M. Perry
1999-12-08 22:51 ` What now? Brian May
1999-12-06 17:36 ` Jody M. Klymak
1999-12-06 20:34 ` Bruce Stephens
1999-12-06 22:38 ` Kai Großjohann
1999-12-03 19:12 ` What now? (was: Forwarding Mail Messages) Jody M. Klymak
1999-12-04 17:05 ` Hrvoje Niksic
1999-12-04 22:53 ` Jody M. Klymak
2000-04-21 21:13 ` Lars Magne Ingebrigtsen
2000-04-21 21:05 ` William M. Perry
2000-04-21 21:16 ` Arcady Genkin
2000-04-21 23:32 ` William M. Perry
2000-04-22 9:36 ` Hans de Graaff
1999-12-05 21:46 ` Kai Großjohann
1999-12-05 21:51 ` Kai Großjohann
1999-12-06 1:27 ` Richard Hoskins
1999-12-02 1:48 ` Forwarding Mail Messages Brian May
1999-12-06 4:12 ` 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=m3yabedtru.fsf_-_@quimbies.gnus.org \
--to=larsi@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).