From: Cristian Gutierrez <crgutier@dcc.uchile.cl>
Subject: Re: Bookmarking summary limit commands?
Date: Wed, 13 Oct 2004 21:23:19 -0300 [thread overview]
Message-ID: <87y8iagnbc.fsf@guti.no-ip.org> (raw)
In-Reply-To: <m3d5zmwb0v.fsf@defun.localdomain>
Jesper Harder wrote:
> 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.
Good idea.
[...]
> 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'.
Couldn't be more right: I was merely doing a `C-x C-e' in front of the
defvar. Now it works flawlessly. Thanks again!
If anyone feels like trying this, here it is what I'm using now:
,----
| (defvar my-limit-bookmark-alist
| '(("job" . (gnus-summary-limit-to-author "jobdomain.com"))
| ("thesis" . (gnus-summary-limit-to-author "someteacher")))
| "Alist of limit bookmarks.")
|
| (defun my-limit-bookmark (limit)
| "Apply a limit in `my-limit-bookmark-alist'."
| (interactive
| (list (completing-read "Bookmark: " my-limit-bookmark-alist)))
| (condition-case nil
| (gnus-summary-pop-limit)
| (error nil))
| (eval (cdr (assoc limit my-limit-bookmark-alist))))
|
| (define-key gnus-summary-mode-map "/q" 'my-limit-bookmark)
`----
--
Cristian Gutierrez http://www.dcc.uchile.cl/~crgutier
crgutier[@]dcc.uchile.cl Jabber:crgutier@jabber.org
Hi! I'm a shareware signature! Send $5 if you use me, send $10 for manual!
next prev parent reply other threads:[~2004-10-14 0:23 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
2004-10-14 0:23 ` Cristian Gutierrez [this message]
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=87y8iagnbc.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).