unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Trust me I am a Doctor <pillule@riseup.net>
To: Juri Linkov <juri@linkov.net>
Cc: 49069@debbugs.gnu.org
Subject: bug#49069: 28.0.50; [PATCH] Use display-buffer for re-builder
Date: Thu, 08 Jul 2021 23:12:21 +0200	[thread overview]
Message-ID: <87eec85wmb.fsf@riseup.net> (raw)
In-Reply-To: <87im1kya94.fsf@mail.linkov.net>


Juri Linkov <juri@linkov.net> writes:

> Also I don't know if there is any chance to fix Org-mode.
> Anyway, I'm using such workaround for Org-mode problem:
>
> #+begin_src emacs-lisp
> ;; Unfortunately, Org window customization has no effect because
> ;; ‘display-buffer-alist’ is ignored in ‘org-no-popups’
> ;; until ‘org-switch-to-buffer-other-window’ is overridden below:
> (defalias 'org-switch-to-buffer-other-window 'switch-to-buffer-other-window)
>
> ;; This allows such user customizations:
> (push '("\\`\\*Org \\(Links\\|Select\\)\\*\\'"
>         display-buffer-below-selected
>         (window-height . fit-window-to-buffer)
>         (preserve-size . (nil . t)))
>       display-buffer-alist)
> #+end_src

Nice, I was aware of overriding 'org-switch-to-buffer-other-window but
didn't customized anything yet for theses buffers.


Constantine Vetoshev <gepardcv@gmail.com> writes:

> Thank you for bringing this to my attention. I’ll test the display-buffer-base-action approach over
> the next couple of days, and if it works as I expect, I’ll update the Perspective README.
>
> Note that Juri’s example is not quite the same as mine. Please test with this instead:
>
> (customize-set-variable 'display-buffer-base-action
>  '((display-buffer-reuse-window display-buffer-same-window)
>  (reusable-frames . t)))

Ok I will update the recipe with yours -even if until now I had no issue
with emacs creating new frames. (I know ediff do it but I also now the
setting to tweak).

For now the only package that seems really difficult to work with is Magit;
transient.el is a brillant idea until you cannot see its whole windows,
but that's beyond the scope of this patch ;

Thank you both.

--





  reply	other threads:[~2021-07-08 21:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-17  1:16 bug#49069: 28.0.50; [PATCH] Use display-buffer for re-builder pillule
2021-06-17  4:10 ` pillule
2021-06-17 14:50   ` pillule
2021-06-29 15:51     ` Trust me I am a Doctor
2021-06-29 20:47       ` Juri Linkov
2021-06-29 21:50         ` Trust me I am a Doctor
2021-06-30 19:49           ` Juri Linkov
2021-07-08 15:18             ` Trust me I am a Doctor
2021-07-08 17:40               ` Juri Linkov
2021-07-08 21:12                 ` Trust me I am a Doctor [this message]
     [not found]                   ` <87bl7c5wgl.fsf@riseup.net>
     [not found]                     ` <7355eaf3-5ae2-46e7-80f5-d3d23ffff7d8@Spark>
2021-07-09  9:00                       ` bug#49069: Fwd: " Trust me I am a Doctor
2021-07-08 18:38               ` Constantine Vetoshev

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=87eec85wmb.fsf@riseup.net \
    --to=pillule@riseup.net \
    --cc=49069@debbugs.gnu.org \
    --cc=juri@linkov.net \
    /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 public inbox

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

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).