From: "leo" <halloleo@noospaam.myrealbox.com>
Subject: Re: elisp question: how to walk through a variable like special-display-buffer-names
Date: Wed, 14 Jan 2004 10:58:48 +1100 [thread overview]
Message-ID: <bu20n0$278$1@otis.netspace.net.au> (raw)
In-Reply-To: uk73vlvct.fsf@sdm.de
i couldn't find joakim's direct reply post, that's why i answer to klaus'
reply:
"Klaus Berndl" <klaus.berndl@sdm.de> wrote in message
news:uk73vlvct.fsf@sdm.de...
> On Tue, 13 Jan 2004, Joakim Hove wrote:
>
> >
> > leo <leo@bella.local> writes:
> >
> > >i want to walk through the list in special-display-buffer-names (and
> > >special-display-regexps), in order to find out if the left parameter is
> > >set in the contained alist.
> >
> > Well,
> >
> > I personally like (dolist) a lot:
>>
> > (dolist (el list)
> > ;; do something with el
> > (let ((buffer (car el))
> > (alist (cdr el)))
> > ;;
> > ;; But then ...
> > ;;
> > ))
ok, i just hoped that there might be a function in emacs for that: emacs has
so many variables which contain lists of lists or regexps...
but thanks for the tip with dolist!
> > I dont understand what you mean with 'contained alist' - but you might
> > need the assoc function.
well, special-display-buffer-names can have the follwoing structure:
'( (name-of-buffer1 (parameter1 . value_a) (parameter2 . value_b) ...)
(name-of-buffer2 (parameter1 . value_c) (parameter2 . value_d) ...)
(name-of-buffer2 (parameter1 . value_e) (parameter2 . value_f) ...)
...)
and i want to pull out e.g. the value for parameter2 for a specific buffer
name, say name-of-buffer2 with a function i feed with the parameter-symbol
and the buffer-name.
cheers, leo
next prev parent reply other threads:[~2004-01-13 23:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-13 13:45 elisp question: how to walk through a variable like special-display-buffer-names leo
2004-01-13 15:07 ` Joakim Hove
2004-01-13 15:30 ` Klaus Berndl
2004-01-13 23:58 ` leo [this message]
2004-01-14 5:23 ` Martin Rydstr|m
2004-01-13 15:42 ` Jesper Harder
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='bu20n0$278$1@otis.netspace.net.au' \
--to=halloleo@noospaam.myrealbox.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).