From: Konrad Podczeck <konrad.podczeck@univie.ac.at>
To: martin rudalics <rudalics@gmx.at>
Cc: 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 17:23:07 +0100 [thread overview]
Message-ID: <A05F9024-8F08-493B-B12D-A221320B4D63@univie.ac.at> (raw)
In-Reply-To: <835DF2AB-2C8A-49B4-8C96-6553A6B1A148@univie.ac.at>
Remembering what you told me, the problem with “x” to exit ispell is solvable by inserting (dedicated . t) in the customization below. The other problem is not affected by this.
Konrad
> Am 26.03.2020 um 16:52 schrieb Konrad Podczeck <konrad.podczeck@univie.ac.at>:
>
> Thanks!
>
> Basically this works fine. However, when I type ‘x’ to exit ispell, the buffer which was spelled appears a second time in the frame that showed the choices. If I type ‘q’ to quit ispell, the answer to the “yes-or-no” prompt has not the intended effect but becomes written in the frame showing the choices.
>
> Konrad
>
>
>> Am 26.03.2020 um 16:29 schrieb martin rudalics <rudalics@gmx.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
>
next prev parent reply other threads:[~2020-03-26 16:23 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
2020-03-26 15:52 ` Konrad Podczeck
2020-03-26 16:23 ` Konrad Podczeck [this message]
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=A05F9024-8F08-493B-B12D-A221320B4D63@univie.ac.at \
--to=konrad.podczeck@univie.ac.at \
--cc=40238@debbugs.gnu.org \
--cc=rudalics@gmx.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).