From: wmperry@aventail.com (William M. Perry)
Cc: ding@gnus.org
Subject: Re: What now?
Date: Tue, 7 Dec 1999 00:36:32 -0500 [thread overview]
Message-ID: <199912070536.AAA01920@wmperry.bp.aventail.com> (raw)
In-Reply-To: Brian May's message of "06 Dec 1999 16:31:23 +1100"
Brian May <bmay@csse.monash.edu.au> writes:
> >>>>> "Lars" == Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
>
> Lars> "Jody M. Klymak" <jklymak@apl.washington.edu> writes:
> >> I was also thinking that perhaps a hyper diary may be a nice
> >> thing. The diary would accept hyperlinks (much the way that
> >> gnus does now, or Asvin Goel's Records Mode
> >> http://www.cse.ogi.edu/~ashvin/software.html). Then you could
> >> write a lisp function to save your article to a text file (or
> >> mbox) and add a hyperlink to your diary.
>
> Lars> That sounds kinda neat. If Gnus had a proper "refer article
> Lars> from outside of Gnus" function, Gnus could handle the
> Lars> "news:" URLs.
Well, Emacs/W3 already uses gnus for that, so that should be pretty simple
to do. :)
> I think this would be really good.
>
> Another feature (one that doesn't look like its already implemented at
> least) could be a "write new message with these headers" function, that
> could be called, eg by w3. Currently, while w3 uses Gnus message mode,
> major Gnus features, eg MIME and gnus-posting styles don't appear to be
> supported. However, this would require co-operation from w3.
Easily accomplished. :) The problem with using gnus posting styles for
Emacs/W3 mailto: URLs is that not everybody clicks those links from within
Gnus. Emacs/W3 uses _message_, not Gnus for sending the mail. There might
be a case for having w3 allow customization of posting styles based on
email address or the URL the link is on, something like that.
-bp
next prev parent reply other threads:[~1999-12-07 5:36 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 ` What now? (was: Forwarding Mail Messages) Lars Magne Ingebrigtsen
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 [this message]
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=199912070536.AAA01920@wmperry.bp.aventail.com \
--to=wmperry@aventail.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).