unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Kevin Rodgers <ihs_4664@yahoo.com>
Subject: Re: using special-display-regexps
Date: Fri, 18 Jun 2004 09:34:30 -0600	[thread overview]
Message-ID: <40D30B86.9060503@yahoo.com> (raw)
In-Reply-To: u7ju5wedj.fsf@hotmail.com

Mathias Dahl wrote:
 > Michael Slass <miknrene@drizzle.com> writes:
 >>>I'm trying to teach emacs to treat some buffers in a special way using
 >>>this code that is supposed to work:
 >>>
 >>>(setq special-display-regexps
 >>>     '(("jabber-chat"
 >>>     ((top . 10) (height . 5) (left . 200)))))
 >>>
 >>>In the documentation string thew following can be seen:
 >>>
 >>> *List of regexps saying which buffers should have their own special
 >>> frames.  If a buffer name matches one of these regexps, it gets its
 >>> own frame.  Displaying a buffer whose name is in this list makes a
 >>> special frame for it using `special-display-function'.
 >>>
 >>> An element of the list can be a list instead of just a string.
 >>> There are two ways to use a list as an element:
 >>>   (REGEXP FRAME-PARAMETERS...)   (REGEXP FUNCTION OTHER-ARGS...)
 >>> In the first case, FRAME-PARAMETERS are used to create the frame.
 >>>
 >>>It works only half way, emacs opens up matching buffers in a new
 >>>frame, but the supplied frame parameters is not applied.
 >>
 >>The frame parameters should each be elements at the same level as
 >>"jabber-chat", rather than in their own enclosing list, as you've got it.
 >>Also, it's better to use (add-to-list ...) rather than setq in this
 >>context, because setq will clobber anything that's already there.
 >>
 >>Put those together, and I think you get something like this:
 >>
 >>(add-to-list 'special-display-regexps
 >>      '("jabber-chat" (top . 10) (height . 5) (left . 200)))
 >>
 >
 > Aaaaaah! Yes, that did the trick! Is this just a problem with me
 > or could the documentation be more clear on this subject? I have
 > fiddles with frame parameters from time to time and then I had
 > always needed to enclose them in their own list. This is the
 > reason I thought I had to do the same now.

Yes, I think the correct way to denote that data structure would be:

(REGEXP . FRAME-PARAMETERS)	; FRAME-PARAMETERS is an association list
				; of (PARAMETER . VALUE) conses

or

(REGEXP (PARAMETER . VALUE) ...)

-- 
Kevin Rodgers

      parent reply	other threads:[~2004-06-18 15:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-17 22:19 using special-display-regexps Barman Brakjoller
2004-06-17 22:23 ` Barman Brakjoller
2004-06-17 23:43 ` Michael Slass
2004-06-18  6:48   ` Mathias Dahl
2004-06-18 14:44     ` Michael Slass
2004-06-18 15:34     ` Kevin Rodgers [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

  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=40D30B86.9060503@yahoo.com \
    --to=ihs_4664@yahoo.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).