From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: Better integration of the new Gnus FAQ in Oort
Date: Fri, 11 Apr 2003 12:01:22 -0400 [thread overview]
Message-ID: <4nfzopkoq5.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <v9of3dkspe.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Fri, 11 Apr 2003 16:35:25 +0200")
On Fri, 11 Apr 2003, 4.uce.03.r.s@nurfuerspam.de wrote:
> An advantage of the above mentioned `gnus-faq-*' functions would be,
> that we can still use the buttons and functions when the FAQ has
> been converted to info successfully: Instead of jumping to the nndoc
> article, the functions will go to the info node.
>
> What do people think? I could add the buttons easily. Can someone
> give me hints on how to implement the "jump to
> `nndoc+gnus-help:gnus-help' and go to ..." part in a reasonably
> manner? Or better send code. ;-)
I like the idea, and I can write the code to get the article but I
don't know how to do the parsing necessary to jump to a section or
item number.
I think we should also buttonize every instance of "gnus faq item
[0-9.]+" (case-insensitive). That way, you can just say "see gnus FAQ
item 4.7" and a link would be shown to the user. Asking users to run
Lisp code may be a problem for novices.
Ted
next prev parent reply other threads:[~2003-04-11 16:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-11 14:35 Reiner Steib
2003-04-11 16:01 ` Ted Zlatanov [this message]
2003-04-11 23:02 ` Reiner Steib
2003-04-12 8:57 ` Kai Großjohann
2003-04-14 19:37 ` Ted Zlatanov
2003-04-14 21:11 ` Reiner Steib
2003-04-15 19:57 ` Ted Zlatanov
2003-04-15 21:57 ` Lars Magne Ingebrigtsen
2003-04-16 4:27 ` Ted Zlatanov
2003-04-11 23:10 ` Jesper Harder
2003-04-12 15:31 ` Reiner Steib
2003-04-12 19:54 ` Frank Schmitt
2003-04-12 20:54 ` Jesper Harder
2003-04-12 22:13 ` Lars Magne Ingebrigtsen
[not found] ` <v9fzomqezo.fsf@marauder.physik.uni-ulm.de>
2003-04-13 21:23 ` Frank Schmitt
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=4nfzopkoq5.fsf@lockgroove.bwh.harvard.edu \
--to=tzz@lifelogs.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).