From: Jesper Harder <harder@ifa.au.dk>
Subject: Re: Bookmarking summary limit commands?
Date: Wed, 13 Oct 2004 23:42:08 +0200 [thread overview]
Message-ID: <m3d5zmwb0v.fsf@defun.localdomain> (raw)
In-Reply-To: <87brf6js0x.fsf@guti.no-ip.org> (Cristian Gutierrez's message of "Wed, 13 Oct 2004 17:13:18 -0300")
Cristian Gutierrez <crgutier@dcc.uchile.cl> writes:
> 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:
You could move pop-limit down to the function instead to make the
bookmarks easier to write.
> 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).
>
> ,----
> | ("analytics" . (progn
> | (condition-case nil
> | (gnus-summary-pop-limit)
> | (error nil))
> | (gnus-summary-limit-to-author "analytics\\|dads")))
> `----
This works for me. Maybe you forgot to reevaluate the defvar.
Remember that evaluating a defvar, e.g. with `C-j', does not change
the value if the variable is already defined. To set it
unconditionally you can use `C-M-x'.
--
Jesper Harder <http://purl.org/harder/>
next prev parent reply other threads:[~2004-10-13 21:42 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
2004-10-13 21:42 ` Jesper Harder [this message]
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=m3d5zmwb0v.fsf@defun.localdomain \
--to=harder@ifa.au.dk \
/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).