unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Konrad Podczeck <konrad.podczeck@univie.ac.at>, 40238@debbugs.gnu.org
Subject: bug#40238: Trying to customize the ispell choices buffer via display-buffer-alist has no effect
Date: Thu, 26 Mar 2020 16:29:22 +0100	[thread overview]
Message-ID: <6bcd41b9-6370-cbb5-ac6c-c285c17bc22a@gmx.at> (raw)
In-Reply-To: <05D843B2-103A-4DD5-8440-0454DC422643@univie.ac.at>

 > There is no effect if in display-buffer-alist the ispell choices buffer is customized, e.g. in the form
 >
 >     ("\\*Choices\\*"
 >      (display-buffer-reuse-window display-buffer-pop-up-frame)
 >       (pop-up-frame-parameters
 >       (tool-bar-lines . 0)
 >       (font . "Monaco-12")
 >       (left . 778)
 >       (top . 280) (height . 12) (width . 78)
 >       ))

Intentionally so.  IIRC, displaying *Choices* was initially even more
rigid - it didn't use 'display-buffer' at all.

The solution is to set 'ispell-choices-win-default-height' to a very
large value so that in practice 'split-window' can never make a window
that high.  If after some time you come to the conclusion that this
trick works satisfactorily, we can mention it somewhere at your choice.

martin





  reply	other threads:[~2020-03-26 15:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-26 14:56 bug#40238: Trying to customize the ispell choices buffer via display-buffer-alist has no effect Konrad Podczeck
2020-03-26 15:29 ` martin rudalics [this message]
2020-03-26 15:52   ` Konrad Podczeck
2020-03-26 16:23     ` Konrad Podczeck
2020-03-26 17:36     ` martin rudalics
2020-03-26 18:05       ` Konrad Podczeck
2020-03-26 18:45         ` martin rudalics
2020-03-27  1:12           ` Konrad Podczeck
2020-03-27  9:02             ` martin rudalics
2020-03-27 11:22               ` Konrad Podczeck
2020-03-28 18:38                 ` martin rudalics
2022-02-10  7:20 ` Lars Ingebrigtsen
2022-03-12 22:42   ` Lars Ingebrigtsen

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=6bcd41b9-6370-cbb5-ac6c-c285c17bc22a@gmx.at \
    --to=rudalics@gmx.at \
    --cc=40238@debbugs.gnu.org \
    --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 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).