Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <4.uce.03.r.s@nurfuerspam.de>
Subject: Re: Better integration of the new Gnus FAQ in Oort
Date: Sat, 12 Apr 2003 01:02:44 +0200	[thread overview]
Message-ID: <v9fzooprhn.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <4nfzopkoq5.fsf@lockgroove.bwh.harvard.edu>

On Fri, Apr 11 2003, Ted Zlatanov wrote:

> On Fri, 11 Apr 2003, 4.uce.03.r.s@nurfuerspam.de wrote:
>> 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.

This was my problem too, but I though it was just my ignorance.  :-)
IMHO, ideally, we should have something like incremental search or `i'
and `,' in info.  Is this feasible?  Ideas?

Please post the code, even if the jump-to thingie is missing.
Probably somebody on the list will know how to fill the gap.

> I think we should also buttonize every instance of "gnus faq item
> [0-9.]+" (case-insensitive).  

Yes, this can be added easily.  The button regexps are
case-insensitive anyhow.

> That way, you can just say "see gnus FAQ item 4.7" and a link would
> be shown to the user.  

This would be similar to "in article <mid>" buttons:

    ("\\bin\\( +article\\| +message\\)? +\\(<\\([^\n @<>]+@[^\n @<>]+\\)>\\)"
     2 (>= gnus-button-message-level 0) gnus-button-message-id 3)

> Asking users to run Lisp code may be a problem for novices.

If we have buttons for such stuff in 5.10, novice users just have to
press RET or mouse-2 on stuff like (gnus-faq-search
"mm-text-html-renderer").  (And it's international.)  We often see
answers like "See `C-h v some-var RET'." even now---that non-Oort
users don't have buttons for.  And my impression is, that those
answers are appreciated by novices.

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo--- PGP key available via WWW   http://rsteib.home.pages.de/




  reply	other threads:[~2003-04-11 23:02 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
2003-04-11 23:02   ` Reiner Steib [this message]
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=v9fzooprhn.fsf@marauder.physik.uni-ulm.de \
    --to=4.uce.03.r.s@nurfuerspam.de \
    --cc=reiner.steib@gmx.de \
    /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).