From: Tassilo Horn <tassilo@member.fsf.org>
To: ding@gnus.org
Subject: Re: Sticky article buffers
Date: Mon, 13 Aug 2007 15:03:56 +0200 [thread overview]
Message-ID: <87hcn3oabn.fsf@baldur.tsdh.de> (raw)
In-Reply-To: <v9643k7wkp.fsf@marauder.physik.uni-ulm.de>
Reiner Steib <reinersteib+gmane@imap.cc> writes:
Hi Reiner,
>> Is there something to create them automatically, so that I only need
>> to add comments to the functions I cahnged?
>
> Sure: When point is inside the modified defun, defcustom, ... (in the
> lisp or texi file or in the diff buffer) you can use `C-x 4 a'
> (`add-change-log-entry-other-window' or `M-x add-change-log-entry
> RET').
Nifty.
>>> - Could you provide documentation for texi/gnus.texi and an entry
>>> for texi/gnus-news.texi?
>>
>> I think this applies to the current patch as well as to future
>> contributions, right?
>
> Yes.
Ok, here's the patch, created with pcl-cvs which is indeed very nice.
--8<---------------cut here---------------start------------->8---
Index: texi/gnus.texi
===================================================================
RCS file: /usr/local/cvsroot/gnus/texi/gnus.texi,v
retrieving revision 7.242
diff -u -r7.242 gnus.texi
--- texi/gnus.texi 10 Aug 2007 02:34:24 -0000 7.242
+++ texi/gnus.texi 13 Aug 2007 13:00:17 -0000
@@ -496,6 +496,7 @@
* Asynchronous Fetching:: Gnus might be able to pre-fetch articles.
* Article Caching:: You may store articles in a cache.
* Persistent Articles:: Making articles expiry-resistant.
+* Sticky Articles:: Article buffers that are not reused.
* Article Backlog:: Having already read articles hang around.
* Saving Articles:: Ways of customizing article saving.
* Decoding Articles:: Gnus can treat series of (uu)encoded articles.
@@ -4598,6 +4599,7 @@
* Asynchronous Fetching:: Gnus might be able to pre-fetch articles.
* Article Caching:: You may store articles in a cache.
* Persistent Articles:: Making articles expiry-resistant.
+* Sticky Articles:: Article buffers that are not reused.
* Article Backlog:: Having already read articles hang around.
* Saving Articles:: Ways of customizing article saving.
* Decoding Articles:: Gnus can treat series of (uu)encoded articles.
@@ -7484,6 +7486,53 @@
(setq gnus-use-cache 'passive)
@end lisp
+@node Sticky Articles
+@section Sticky Articles
+@cindex sticky articles
+
+When you select an article the current article buffer will be reused
+according to the value of the variable
+@code{gnus-single-article-buffer}. If its value is non-nil (the
+default) all articles reuse the same article buffer. Else each group
+has its own article buffer.
+
+This implies that it's not possible to have more than one article buffer
+in a group at a time. But sometimes you might want to display all the
+latest emails from your mother, your father, your aunt, your uncle and
+your 17 cousins to coordinate the next christmas party.
+
+That's where sticky articles come in handy. A sticky article buffer
+basically is a normal article buffer, but it won't be reused when you
+select another article. You can make an article sticky with:
+
+@table @kbd
+@item A S
+@kindex A S (Summary)
+@findex gnus-sticky-article
+Make the current article sticky. If a prefix arg is given, ask for a
+name for this sticky article buffer.
+@end table
+
+To close a sticky article buffer you can use these commands:
+
+@table @kbd
+@item q
+@kindex q (Article)
+@findex bury-buffer
+Puts this sticky article buffer at the end of the list of all buffers.
+
+@item k
+@kindex k (Article)
+@findex gnus-kill-sticky-article-buffer
+Kills this sticky article buffer.
+@end table
+
+To kill all sticky article buffers you can use:
+
+@defun gnus-kill-sticky-article-buffers ARG
+Kill all sticky article buffers.
+If a prefix ARG is given, ask for confirmation.
+@end defun
@node Article Backlog
@section Article Backlog
@@ -26195,6 +26244,7 @@
P. E. Jareth Hein,
Hisashige Kenji, @c Hisashige
Scott Hofmann,
+Tassilo Horn,
Marc Horowitz,
Gunnar Horrigmo,
Richard Hoskins,
--8<---------------cut here---------------end--------------->8---
Bye,
Tassilo
next prev parent reply other threads:[~2007-08-13 13:03 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
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 [this message]
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=87hcn3oabn.fsf@baldur.tsdh.de \
--to=tassilo@member.fsf.org \
--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).