From: Reiner Steib <reinersteib+gmane@imap.cc>
To: ding@gnus.org
Subject: Re: Sticky article buffers
Date: Wed, 25 Jul 2007 20:36:25 +0200 [thread overview]
Message-ID: <v9wswo8h5i.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <876448eby7.fsf@baldur.tsdh.de>
On Wed, Jul 25 2007, Tassilo Horn wrote:
> my assignment papers have arrived at the FSF. Here's my patch, [...]
Thank you.
> One thing that I'm aware of it that the binding `C-c s' is not too good,
> because bindings with `C-c' should be reserved for the user.
We should not install it with `C-c s'. If we can't find a better
binding, we can install it without a key binding first and add a
binding later.
> But what other free binding could be used?
If we stay with the term "sticky article buffer", I'd suggest `A S'.
Did you think about menu entries? Sometimes this helps to find
similar command and key bindings.
> diff -r7.66 gnus.el
> 911a912,923
Oh, please use unified diff (-u) (or context diff (-c)).
> 4360a4373,4378
>>
>> ;; Local Variables:
>> ;; coding: iso-8859-1
>> ;; indent-tabs-mode: t
>> ;; tab-width: 8
>> ;; End:
Please don't submit proposals that include unrelated changes.
>> (define-key gnus-sticky-article-mode-map k nil))
>> (define-key gnus-sticky-article-mode-map "q" 'gnus-sticky-article-kill-buffer)
I'd expect `k' for kill buffer and `q' for quit (bury buffer).
>> (define-key gnus-sticky-article-mode-map "\C-hc" 'describe-key-briefly)
>> (define-key gnus-sticky-article-mode-map "\C-hk" 'describe-key))
Why do we need to treat these two command specially?
>> (defun gnus-sticky-article-kill-buffer (&optional buffer)
>> "Kills the given sticky article buffer. If none is given, it'll
>> assume the current buffer and kill it if it has
>> `gnus-sticky-article-mode'."
[...]
>> (defun gnus-summary-make-sticky-article (arg)
>> "Make the current article sticky. If a prefix arg is given you
>> will be asked for a name for this sticky buffer."
The doc strings needs a little improvement. Cf. `M-x checkdoc-defun
RET'. But I may do this after installing the patch.
> 8089a8119,8124
>>
>> ;; Local Variables:
>> ;; coding: iso-8859-1
>> ;; indent-tabs-mode: t
>> ;; tab-width: 8
>> ;; End:
Please don't include unrelated changes. (Same for other
indent-tabs-mode/tab-width hunks below.)
> 1770a1771
>> "\C-cs" gnus-summary-make-sticky-article
Should be removed/change. See above.
> 2446a2448
>> ["Make article buffer sticky" gnus-summary-make-sticky-article t]
Okay, a menu entry. I'd too lazy to check where it would end up. In
unified/context diff it would be easier to guess. ;-)
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2007-07-25 18:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-25 15:32 Tassilo Horn
2007-07-25 18:36 ` Reiner Steib [this message]
2007-07-25 19:32 ` Tassilo Horn
2007-07-25 20:17 ` Tassilo Horn
2007-08-12 11:15 ` Reiner Steib
2007-08-12 11:59 ` Tassilo Horn
2007-08-12 12:43 ` Reiner Steib
2007-08-13 13:03 ` Tassilo Horn
2007-08-13 14:04 ` Tassilo Horn
2007-08-14 5:18 ` Katsumi Yamaoka
2007-08-14 7:34 ` Tassilo Horn
2007-08-14 9:02 ` Katsumi Yamaoka
2007-08-14 10:41 ` Tassilo Horn
2007-08-14 6:12 ` Katsumi Yamaoka
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=v9wswo8h5i.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
--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).