GNU bug report logs -
#69140
30.0.50; [elpa/vertico] Emacs with vertico-mode freezes if font is too big
Previous Next
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 69140 in the body.
You can then email your comments to 69140 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#69140
; Package
emacs
.
(Thu, 15 Feb 2024 11:59:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Aleksandr Vityazev <avityazev <at> disroot.org>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Thu, 15 Feb 2024 11:59:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
Hi,
Vertico version 1.7, version 1.3 has also been tested, is incompatible
with the changes made by the commit -
caea0c1649d1df96b811c1388fde396e66bc356b. This commit was found via
git bisect.
To reproduce:
1. Run emacs -Q
2. M-x load-library vertico RET
3. M-x vertico-mode RET
4. Set a large font, the following is suitable for my 13 inch monitor:
(set-face-attribute 'default nil :family "monospace" :height 440)
5. Call M-x
Emacs should freeze, sometimes you can unfreeze it with a few presses
of C-g
profiler-report below:
#+begin_example
5555 81% - command-execute
5555 81% - call-interactively
5555 81% - byte-code
5555 81% - read-extended-command
5555 81% - read-extended-command-1
5555 81% - completing-read
5555 81% - completing-read-default
5555 81% - apply
5555 81% - vertico--advice
5555 81% - apply
5555 81% - #<compiled -0x109324e03480587c>
5555 81% - read-from-minibuffer
2795 40% - redisplay_internal (C function)
76 1% + window--resize-root-window-vertically
50 0% + eval
12 0% + file-remote-p
12 0% + mode-line-default-help-echo
2520 36% - minibuffer-error-function
2520 36% - minibuffer-message
2520 36% - sit-for
2516 36% - redisplay
2516 36% - redisplay_internal (C function)
72 1% - window--resize-root-window-vertically
56 0% + window-sizable
8 0% + walk-window-tree
4 0% + window--resize-this-window
68 0% + eval
32 0% + mode-line-default-help-echo
20 0% + file-remote-p
4 0% input-pending-p
135 1% + vertico--exhibit
1104 16% Automatic GC
180 2% + redisplay_internal (C function)
8 0% + timer-event-handler
0 0% ...
#+end_example
In GNU Emacs 30.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version
3.24.37, cairo version 1.16.0)
System Description: Guix System
Configured using:
'configure
CONFIG_SHELL=/gnu/store/v9p25q9l5nnaixkhpap5rnymmwbhf9rp-bash-minimal-5.1.16/bin/bash
SHELL=/gnu/store/v9p25q9l5nnaixkhpap5rnymmwbhf9rp-bash-minimal-5.1.16/bin/bash
--prefix=/gnu/store/f9faac619qdhgybd0ddfvwdazcvv41qq-emacs-rrr-next-30.0.50-49.3a93e30
--enable-fast-install --with-pgtk --without-libsystemd
--with-tree-sitter --with-native-compilation --with-cairo
--with-modules --with-native-compilation=aot --disable-build-details'
--
Best regards,
Aleksandr Vityazev
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#69140
; Package
emacs
.
(Thu, 15 Feb 2024 13:48:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 69140 <at> debbugs.gnu.org (full text, mbox):
> Cc: mail <at> daniel-mendler.de
> Date: Thu, 15 Feb 2024 14:23:28 +0300
> From: Aleksandr Vityazev via "Bug reports for GNU Emacs,
> the Swiss army knife of text editors" <bug-gnu-emacs <at> gnu.org>
>
> Vertico version 1.7, version 1.3 has also been tested, is incompatible
> with the changes made by the commit -
> caea0c1649d1df96b811c1388fde396e66bc356b. This commit was found via
> git bisect.
>
> To reproduce:
> 1. Run emacs -Q
> 2. M-x load-library vertico RET
> 3. M-x vertico-mode RET
> 4. Set a large font, the following is suitable for my 13 inch monitor:
> (set-face-attribute 'default nil :family "monospace" :height 440)
> 5. Call M-x
> Emacs should freeze, sometimes you can unfreeze it with a few presses
> of C-g
Thanks, but why do you think the bug is in Emacs and not in vertico?
The fact that you can unfreeze Emacs with C-g indicates that some Lisp
is involved in what probably is an infloop. At the very least, could
you please catch a Lisp backtrace when you type C-g, so that we could
see what Lisp is involved? Also, what exactly does vertico do with
resizing the mini-window, and what should be the value of
resize-mini-windows for reproducing this issue.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#69140
; Package
emacs
.
(Thu, 15 Feb 2024 14:30:02 GMT)
Full text and
rfc822 format available.
Message #11 received at 69140 <at> debbugs.gnu.org (full text, mbox):
Eli Zaretskii <eliz <at> gnu.org> writes:
>> Cc: mail <at> daniel-mendler.de
>> Date: Thu, 15 Feb 2024 14:23:28 +0300
>> From: Aleksandr Vityazev via "Bug reports for GNU Emacs,
>> the Swiss army knife of text editors" <bug-gnu-emacs <at> gnu.org>
>>
>> Vertico version 1.7, version 1.3 has also been tested, is incompatible
>> with the changes made by the commit -
>> caea0c1649d1df96b811c1388fde396e66bc356b. This commit was found via
>> git bisect.
>>
>> To reproduce:
>> 1. Run emacs -Q
>> 2. M-x load-library vertico RET
>> 3. M-x vertico-mode RET
>> 4. Set a large font, the following is suitable for my 13 inch monitor:
>> (set-face-attribute 'default nil :family "monospace" :height 440)
>> 5. Call M-x
>> Emacs should freeze, sometimes you can unfreeze it with a few presses
>> of C-g
>
> Thanks, but why do you think the bug is in Emacs and not in vertico?
> The fact that you can unfreeze Emacs with C-g indicates that some Lisp
> is involved in what probably is an infloop. At the very least, could
> you please catch a Lisp backtrace when you type C-g, so that we could
> see what Lisp is involved? Also, what exactly does vertico do with
> resizing the mini-window, and what should be the value of
> resize-mini-windows for reproducing this issue.
Also, if at all possible, please attempt to interrupt Emacs while it is
so frozen under GDB until you have collected several unique backtraces
containing entries for `redisplay_internal', and post them here.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#69140
; Package
emacs
.
(Thu, 15 Feb 2024 17:16:01 GMT)
Full text and
rfc822 format available.
Message #14 received at 69140 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
On 2024-02-15 15:46, Eli Zaretskii wrote:
>> Cc: mail <at> daniel-mendler.de
>> Date: Thu, 15 Feb 2024 14:23:28 +0300
>> From: Aleksandr Vityazev via "Bug reports for GNU Emacs,
>> the Swiss army knife of text editors" <bug-gnu-emacs <at> gnu.org>
>>
>> Vertico version 1.7, version 1.3 has also been tested, is incompatible
>> with the changes made by the commit -
>> caea0c1649d1df96b811c1388fde396e66bc356b. This commit was found via
>> git bisect.
>>
>> To reproduce:
>> 1. Run emacs -Q
>> 2. M-x load-library vertico RET
>> 3. M-x vertico-mode RET
>> 4. Set a large font, the following is suitable for my 13 inch monitor:
>> (set-face-attribute 'default nil :family "monospace" :height 440)
>> 5. Call M-x
>> Emacs should freeze, sometimes you can unfreeze it with a few presses
>> of C-g
>
> Thanks, but why do you think the bug is in Emacs and not in vertico?
> The fact that you can unfreeze Emacs with C-g indicates that some Lisp
> is involved in what probably is an infloop. At the very least, could
> you please catch a Lisp backtrace when you type C-g, so that we could
> see what Lisp is involved? Also, what exactly does vertico do with
> resizing the mini-window, and what should be the value of
> resize-mini-windows for reproducing this issue.
resize-mini-windows is set to default ‘grow-only’
All vertico customs are also default.
I couldn’t reproduce it any other way, but it seemed to me that there
might be some problems with the redisplay.
I couldn't get a backtrace because if you set the debug-on-quit to t,
then C-g no longer helps. 2 screenshots in the attachment, but the
backtrace is only partially visible.
I'm not very familiar with gdb, I'll look into the matter and attach the
backtraces.
[5364223907583875189_119.jpg (image/jpeg, attachment)]
[5364223907583875234_119.jpg (image/jpeg, attachment)]
[Message part 4 (text/plain, inline)]
--
Best regards,
Aleksandr Vityazev
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#69140
; Package
emacs
.
(Wed, 21 Feb 2024 16:17:02 GMT)
Full text and
rfc822 format available.
Message #17 received at 69140 <at> debbugs.gnu.org (full text, mbox):
On 2024-02-15 22:29, Po Lu wrote:
> Eli Zaretskii <eliz <at> gnu.org> writes:
>
>>> Cc: mail <at> daniel-mendler.de
>>> Date: Thu, 15 Feb 2024 14:23:28 +0300
>>> From: Aleksandr Vityazev via "Bug reports for GNU Emacs,
>>> the Swiss army knife of text editors" <bug-gnu-emacs <at> gnu.org>
>>>
>>> Vertico version 1.7, version 1.3 has also been tested, is incompatible
>>> with the changes made by the commit -
>>> caea0c1649d1df96b811c1388fde396e66bc356b. This commit was found via
>>> git bisect.
>>>
>>> To reproduce:
>>> 1. Run emacs -Q
>>> 2. M-x load-library vertico RET
>>> 3. M-x vertico-mode RET
>>> 4. Set a large font, the following is suitable for my 13 inch monitor:
>>> (set-face-attribute 'default nil :family "monospace" :height 440)
>>> 5. Call M-x
>>> Emacs should freeze, sometimes you can unfreeze it with a few presses
>>> of C-g
>>
>> Thanks, but why do you think the bug is in Emacs and not in vertico?
>> The fact that you can unfreeze Emacs with C-g indicates that some Lisp
>> is involved in what probably is an infloop. At the very least, could
>> you please catch a Lisp backtrace when you type C-g, so that we could
>> see what Lisp is involved? Also, what exactly does vertico do with
>> resizing the mini-window, and what should be the value of
>> resize-mini-windows for reproducing this issue.
>
> Also, if at all possible, please attempt to interrupt Emacs while it is
> so frozen under GDB until you have collected several unique backtraces
> containing entries for `redisplay_internal', and post them here.
No backtrace yet, but I found another reproducer without vertico, all
used packages are from Emacs core.
Configured using:
'configure
CONFIG_SHELL=/gnu/store/v9p25q9l5nnaixkhpap5rnymmwbhf9rp-bash-minimal-5.1.16/bin/bash
SHELL=/gnu/store/v9p25q9l5nnaixkhpap5rnymmwbhf9rp-bash-minimal-5.1.16/bin/bash
--prefix=/gnu/store/1gij4r65kyw6lm2m9clqpraigivjgzq9-emacs-test-test
--enable-fast-install --with-pgtk --without-libsystemd
--enable-checking=yes,glyphs --enable-check-lisp-object-type
--with-native-compilation=no --with-cairo --with-modules
--disable-build-details 'CFLAGS=-O0 -g3''
1. Run emacs -Q
2. Paste the following code into the scratch buffer and run eval-buffer
--8<---------------cut here---------------start------------->8---
(load-library "transient")
(fido-vertical-mode 1)
(defclass test-transient-multi (transient-option) ()
((key :initform "-")
(argument :initform "-")
(multi-value :initform t)
(reader :initform completing-read-multiple))
"")
(transient-define-argument test:--1 ()
:description "test1"
:class 'transient-option
:shortarg "a"
:argument "test1=")
(transient-define-argument test:--2 ()
:description "test2"
:class 'test-transient-multi
:key "r"
:argument "test2"
:multi-value t
:prompt "Test2: "
:reader (lambda (prompt _initial-input _history)
(completing-read-multiple
prompt
'("nonsdlslde" "slsdl" "2323" "ldslld" "30203" "llx" "ldslsd"))))
(transient-define-argument test:--3 ()
:description "test3"
:class 'test-transient-multi
:key "l"
:argument "test3"
:multi-value t
:prompt "Test3: "
:reader (lambda (prompt _initial-input _history)
(completing-read-multiple
prompt
'("nonsdlslde" "slsdl" "2323" "ldslld" "30203" "llx" "ldslsd"))))
(transient-define-argument test:--4 ()
:description "test4"
:class 'test-transient-multi
:key "y"
:argument "test4"
:multi-value t
:prompt "Test4: "
:reader (lambda (prompt _initial-input _history)
(completing-read-multiple
prompt
'("nonsdlslde" "slsdl" "2323" "ldslld" "30203" "llx" "ldslsd"))))
(defun test-hello ()
""
(interactive)
(message "hello"))
(transient-define-prefix test-dispatch ()
["Test parameters"
(test:--1)
(test:--2)
(test:--3)
(test:--4)
]
[["Search"
("s" "test" test-hello)]])
(set-face-attribute 'default nil :family "monospace" :height 440)
--8<---------------cut here---------------end--------------->8---
3. M-x test-dispatch
4. Try playing with the parameters test1, test2, test3, test4. At the
same time you can put Emacs into full screen mode and back into windowed
mode, where it will occupy half of the screen. Initially, calling the
parameters test1, test2, test3, test4 in the transient window will be
delayed and everything can be canceled with C-g, after a few repetitions
Emacs hangs completely.
--
Best regards,
Aleksandr Vityazev
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#69140
; Package
emacs
.
(Wed, 21 Feb 2024 17:11:02 GMT)
Full text and
rfc822 format available.
Message #20 received at 69140 <at> debbugs.gnu.org (full text, mbox):
> From: Aleksandr Vityazev <avityazev <at> disroot.org>
> Cc: Eli Zaretskii <eliz <at> gnu.org>, 69140 <at> debbugs.gnu.org,
> mail <at> daniel-mendler.de
> Date: Wed, 21 Feb 2024 19:15:57 +0300
>
> 3. M-x test-dispatch
> 4. Try playing with the parameters test1, test2, test3, test4. At the
> same time you can put Emacs into full screen mode and back into windowed
> mode, where it will occupy half of the screen. Initially, calling the
> parameters test1, test2, test3, test4 in the transient window will be
> delayed and everything can be canceled with C-g, after a few repetitions
> Emacs hangs completely.
Thanks, but I don't understand what to do after "m-x test-dispatch".
Please tell in more details what you mean in Step 4, in terms of what
I need to type after "M-x test-dispatch". (I tried several things,
but couldn't get any interesting effects, let alone a hang.)
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#69140
; Package
emacs
.
(Wed, 21 Feb 2024 17:21:02 GMT)
Full text and
rfc822 format available.
Message #23 received at 69140 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
On 2024-02-21 18:38, Eli Zaretskii wrote:
>> From: Aleksandr Vityazev <avityazev <at> disroot.org>
>> Cc: Eli Zaretskii <eliz <at> gnu.org>, 69140 <at> debbugs.gnu.org,
>> mail <at> daniel-mendler.de
>> Date: Wed, 21 Feb 2024 19:15:57 +0300
>>
>> 3. M-x test-dispatch
>> 4. Try playing with the parameters test1, test2, test3, test4. At the
>> same time you can put Emacs into full screen mode and back into windowed
>> mode, where it will occupy half of the screen. Initially, calling the
>> parameters test1, test2, test3, test4 in the transient window will be
>> delayed and everything can be canceled with C-g, after a few repetitions
>> Emacs hangs completely.
>
> Thanks, but I don't understand what to do after "m-x test-dispatch".
> Please tell in more details what you mean in Step 4, in terms of what
> I need to type after "M-x test-dispatch". (I tried several things,
> but couldn't get any interesting effects, let alone a hang.)
I run test-dispatch, for example I press "r", which calls the
minibuffer. At this point, Emacs is already starting to freeze for me; if
I change the full-screen to windowed mode several times, everything gets
worse. If nothing happens after pressing "r" you can try other bound
letters.
In fact, I can call commands through the tool-bar or menu-bar, but
everything that is displayed in the window or minibuffer does not
change. Was able to switch to the *Bactrace* buffer and save it via the
menu bar.
Bactrace is attached.
[*Backtrace* (text/plain, attachment)]
[Message part 3 (text/plain, inline)]
--
Best regards,
Aleksandr Vityazev
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#69140
; Package
emacs
.
(Wed, 21 Feb 2024 17:48:01 GMT)
Full text and
rfc822 format available.
Message #26 received at 69140 <at> debbugs.gnu.org (full text, mbox):
On 2024-02-21 20:20, Aleksandr Vityazev wrote:
> On 2024-02-21 18:38, Eli Zaretskii wrote:
>
>>> From: Aleksandr Vityazev <avityazev <at> disroot.org>
>>> Cc: Eli Zaretskii <eliz <at> gnu.org>, 69140 <at> debbugs.gnu.org,
>>> mail <at> daniel-mendler.de
>>> Date: Wed, 21 Feb 2024 19:15:57 +0300
>>>
>>> 3. M-x test-dispatch
>>> 4. Try playing with the parameters test1, test2, test3, test4. At the
>>> same time you can put Emacs into full screen mode and back into windowed
>>> mode, where it will occupy half of the screen. Initially, calling the
>>> parameters test1, test2, test3, test4 in the transient window will be
>>> delayed and everything can be canceled with C-g, after a few repetitions
>>> Emacs hangs completely.
>>
>> Thanks, but I don't understand what to do after "m-x test-dispatch".
>> Please tell in more details what you mean in Step 4, in terms of what
>> I need to type after "M-x test-dispatch". (I tried several things,
>> but couldn't get any interesting effects, let alone a hang.)
>
> I run test-dispatch, for example I press "r", which calls the
> minibuffer. At this point, Emacs is already starting to freeze for me; if
> I change the full-screen to windowed mode several times, everything gets
> worse. If nothing happens after pressing "r" you can try other bound
> letters.
You could also try enlarging the font
> In fact, I can call commands through the tool-bar or menu-bar, but
> everything that is displayed in the window or minibuffer does not
> change. Was able to switch to the *Bactrace* buffer and save it via the
> menu bar.
> Bactrace is attached.
--
Best regards,
Aleksandr Vityazev
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#69140
; Package
emacs
.
(Wed, 21 Feb 2024 19:26:01 GMT)
Full text and
rfc822 format available.
Message #29 received at 69140 <at> debbugs.gnu.org (full text, mbox):
> From: Aleksandr Vityazev <avityazev <at> disroot.org>
> Cc: luangruo <at> yahoo.com, 69140 <at> debbugs.gnu.org, mail <at> daniel-mendler.de
> Date: Wed, 21 Feb 2024 20:20:14 +0300
>
> > Thanks, but I don't understand what to do after "m-x test-dispatch".
> > Please tell in more details what you mean in Step 4, in terms of what
> > I need to type after "M-x test-dispatch". (I tried several things,
> > but couldn't get any interesting effects, let alone a hang.)
>
> I run test-dispatch, for example I press "r", which calls the
> minibuffer. At this point, Emacs is already starting to freeze for me; if
> I change the full-screen to windowed mode several times, everything gets
> worse. If nothing happens after pressing "r" you can try other bound
> letters.
I tried all the letters, and didn't see any hangs.
Maybe this only happens in a GTK build with Cairo.
You say "set a large font", but running your recipe I don't see any
large fonts, except in the help-echo tooltips. Maybe that's why I
cannot see any problems. Perhaps the problem is with the
set-face-attribute part of the recipe, in that it doesn't produce the
same effect on my system as on yours?
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#69140
; Package
emacs
.
(Wed, 21 Feb 2024 20:11:02 GMT)
Full text and
rfc822 format available.
Message #32 received at 69140 <at> debbugs.gnu.org (full text, mbox):
> From: Aleksandr Vityazev <avityazev <at> disroot.org>
> Cc: luangruo <at> yahoo.com, mail <at> daniel-mendler.de, 69140 <at> debbugs.gnu.org
> Date: Wed, 21 Feb 2024 20:47:22 +0300
>
> > I run test-dispatch, for example I press "r", which calls the
> > minibuffer. At this point, Emacs is already starting to freeze for me; if
> > I change the full-screen to windowed mode several times, everything gets
> > worse. If nothing happens after pressing "r" you can try other bound
> > letters.
>
> You could also try enlarging the font
What you "eval-buffer", is the Emacs frame visible in its entirety on
the screen, or are parts of it hidden because the font is too large?
I tried different fonts and different sizes, and as long as I can see
the frame on the screen, I don't see any hangs. Maybe this only
happens with pathologically large fonts, with which only a small part
of the frame can be seen, but if so, why is this situation
interesting?
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#69140
; Package
emacs
.
(Wed, 21 Feb 2024 20:23:02 GMT)
Full text and
rfc822 format available.
Message #35 received at 69140 <at> debbugs.gnu.org (full text, mbox):
On 2024-02-21 21:43, Eli Zaretskii wrote:
>> From: Aleksandr Vityazev <avityazev <at> disroot.org>
>> Cc: luangruo <at> yahoo.com, mail <at> daniel-mendler.de, 69140 <at> debbugs.gnu.org
>> Date: Wed, 21 Feb 2024 20:47:22 +0300
>>
>> > I run test-dispatch, for example I press "r", which calls the
>> > minibuffer. At this point, Emacs is already starting to freeze for me; if
>> > I change the full-screen to windowed mode several times, everything gets
>> > worse. If nothing happens after pressing "r" you can try other bound
>> > letters.
>>
>> You could also try enlarging the font
>
> What you "eval-buffer", is the Emacs frame visible in its entirety on
> the screen, or are parts of it hidden because the font is too large?
part of the mode-lane is hidden, but otherwise everything is visible
> I tried different fonts and different sizes, and as long as I can see
> the frame on the screen, I don't see any hangs. Maybe this only
> happens with pathologically large fonts, with which only a small part
> of the frame can be seen, but if so, why is this situation
> interesting?
>
with (set-face-attribute 'default nil :family "monospace" :height 440)
the result is the following:
--8<---------------cut here---------------start------------->8---
(list (window-height) (window-width)) => (13 53)
C-u C-x = (what-cursor-position) =>
display: by this font (glyph code):
ftcrhb:- -Go Mono-regular-normal-normal-*-58-*-*-*-m-0-iso10646-1 (#x37)
--8<---------------cut here---------------end--------------->8---
I think this is still a reasonable size. I usually have my font height
set to 240, and recently I noticed that vertico was starting to lag at
this setting. Researching further, I found that the larger the font, the
more obvious the hang, and I also found the commit after which it all
started. I think that there is a bug here, but we need to investigate it
further and check it without pgtk on X.
--
Best regards,
Aleksandr Vityazev
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#69140
; Package
emacs
.
(Thu, 22 Feb 2024 06:25:02 GMT)
Full text and
rfc822 format available.
Message #38 received at 69140 <at> debbugs.gnu.org (full text, mbox):
> From: Aleksandr Vityazev <avityazev <at> disroot.org>
> Cc: luangruo <at> yahoo.com, mail <at> daniel-mendler.de, 69140 <at> debbugs.gnu.org
> Date: Wed, 21 Feb 2024 23:22:27 +0300
>
> On 2024-02-21 21:43, Eli Zaretskii wrote:
>
> > What you "eval-buffer", is the Emacs frame visible in its entirety on
> > the screen, or are parts of it hidden because the font is too large?
>
> part of the mode-lane is hidden, but otherwise everything is visible
This situation works well here, it doesn't hang.
> > I tried different fonts and different sizes, and as long as I can see
> > the frame on the screen, I don't see any hangs. Maybe this only
> > happens with pathologically large fonts, with which only a small part
> > of the frame can be seen, but if so, why is this situation
> > interesting?
> >
>
> with (set-face-attribute 'default nil :family "monospace" :height 440)
> the result is the following:
>
> --8<---------------cut here---------------start------------->8---
> (list (window-height) (window-width)) => (13 53)
>
> C-u C-x = (what-cursor-position) =>
>
> display: by this font (glyph code):
> ftcrhb:- -Go Mono-regular-normal-normal-*-58-*-*-*-m-0-iso10646-1 (#x37)
> --8<---------------cut here---------------end--------------->8---
>
> I think this is still a reasonable size. I usually have my font height
> set to 240, and recently I noticed that vertico was starting to lag at
> this setting. Researching further, I found that the larger the font, the
> more obvious the hang, and I also found the commit after which it all
> started. I think that there is a bug here, but we need to investigate it
> further and check it without pgtk on X.
Could someone please reproduce and investigate? Po Lu, any
suggestions or ideas?
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#69140
; Package
emacs
.
(Thu, 22 Feb 2024 06:39:02 GMT)
Full text and
rfc822 format available.
Message #41 received at 69140 <at> debbugs.gnu.org (full text, mbox):
Eli Zaretskii <eliz <at> gnu.org> writes:
>> with (set-face-attribute 'default nil :family "monospace" :height 440)
>> the result is the following:
>>
>> --8<---------------cut here---------------start------------->8---
>> (list (window-height) (window-width)) => (13 53)
>>
>> C-u C-x = (what-cursor-position) =>
>>
>> display: by this font (glyph code):
>> ftcrhb:- -Go Mono-regular-normal-normal-*-58-*-*-*-m-0-iso10646-1 (#x37)
>> --8<---------------cut here---------------end--------------->8---
>>
>> I think this is still a reasonable size. I usually have my font height
>> set to 240, and recently I noticed that vertico was starting to lag at
>> this setting. Researching further, I found that the larger the font, the
>> more obvious the hang, and I also found the commit after which it all
>> started. I think that there is a bug here, but we need to investigate it
>> further and check it without pgtk on X.
>
> Could someone please reproduce and investigate? Po Lu, any
> suggestions or ideas?
Alexandr, please send me an archive containing the font files for "Go
Mono", and I'll try to reproduce.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#69140
; Package
emacs
.
(Thu, 22 Feb 2024 11:00:02 GMT)
Full text and
rfc822 format available.
Message #44 received at 69140 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
On 2024-02-22 14:37, Po Lu wrote:
> Eli Zaretskii <eliz <at> gnu.org> writes:
>
>>> with (set-face-attribute 'default nil :family "monospace" :height 440)
>>> the result is the following:
>>>
>>> --8<---------------cut here---------------start------------->8---
>>> (list (window-height) (window-width)) => (13 53)
>>>
>>> C-u C-x = (what-cursor-position) =>
>>>
>>> display: by this font (glyph code):
>>> ftcrhb:- -Go Mono-regular-normal-normal-*-58-*-*-*-m-0-iso10646-1 (#x37)
>>> --8<---------------cut here---------------end--------------->8---
>>>
>>> I think this is still a reasonable size. I usually have my font height
>>> set to 240, and recently I noticed that vertico was starting to lag at
>>> this setting. Researching further, I found that the larger the font, the
>>> more obvious the hang, and I also found the commit after which it all
>>> started. I think that there is a bug here, but we need to investigate it
>>> further and check it without pgtk on X.
>>
>> Could someone please reproduce and investigate? Po Lu, any
>> suggestions or ideas?
>
> Alexandr, please send me an archive containing the font files for "Go
> Mono", and I'll try to reproduce.
I also checked the following fonts: Iosevka, Liberation Mono, DejaVu
Sans Mono, the behavior is the same.
Go Mono fonts archive attached.
[Go-mono-fonts.tar.gz (application/octet-stream, attachment)]
[Message part 3 (text/plain, inline)]
--
Best regards,
Aleksandr Vityazev
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#69140
; Package
emacs
.
(Fri, 23 Feb 2024 02:21:02 GMT)
Full text and
rfc822 format available.
Message #47 received at 69140 <at> debbugs.gnu.org (full text, mbox):
Aleksandr Vityazev <avityazev <at> disroot.org> writes:
> On 2024-02-22 14:37, Po Lu wrote:
>
>> Eli Zaretskii <eliz <at> gnu.org> writes:
>>
>>>> with (set-face-attribute 'default nil :family "monospace" :height 440)
>>>> the result is the following:
>>>>
>>>> --8<---------------cut here---------------start------------->8---
>>>> (list (window-height) (window-width)) => (13 53)
>>>>
>>>> C-u C-x = (what-cursor-position) =>
>>>>
>>>> display: by this font (glyph code):
>>>> ftcrhb:- -Go Mono-regular-normal-normal-*-58-*-*-*-m-0-iso10646-1 (#x37)
>>>> --8<---------------cut here---------------end--------------->8---
>>>>
>>>> I think this is still a reasonable size. I usually have my font height
>>>> set to 240, and recently I noticed that vertico was starting to lag at
>>>> this setting. Researching further, I found that the larger the font, the
>>>> more obvious the hang, and I also found the commit after which it all
>>>> started. I think that there is a bug here, but we need to investigate it
>>>> further and check it without pgtk on X.
>>>
>>> Could someone please reproduce and investigate? Po Lu, any
>>> suggestions or ideas?
>>
>> Alexandr, please send me an archive containing the font files for "Go
>> Mono", and I'll try to reproduce.
>
> I also checked the following fonts: Iosevka, Liberation Mono, DejaVu
> Sans Mono, the behavior is the same.
>
> Go Mono fonts archive attached.
Should be fixed now, thanks.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#69140
; Package
emacs
.
(Fri, 23 Feb 2024 17:13:02 GMT)
Full text and
rfc822 format available.
Message #50 received at 69140 <at> debbugs.gnu.org (full text, mbox):
On 2024-02-23 10:19, Po Lu wrote:
> Aleksandr Vityazev <avityazev <at> disroot.org> writes:
>
>> On 2024-02-22 14:37, Po Lu wrote:
>>
>>> Eli Zaretskii <eliz <at> gnu.org> writes:
>>>
>>>>> with (set-face-attribute 'default nil :family "monospace" :height 440)
>>>>> the result is the following:
>>>>>
>>>>> --8<---------------cut here---------------start------------->8---
>>>>> (list (window-height) (window-width)) => (13 53)
>>>>>
>>>>> C-u C-x = (what-cursor-position) =>
>>>>>
>>>>> display: by this font (glyph code):
>>>>> ftcrhb:- -Go Mono-regular-normal-normal-*-58-*-*-*-m-0-iso10646-1 (#x37)
>>>>> --8<---------------cut here---------------end--------------->8---
>>>>>
>>>>> I think this is still a reasonable size. I usually have my font height
>>>>> set to 240, and recently I noticed that vertico was starting to lag at
>>>>> this setting. Researching further, I found that the larger the font, the
>>>>> more obvious the hang, and I also found the commit after which it all
>>>>> started. I think that there is a bug here, but we need to investigate it
>>>>> further and check it without pgtk on X.
>>>>
>>>> Could someone please reproduce and investigate? Po Lu, any
>>>> suggestions or ideas?
>>>
>>> Alexandr, please send me an archive containing the font files for "Go
>>> Mono", and I'll try to reproduce.
>>
>> I also checked the following fonts: Iosevka, Liberation Mono, DejaVu
>> Sans Mono, the behavior is the same.
>>
>> Go Mono fonts archive attached.
>
> Should be fixed now, thanks.
Thanks for the fix, I tested it and it works fine for me.
--
Best regards,
Aleksandr Vityazev
Reply sent
to
Eli Zaretskii <eliz <at> gnu.org>
:
You have taken responsibility.
(Fri, 23 Feb 2024 18:26:03 GMT)
Full text and
rfc822 format available.
Notification sent
to
Aleksandr Vityazev <avityazev <at> disroot.org>
:
bug acknowledged by developer.
(Fri, 23 Feb 2024 18:26:03 GMT)
Full text and
rfc822 format available.
Message #55 received at 69140-done <at> debbugs.gnu.org (full text, mbox):
> From: Aleksandr Vityazev <avityazev <at> disroot.org>
> Cc: mail <at> daniel-mendler.de, Eli Zaretskii <eliz <at> gnu.org>,
> 69140 <at> debbugs.gnu.org
> Date: Fri, 23 Feb 2024 20:12:12 +0300
>
> On 2024-02-23 10:19, Po Lu wrote:
>
> > Should be fixed now, thanks.
>
> Thanks for the fix, I tested it and it works fine for me.
Thanks for testing, I'm therefore closing this bug.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Sat, 23 Mar 2024 11:24:09 GMT)
Full text and
rfc822 format available.
This bug report was last modified 1 year and 90 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.