[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: The window-pub branch

From: grischka
Subject: Re: The window-pub branch
Date: Mon, 22 Nov 2010 17:18:42 +0100
User-agent: Thunderbird (Windows/20090812)

martin rudalics wrote:
 > How can the user override specifiers for buffers that don't match
 > unambiguous naming conventions (ediff, dired, ...)?

Another user option, say `display-buffer-symbols'?  The application
would pass a symbol in the call and make sure it has an entry in the
`display-buffer-specifiers' list  which associates symbols like
'other-window with specifiers.   ediff could add entries like 'ediff-A
and 'ediff-B to `display-buffer-specifiers' and the user, in
`display-buffer-symbols', could provide an entry to override them.

But I'm not sure how to resolve the conflict when a matching entry can
be found in both `display-buffer-names' and `display-buffer-symbols'.

A symbol entry is more specific.

However I'd maybe just put names/regexps/symbols in the same
structure.  Such as:

   (setq display-buffer-specifiers '(
      ((a-symbol "*b-name*" (r . "^c-regexp.+"))

That way the user can express preferences by the order naturally.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]