From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: Re: Finding a buffer given a symbolp pointer... err...
Date: 20 Dec 1995 02:05:40 +0100 [thread overview]
Message-ID: <w8s91k8h7dn.fsf@gymir.ifi.uio.no> (raw)
In-Reply-To: Wes Hardaker's message of Tue, 19 Dec 1995 14:35:46 -0800
Wes Hardaker <hardaker@ece.ucdavis.edu> writes:
> This works. However, I also want to be able to follow the rapidly
> moving targets: gnus-article-buffer and gnus-summary-buffer. It
> seems to me rather than
>
> (setq gnus-picons-display-where 'gnus-summary-buffer)
>
> one should do something more along the lines of the rest of the sgnus
> config world:
>
> (setq gnus-picons-display-where 'summary)
Well, if you went with the first, you could say something like:
(cond ((symbolp gnus-picons-display-where)
(symbol-value gnus-picons-display-where))
((strinp gnus-picons-display-where)
gnus-picons-display-where))
Or something like that. If you go with the latter, you have one more
indirection:
(setq sym (cdr (assq gnus-picons-display-where gnus-window-to-buffer)))
And then you'd have to to the `cond' up there on `sym'.
I think having `summary', `article', `picons' as possible values
sounds nice...
--
(domestic pets only, the antidote for overdose, milk.)
larsi@ifi.uio.no * Lars Ingebrigtsen
prev parent reply other threads:[~1995-12-20 1:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-12-19 22:35 Wes Hardaker
1995-12-19 23:36 ` Wes Hardaker
1995-12-20 1:05 ` Lars Magne Ingebrigtsen [this message]
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=w8s91k8h7dn.fsf@gymir.ifi.uio.no \
--to=larsi@ifi.uio.no \
/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).