From: Hynek Schlawack <hs+ding@ox.cx>
Subject: Documentation & Keybinding for `gnus-article-browse-html-article'
Date: Wed, 15 Mar 2006 14:30:28 +0100 [thread overview]
Message-ID: <x7psknhm2z@ox.cx> (raw)
Hi,
some time ago, my HTML-viewing-code has been commited to CVS. Now it's up
to define a key-binding, a menuitem and add some documentation.
So, where would you categorize this code to?
Reiner suggested "<menu-bar> <Article> <Washing> <Html>" but there's
already a Html entry in the Washing-menu. Any other suggestions? "Extern HTML"?
The keybinding is even trickier I'm afraid. :( `W H' (as an analogy to
`W h') is already taken. Am I mistaken or it `W R' (_r_ender) still
free?
And last but not least, where would you put the documentation to? Is
this really `washing'? I'm a bit baffled in this point. :)
-hs
next reply other threads:[~2006-03-15 13:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-15 13:30 Hynek Schlawack [this message]
2006-04-12 4:46 ` Lars Magne Ingebrigtsen
2006-05-18 13:32 ` Reiner Steib
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=x7psknhm2z@ox.cx \
--to=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).