From: Cristian Gutierrez <crgutier@dcc.uchile.cl>
Subject: Re: Bookmarking summary limit commands?
Date: Wed, 13 Oct 2004 17:13:18 -0300 [thread overview]
Message-ID: <87brf6js0x.fsf@guti.no-ip.org> (raw)
In-Reply-To: <m3wtxvvfp7.fsf@defun.localdomain>
Jesper Harder wrote:
> Cristian Gutierrez <crgutier@dcc.uchile.cl> writes:
>
>> But switching between these is somewhat tiresome, and cluttering the
>> keymap with hotkeys for each one of them is not very useful; so my
>> question is: Is there some way to `bookmark' a limit command/author
>> combo, so I can assign _one_ keybinding and use it to select what
>> "view" (entry on the bookmarks list) I want to apply?
>
> There's no predefined functionality. But it's fairly straightforward
> to make, e.g.
[code]
This is just nice, thank you Jesper!
I added a pop-limit command just before the actual limit command for
each entry, to be able to switch between them without manually doing
"/w" every time:
,----
| (defvar my-limit-bookmark-alist
| '(("analytics" . (progn
| (gnus-summary-pop-limit)
| (gnus-summary-limit-to-author "analytics\\|dads")))
| ("irf" . (progn
| (gnus-summary-pop-limit)
| (gnus-summary-limit-to-author "rlemus\\|javier g")))
| ("memoria" . (progn
| (gnus-summary-pop-limit)
| (gnus-summary-limit-to-author "cecilia\\|garreaud"))))
| "Alist of limit bookmarks.")
`----
But now when a limit fails, I get blocked trying to switch to another
one with the message "No limit to pop" (yes, because the limit has
already been popped in the last [failed] limit).
How could I force the second command in (progn ...) to be evaluated even
if the first fails? I tried surrounding the first one in a
condition-case construct, for example:
,----
| ("analytics" . (progn
| (condition-case nil
| (gnus-summary-pop-limit)
| (error nil))
| (gnus-summary-limit-to-author "analytics\\|dads")))
`----
... but the result is the same. Any insights are appreciated.
--
Cristian Gutierrez http://www.dcc.uchile.cl/~crgutier
crgutier[@]dcc.uchile.cl Jabber:crgutier@jabber.org
"Today's piece of secure software is the subject of tomorrow's Bugtraq
posting. -- http://www.landfield.com/isn/mail-archive/2001/Nov/0076.html
next prev parent reply other threads:[~2004-10-13 20:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-12 2:27 Cristian Gutierrez
2004-10-12 20:34 ` Jesper Harder
2004-10-13 20:13 ` Cristian Gutierrez [this message]
2004-10-13 21:42 ` Jesper Harder
2004-10-14 0:23 ` Cristian Gutierrez
2004-10-17 12:45 ` Kai Grossjohann
2004-10-18 3:09 ` Cristian Gutierrez
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=87brf6js0x.fsf@guti.no-ip.org \
--to=crgutier@dcc.uchile.cl \
/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).