From: Konrad Podczeck <konrad.podczeck@univie.ac.at>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 55264@debbugs.gnu.org
Subject: bug#55264: A problem with display-buffer-alist
Date: Fri, 6 May 2022 02:56:17 +0200 [thread overview]
Message-ID: <0A916706-9939-4222-9F15-4213D52B5B95@univie.ac.at> (raw)
In-Reply-To: <83ilqk346f.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1157 bytes --]
Reversing commit (by Po Lu) 5adc84a27b86cdbd048ee3ebc023549c928f7425 (both in nsmenu.m and in tooltip.el) solved the problem.
Konread
> Am 05.05.2022 um 08:05 schrieb Eli Zaretskii <eliz@gnu.org>:
>
>> From: Konrad Podczeck <konrad.podczeck@univie.ac.at>
>> Date: Thu, 5 May 2022 01:25:44 +0200
>>
>> With a fresh build, I have the following problem:
>>
>> Make an init file just containing the lines:
>>
>> (setq
>> display-buffer-base-action
>> '((display-buffer-reuse-window display-buffer-pop-up-frame)
>> (reusable-frames . t))
>> display-buffer-alist
>> '(("[.]"
>> (display-buffer-reuse-window display-buffer-pop-up-frame)
>> (pop-up-frame-parameters
>> (left . 100)
>> ))))
>>
>>
>> Start the app. Open any file, say foo.tex, and do "M-x
>> context-menu-mode". In the frame showing foo.tex, scroll a bit. Then,
>> using the mouse, select some text and use the right mouse button to open
>> the context menu. If I try to choose any item in the context menu, the
>> app quits unexpectedly. This quitting is not registered as a crash by
>> the OS.
>
> Seems to be specific to macOS? I cannot reproduce here.
[-- Attachment #2: Type: text/html, Size: 2998 bytes --]
next prev parent reply other threads:[~2022-05-06 0:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 23:25 bug#55264: A problem with display-buffer-alist Konrad Podczeck
2022-05-05 6:05 ` Eli Zaretskii
2022-05-05 21:51 ` Konrad Podczeck
2022-05-06 0:56 ` Konrad Podczeck [this message]
2022-05-08 14:35 ` bug#55299: " Konrad Podczeck
2022-05-09 9:52 ` Lars Ingebrigtsen
2022-05-09 9:53 ` Lars Ingebrigtsen
2022-05-09 11:33 ` Konrad Podczeck
2022-05-09 11:45 ` 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=0A916706-9939-4222-9F15-4213D52B5B95@univie.ac.at \
--to=konrad.podczeck@univie.ac.at \
--cc=55264@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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).