Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
Cc: Hynek Schlawack <hs+ding@ox.cx>
Subject: Re: Documentation & Keybinding for `gnus-article-browse-html-article'
Date: Thu, 18 May 2006 15:32:57 +0200	[thread overview]
Message-ID: <v9iro34fw6.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <m3psjnwgdd.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Wed, 12 Apr 2006 06:46:22 +0200")

On Wed, Apr 12 2006, Lars Magne Ingebrigtsen wrote:

> Hynek Schlawack <hs+ding@ox.cx> writes:
>> some time ago, my HTML-viewing-code has been commited to CVS. 

[ `gnus-article-browse-html-article' ]

>> Now it's up to define a key-binding, a menuitem and add some
>> documentation.
>
>> And last but not least, where would you put the documentation to? Is
>> this really `washing'? I'm a bit baffled in this point. :)
>
> This isn't really "washing" -- it's more akin to
> `gnus-article-view-part-externally', which is bound to `K e'.  So I'd
> suggest `K H' for the binding, and put it in the same
> menu/documentation node as `K e'.

Hynek, could you provide a patch following Larsi's suggestions?

BTW, (info "(gnus)Saving Articles") also has similar commands:

,----[ (info "(gnus)Saving Articles") ]
| `O p'
| `|'
|      Save the current article in a pipe.  [...]
| 
| `O P'
|      Save the current article into muttprint.  [...]
`----

But `gnus-article-browse-html-article' doesn't use the process/prefix
convention (maybe it could be extended to use it?):

,----[ (info "(gnus)Saving Articles") ]
|    All these commands use the process/prefix convention (*note
| Process/Prefix::).
`----

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



  reply	other threads:[~2006-05-18 13:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-15 13:30 Hynek Schlawack
2006-04-12  4:46 ` Lars Magne Ingebrigtsen
2006-05-18 13:32   ` Reiner Steib [this message]
2006-05-23 12:43     ` Hynek Schlawack
2006-05-23 14:26       ` Reiner Steib

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=v9iro34fw6.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --cc=hs+ding@ox.cx \
    /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).