all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Konrad Podczeck <konrad.podczeck@univie.ac.at>
Cc: 37840@debbugs.gnu.org, Juri Linkov <juri@linkov.net>
Subject: bug#37840: Missing in the Emacs manuals:
Date: Sun, 10 Nov 2019 19:33:17 +0100	[thread overview]
Message-ID: <7e6f19a1-fa45-0315-9d22-9bbb7223d695@gmx.at> (raw)
In-Reply-To: <AA4B102C-098C-4347-AF39-ED3F848EB302@univie.ac.at>

 > So what is the correct customization if I wish to have _every_
 > buffer in its own (new) frame, just different buffer types having
 > different frame types, the latter meaning different geometry, fonts
 > etc.?

I'm afraid there's none.  The reason is a technical one.  The speedbar
code uses 'switch-to-buffer' internally to switch to its own buffer in
its own window on its own frame.  Any customization of
'switch-to-buffer' to do something like switch to _any_ buffer in
another frame will make the speedbar choke because its buffer won't be
displayed in the same window where it expects it.

Note that 'switch-to-buffer-obey-display-actions' is a new addition
that has not been yet tested extensively.  In earlier versions you had
no possibility customizing the behavior of 'switch-to-buffer'.  In
practice, it always used the selected window for displaying the
buffer.

You could try to replace the regexp in 'display-buffer-alist' with a
function that filters out all buffers that are in a sense special like
the speedbar buffer but I'm afraid that you will encounter too many
instances of internal uses of 'switch-to-buffer' so you will soon or
later get tired of such an approach.

The other approach is to specify in that function all buffers that
interest you (mostly based on the extension of the file they visit)
instead of _every_ buffer.  Would that be so difficult?

Finally, note that if you make sure that practically all windows you
use are strongly dedicated to their buffers, 'switch-to-buffer' calls
will respect that.  For example, if with emacs -Q I do

(custom-set-variables
  '(display-buffer-base-action
    '((display-buffer-reuse-window display-buffer-pop-up-frame)
      (dedicated . t)
      (reusable-frames . 0))))

(set-window-dedicated-p nil t)

and then choose *Messages* from the Buffers menu, it will pop up in a
new frame and the speedbar will work normally.  Note, however, that
strongly dedicated windows may have other disadvantages you will have
to get used to.

martin





  reply	other threads:[~2019-11-10 18:33 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-21  0:39 bug#37840: Missing in the Emacs manuals: Konrad Podczeck
2019-10-22  8:43 ` martin rudalics
2019-10-23  7:25   ` Konrad Podczeck
2019-10-23  7:46     ` martin rudalics
2019-10-28 17:37       ` Konrad Podczeck
2019-10-28 18:13         ` martin rudalics
2019-10-28 19:04           ` Konrad Podczeck
2019-10-29  9:28             ` martin rudalics
2019-10-30  0:56               ` Konrad Podczeck
2019-10-30  8:14                 ` martin rudalics
2019-10-30 20:37                   ` Konrad Podczeck
2019-10-31  7:59                     ` martin rudalics
2019-11-02 21:47                       ` Konrad Podczeck
2019-11-04  9:06                         ` martin rudalics
2019-11-04 11:20                           ` Konrad Podczeck
2019-11-04 18:27                             ` martin rudalics
     [not found]                               ` <A8BBF7A4-BFE0-44BB-BCB3-B26477FFC946@univie.ac.at>
2019-11-04 19:10                                 ` martin rudalics
2019-11-06 22:41                                   ` Juri Linkov
2019-11-07  8:39                                     ` martin rudalics
2019-11-07 21:58                                       ` Juri Linkov
2019-11-08  9:20                                         ` martin rudalics
2019-11-08 11:04                                           ` Konrad Podczeck
2019-11-08 18:27                                             ` martin rudalics
2019-11-08 21:12                                               ` Konrad Podczeck
2019-11-09  9:01                                                 ` martin rudalics
2019-11-10 16:44                                                   ` Konrad Podczeck
2019-11-10 18:33                                                     ` martin rudalics [this message]
2019-11-14 10:03                                                       ` Eli Zaretskii
2019-11-14 18:18                                                         ` martin rudalics
2019-11-14 18:35                                                           ` Eli Zaretskii
2019-11-15  8:50                                                             ` martin rudalics
2019-11-22 13:09                                                       ` Konrad Podczeck
2019-11-22 17:49                                                         ` martin rudalics
2019-11-22 19:22                                                           ` Eli Zaretskii
2019-11-23  1:42                                                             ` Konrad Podczeck
2019-11-23  8:16                                                               ` martin rudalics
2019-11-25 23:47                                                                 ` Konrad Podczeck
2019-11-26  9:32                                                                   ` martin rudalics
2019-12-02  1:35                                                                     ` Konrad Podczeck
2019-12-02  9:41                                                                       ` martin rudalics
2019-11-23  8:15                                                             ` martin rudalics
2019-11-23  9:49                                                               ` Eli Zaretskii
2019-11-26  9:31                                                                 ` martin rudalics
2019-11-26  9:42                                                                   ` martin rudalics
2020-09-20 11:12                                                                 ` Lars Ingebrigtsen
2019-11-10 20:11                                           ` Juri Linkov

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=7e6f19a1-fa45-0315-9d22-9bbb7223d695@gmx.at \
    --to=rudalics@gmx.at \
    --cc=37840@debbugs.gnu.org \
    --cc=juri@linkov.net \
    --cc=konrad.podczeck@univie.ac.at \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.