From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org, reiner.steib@physik.uni-ulm.de
Subject: Re: Slow nnimap expiry with expiry-target
Date: Wed, 24 Sep 2003 06:42:55 -0400 [thread overview]
Message-ID: <4neky6fowg.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <86r827i6fl.fsf@doze.rijnh.nl> (Jochen =?iso-8859-1?q?K=FCpper's?= message of "Tue, 23 Sep 2003 22:41:18 +0200")
On Tue, 23 Sep 2003, jochen@jochen-kuepper.de wrote:
On Tue, 23 Sep 2003 21:59:35 +0200 Simon Josefsson wrote:
>
> Simon> Or <info:Gnus/Asynchronous+Article+Fetching> maybe?
>
> (info "(gnus)Asynchronous Fetching")
>
> Simon> What are people using to generate info URLs?
>
> Reiner Steib posted his solution a while ago, this is my copy of it:
This is very nice. Is there any way to get tab completion as well
while in the Gnus message buffer, using the currently opened info
buffers? I do this a lot, have the Gnus manual open to check a post
and then say "look at <blah>" in the post itself. With some sort of
tab completion on a message-insert-info-node function, life would be
easier and inserting info references would be fun.
Ted
next prev parent reply other threads:[~2003-09-24 10:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-23 12:34 Bjørn Mork
2003-09-23 14:59 ` Simon Josefsson
2003-09-23 17:37 ` Zack Weinberg
2003-09-23 18:11 ` Simon Josefsson
2003-09-23 19:41 ` Zack Weinberg
2003-09-23 19:56 ` Simon Josefsson
2003-09-23 19:59 ` Simon Josefsson
2003-09-23 20:41 ` Jochen Küpper
2003-09-23 20:56 ` Simon Josefsson
2003-09-24 10:42 ` Ted Zlatanov [this message]
2003-09-25 14:40 ` Reiner Steib
2003-09-25 17:54 ` Simon Josefsson
2003-09-26 2:57 ` Jesper Harder
2003-10-04 22:10 ` Adding "move" operation to Gnus backends (Was: Slow nnimap...) Steinar Bang
2003-10-10 3:05 ` Adding "move" operation to Gnus backends Jesper Harder
2003-10-06 12:11 ` Slow nnimap expiry with expiry-target Bjørn Mork
2003-10-06 17:58 ` Simon Josefsson
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=4neky6fowg.fsf@lockgroove.bwh.harvard.edu \
--to=tzz@lifelogs.com \
--cc=ding@gnus.org \
--cc=reiner.steib@physik.uni-ulm.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).