GNU bug report logs -
#37007
Problem with the menu-bars in mode "org" and "auctex"
Previous Next
Reported by: Anders Rydvall <anders <at> rydvall.com>
Date: Sun, 11 Aug 2019 15:42:02 UTC
Severity: normal
Tags: moreinfo
Done: Lars Ingebrigtsen <larsi <at> gnus.org>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 37007 in the body.
You can then email your comments to 37007 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#37007
; Package
emacs
.
(Sun, 11 Aug 2019 15:42:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Anders Rydvall <anders <at> rydvall.com>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Sun, 11 Aug 2019 15:42:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
Working with a Dell LTS laptop with factory-installed Ubuntu 18.04 LTS
Emacs 26.2 installed with the Ubuntu graphic installer. Auxtex was
automatically installed according to package list. Emacs identifies the
.tex file and presents the adequate main menu items. But .. instead of
the alternatives coming down for "latex" and "command" it comes a black
bar. I thought this was a problem in auxtex but now I have installed
"org" and "org-journal" and the same problem comes up.
In org mode. the menu items "tbl" and "text" delivers black bars in the
same fashion as it was from auctex.
Therefore I presume a bug in Emacs GUI interface.
Regards
Anders Rydvall
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#37007
; Package
emacs
.
(Mon, 12 Aug 2019 09:01:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 37007 <at> debbugs.gnu.org (full text, mbox):
> Emacs 26.2 installed with the Ubuntu graphic installer. Auxtex was
> automatically installed according to package list. Emacs identifies
> the .tex file and presents the adequate main menu items. But
> .. instead of the alternatives coming down for "latex" and "command"
> it comes a black bar. I thought this was a problem in auxtex but now
> I have installed "org" and "org-journal" and the same problem comes
> up.
Does the problem also happen when you maximize the Emacs frame before
opening a .tex file?
martin
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#37007
; Package
emacs
.
(Wed, 14 Aug 2019 09:20:02 GMT)
Full text and
rfc822 format available.
Message #11 received at 37007 <at> debbugs.gnu.org (full text, mbox):
> In dired "operate, "Mark", "regexp", "immediate", "subdir" give the
> same black bar and absent submenus. The other submenus come down as
> expected.
The "Help" menu as well?
> GTK seems to be 3.22.30. Attached is a print-screen from synaptic package manager.
To make sure: What does clicking on About Emacs in the Help menu tell
about the version used for building Emacs?
> Thanks for engaging in the problem. Have you been able to reproduce it?
No. But I'm with GTK 3.22.11 which suffers from what is cited in
etc/PROBLEMS as
*** Emacs built with GTK+ toolkit can unexpectedly widen frames
Maybe GTK changed their behavior that instead of auto-widening the
window they now black out the menus. When you start Emacs from the
console or a text terminal do you see something like the
Gtk-CRITICAL **: gtk_distribute_natural_allocation: assertion 'extra_space >= 0' failed
mentioned in that entry?
Also, please keep <37007 <at> debbugs.gnu.org> in the list of recipients so
that others see your answers as well (using Reply To All in your MUA
should suffice).
Thanks, martin
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#37007
; Package
emacs
.
(Wed, 14 Aug 2019 14:43:02 GMT)
Full text and
rfc822 format available.
Message #14 received at 37007 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Martin!
The "Help" menu is OK in all modi.
GTK version is 3.22.30(about-emacs.png)
There is no message in the console when starting emacs from terminal and
no difference in behavior.
Today I noted very odd behavior. Suddenly i got all the menus in
org-mode(org-mode.png). When opening a .tex file there was opened most
of the menus but "command" is obviously inherited from
org-mode(latex1.png)! and "math"and "ref" were still absent(latex2.png).
I hope this will give a clue to the solution!
Den 2019-08-14 kl. 11:19, skrev martin rudalics:
> > In dired "operate, "Mark", "regexp", "immediate", "subdir" give the
> > same black bar and absent submenus. The other submenus come down as
> > expected.
>
> The "Help" menu as well?
>
> > GTK seems to be 3.22.30. Attached is a print-screen from synaptic
> package manager.
>
> To make sure: What does clicking on About Emacs in the Help menu tell
> about the version used for building Emacs?
>
> > Thanks for engaging in the problem. Have you been able to reproduce it?
>
> No. But I'm with GTK 3.22.11 which suffers from what is cited in
> etc/PROBLEMS as
>
> *** Emacs built with GTK+ toolkit can unexpectedly widen frames
>
> Maybe GTK changed their behavior that instead of auto-widening the
> window they now black out the menus. When you start Emacs from the
> console or a text terminal do you see something like the
>
> Gtk-CRITICAL **: gtk_distribute_natural_allocation: assertion
> 'extra_space >= 0' failed
>
> mentioned in that entry?
>
> Also, please keep <37007 <at> debbugs.gnu.org> in the list of recipients so
> that others see your answers as well (using Reply To All in your MUA
> should suffice).
>
> Thanks, martin
[about-emacs.png (image/png, attachment)]
[latex1.png (image/png, attachment)]
[latex2.png (image/png, attachment)]
[org-mode.png (image/png, attachment)]
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#37007
; Package
emacs
.
(Thu, 15 Aug 2019 08:13:02 GMT)
Full text and
rfc822 format available.
Message #17 received at 37007 <at> debbugs.gnu.org (full text, mbox):
> Today I noted very odd behavior. Suddenly i got all the menus in
> org-mode(org-mode.png).
Can you trigger both behaviors (the one with and the one without the
bug) using org-mode alone? So far we can rule out only that length or
number of menu bar entries matter much.
> When opening a .tex file there was opened most of the menus but
> "command" is obviously inherited from org-mode(latex1.png)! and
> "math"and "ref" were still absent(latex2.png). I hope this will give
> a clue to the solution!
Hardly. I don't have Auctex installed but I doubt that math and ref
would contain any special entries your toolkit can't display (in
particular without any warning). You could try to play with the font
or size of menu text if you find a knob to do that on your system.
martin
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#37007
; Package
emacs
.
(Fri, 16 Aug 2019 22:53:02 GMT)
Full text and
rfc822 format available.
Message #20 received at 37007 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Martin!
It seems to be by random(I am maybe not enough systematic). At one
occasion all menus came up correctly in latexmode((latexOK.png). Next
try came with obviously corrupted command-menu(latex_wrongCommand.png).
I get those by dragging the mouse from "tools" upwards and then down to
"preview". But not every time.
Today I cant get the correct menues for org-mode
directly(0rg1.org2,org3) but, at one occasion, skifting from latexmode
after I got the menus there the menues come also in org-mode though not
the correct "text"(org4.png).
I've also played somewhat with fonts but no result.
Downgrading Emacs?? In that case to what version? Is it in that case
necessary also to downgrade GTK??
Regards
Anders
Den 2019-08-15 kl. 10:12, skrev martin rudalics:
> > Today I noted very odd behavior. Suddenly i got all the menus in
> > org-mode(org-mode.png).
>
> Can you trigger both behaviors (the one with and the one without the
> bug) using org-mode alone? So far we can rule out only that length or
> number of menu bar entries matter much.
>
> > When opening a .tex file there was opened most of the menus but
> > "command" is obviously inherited from org-mode(latex1.png)! and
> > "math"and "ref" were still absent(latex2.png). I hope this will give
> > a clue to the solution!
>
> Hardly. I don't have Auctex installed but I doubt that math and ref
> would contain any special entries your toolkit can't display (in
> particular without any warning). You could try to play with the font
> or size of menu text if you find a knob to do that on your system.
>
> martin
[latexOK.png (image/png, attachment)]
[latex_wrongCommand.png (image/png, attachment)]
[org1.png (image/png, attachment)]
[org2.png (image/png, attachment)]
[org3.png (image/png, attachment)]
[org4.png (image/png, attachment)]
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#37007
; Package
emacs
.
(Sat, 17 Aug 2019 08:25:01 GMT)
Full text and
rfc822 format available.
Message #23 received at 37007 <at> debbugs.gnu.org (full text, mbox):
> It seems to be by random(I am maybe not enough systematic). At one
> occasion all menus came up correctly in
> latexmode((latexOK.png). Next try came with obviously corrupted
> command-menu(latex_wrongCommand.png). I get those by dragging the
> mouse from "tools" upwards and then down to "preview". But not every
> time.
I suppose you mean just "moving" the mouse, here we use "dragging" for
moving the mouse with one of its buttons pressed. Are "tools" and
"peview" submenus of the latex menu?
> Today I cant get the correct menues for org-mode
> directly(0rg1.org2,org3) but, at one occasion, skifting from
> latexmode after I got the menus there the menues come also in
> org-mode though not the correct "text"(org4.png).
Are all wrong entries somewhat related to latex? From the text above
it sounds so. But since you earlier said that 'dired' had similar
problems ...
I would try to isolate the problematic modes first, if there are any.
For example, if you start Emacs with -Q and invoke 'dired', can you
produce the problem?
> Downgrading Emacs?? In that case to what version? Is it in that case
> necessary also to downgrade GTK??
It depends. If the problem is in the GTK version, it might help to
downgrade GTK only (not really advisable if other applications depend
on a GTK library). In either case, downgrading anything should be the
last option to try.
martin
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#37007
; Package
emacs
.
(Mon, 19 Aug 2019 14:54:01 GMT)
Full text and
rfc822 format available.
Message #26 received at 37007 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Martin!
Yes, I meant "dragging" the mouse.
Wrong entries are not only associated with latex mode. Here example on
calender:holiday going into org-mode(cal_hol.png; org_hol.png).
Corruption of menu from other mode.
When starting emacs -Q I cant see any different behavior. Invoking dired
with C-x d or M-x dired give the same result - incomplete menues as
shown in dired1. However "dragging" the mouse opens the menues shown in
dired2.
Den 2019-08-17 kl. 10:24, skrev martin rudalics:
> > It seems to be by random(I am maybe not enough systematic). At one
> > occasion all menus came up correctly in
> > latexmode((latexOK.png). Next try came with obviously corrupted
> > command-menu(latex_wrongCommand.png). I get those by dragging the
> > mouse from "tools" upwards and then down to "preview". But not every
> > time.
>
> I suppose you mean just "moving" the mouse, here we use "dragging" for
> moving the mouse with one of its buttons pressed. Are "tools" and
> "peview" submenus of the latex menu?
>
> > Today I cant get the correct menues for org-mode
> > directly(0rg1.org2,org3) but, at one occasion, skifting from
> > latexmode after I got the menus there the menues come also in
> > org-mode though not the correct "text"(org4.png).
>
> Are all wrong entries somewhat related to latex? From the text above
> it sounds so. But since you earlier said that 'dired' had similar
> problems ...
>
> I would try to isolate the problematic modes first, if there are any.
> For example, if you start Emacs with -Q and invoke 'dired', can you
> produce the problem?
>
> > Downgrading Emacs?? In that case to what version? Is it in that case
> > necessary also to downgrade GTK??
>
> It depends. If the problem is in the GTK version, it might help to
> downgrade GTK only (not really advisable if other applications depend
> on a GTK library). In either case, downgrading anything should be the
> last option to try.
>
> martin
[cal_hol.png (image/png, attachment)]
[dired1.png (image/png, attachment)]
[dired2.png (image/png, attachment)]
[org_hol.png (image/png, attachment)]
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#37007
; Package
emacs
.
(Wed, 21 Aug 2019 07:38:02 GMT)
Full text and
rfc822 format available.
Message #29 received at 37007 <at> debbugs.gnu.org (full text, mbox):
> Yes, I meant "dragging" the mouse.
Why on earth would you "drag" the mouse in order to pick a menu entry?
I'm not aware of any menu entries that change their semantics when
dragging an object on them. What happens when you hit <f10> and use the
keyboard to select a menu item?
> When starting emacs -Q I cant see any different behavior. Invoking
> dired with C-x d or M-x dired give the same result - incomplete
> menues as shown in dired1. However "dragging" the mouse opens the
> menues shown in dired2.
Maybe you should indeed try to downgrade Emacs to see if the problem
is related to the current version. Provided you can do that ...
martin
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#37007
; Package
emacs
.
(Wed, 21 Aug 2019 11:09:01 GMT)
Full text and
rfc822 format available.
Message #32 received at 37007 <at> debbugs.gnu.org (full text, mbox):
Martin!
Dragging the mouse was one, of different, ways to test. Of course I
normally don't drag the mouse.
Hitting F10 invokes the correct and complete menus in the different
modes. Moreover a new mode does not any longer seem to inherit menus
from the previous used buffer. When shifting between buffers it is
necessary to hit F10 again to get complete menus.
The F10 command seems to correctly load the menus which does not happen
only by shifting into a certain buffer. Thus there must be some problem
with the invocation of the menus. However I'm, for the moment, more
happy. I can use Emacs. Hopefully the problem will be solved in a future
version.
Regards
Anders
Den 2019-08-21 kl. 09:37, skrev martin rudalics:
> > Yes, I meant "dragging" the mouse.
>
> Why on earth would you "drag" the mouse in order to pick a menu entry?
> I'm not aware of any menu entries that change their semantics when
> dragging an object on them. What happens when you hit <f10> and use the
> keyboard to select a menu item?
>
> > When starting emacs -Q I cant see any different behavior. Invoking
> > dired with C-x d or M-x dired give the same result - incomplete
> > menues as shown in dired1. However "dragging" the mouse opens the
> > menues shown in dired2.
>
> Maybe you should indeed try to downgrade Emacs to see if the problem
> is related to the current version. Provided you can do that ...
>
> martin
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#37007
; Package
emacs
.
(Thu, 22 Aug 2019 08:08:01 GMT)
Full text and
rfc822 format available.
Message #35 received at 37007 <at> debbugs.gnu.org (full text, mbox):
> Dragging the mouse was one, of different, ways to test. Of course I
> normally don't drag the mouse.
OK. Just that here, when dragging the mouse, no menu pops up since
Emacs handles the mouse tracking itself and ignores the menu bar
during that.
> Hitting F10 invokes the correct and complete menus in the different
> modes. Moreover a new mode does not any longer seem to inherit menus
> from the previous used buffer. When shifting between buffers it is
> necessary to hit F10 again to get complete menus.
So we have two different issues: One is that the items shown on the
menu bar do not correspond to the items one should see wrt the
selected window's buffer. The other is that popping up a specific
menu shows blacked-out entries. I wonder whether the second issue is
a consequence of the former. If so, some error should have been
reported. Are you sure nothing the like shows up in *Messages*?
> The F10 command seems to correctly load the menus which does not
> happen only by shifting into a certain buffer. Thus there must be
> some problem with the invocation of the menus.
What could F10 possibly do the mouse doesn't? I'm lost.
martin
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#37007
; Package
emacs
.
(Thu, 22 Aug 2019 12:01:02 GMT)
Full text and
rfc822 format available.
Message #38 received at 37007 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Martin!
"messages" doesn't capture anything related to the menus as far as I can
see. Attached screenshot is after shifting between buffers several times
and invoking menus with F10. And different buffers have opened with
corrupted menu items and the black bars which at every occasion is
corrected with F10. Apparently F10 does something different to the menus
than the mouse.
regards
Anders
Den 2019-08-22 kl. 10:07, skrev martin rudalics:
> > Dragging the mouse was one, of different, ways to test. Of course I
> > normally don't drag the mouse.
>
> OK. Just that here, when dragging the mouse, no menu pops up since
> Emacs handles the mouse tracking itself and ignores the menu bar
> during that.
>
> > Hitting F10 invokes the correct and complete menus in the different
> > modes. Moreover a new mode does not any longer seem to inherit menus
> > from the previous used buffer. When shifting between buffers it is
> > necessary to hit F10 again to get complete menus.
>
> So we have two different issues: One is that the items shown on the
> menu bar do not correspond to the items one should see wrt the
> selected window's buffer. The other is that popping up a specific
> menu shows blacked-out entries. I wonder whether the second issue is
> a consequence of the former. If so, some error should have been
> reported. Are you sure nothing the like shows up in *Messages*?
>
> > The F10 command seems to correctly load the menus which does not
> > happen only by shifting into a certain buffer. Thus there must be
> > some problem with the invocation of the menus.
>
> What could F10 possibly do the mouse doesn't? I'm lost.
>
> martin
[messages190822.png (image/png, attachment)]
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#37007
; Package
emacs
.
(Fri, 23 Aug 2019 07:47:01 GMT)
Full text and
rfc822 format available.
Message #41 received at 37007 <at> debbugs.gnu.org (full text, mbox):
> "messages" doesn't capture anything related to the menus as far as I
> can see. Attached screenshot is after shifting between buffers
> several times and invoking menus with F10. And different buffers
> have opened with corrupted menu items and the black bars which at
> every occasion is corrected with F10. Apparently F10 does something
> different to the menus than the mouse.
It should mean that we do not update the menu bar at some decisive
moments. Try evaluating the following noisy form with emacs -Q.
(add-hook 'menu-bar-update-hook (lambda () (ding) (message "%s..%s" (current-buffer) major-mode)))
Here I hear a "ding" and see a message whenever I split a window or
show another buffer in some window. And I hear the ding when hitting
F10 or clicking on a menu bar item with the mouse. Do you see any
"anomalies" when doing that? I mean, does the message intuitively
show the "right" current buffer and its major mode when you randomly
execute some of the actions above?
Sorry, I have no better idea than applying such silly heuristics.
Thanks, martin
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#37007
; Package
emacs
.
(Sat, 30 Apr 2022 17:00:02 GMT)
Full text and
rfc822 format available.
Message #44 received at 37007 <at> debbugs.gnu.org (full text, mbox):
Anders Rydvall <anders <at> rydvall.com> writes:
> Emacs 26.2 installed with the Ubuntu graphic installer. Auxtex was
> automatically installed according to package list. Emacs identifies
> the .tex file and presents the adequate main menu items. But
> .. instead of the alternatives coming down for "latex" and "command"
> it comes a black bar. I thought this was a problem in auxtex but now I
> have installed "org" and "org-journal" and the same problem comes up.
>
> In org mode. the menu items "tbl" and "text" delivers black bars in
> the same fashion as it was from auctex.
(I'm going through old bug reports that unfortunately weren't resolved
at the time.)
Do you see this issue in newer Emacs versions?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
Added tag(s) moreinfo.
Request was from
Lars Ingebrigtsen <larsi <at> gnus.org>
to
control <at> debbugs.gnu.org
.
(Sat, 30 Apr 2022 17:00:03 GMT)
Full text and
rfc822 format available.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#37007
; Package
emacs
.
(Sun, 29 May 2022 13:20:01 GMT)
Full text and
rfc822 format available.
Message #49 received at 37007 <at> debbugs.gnu.org (full text, mbox):
Lars Ingebrigtsen <larsi <at> gnus.org> writes:
> Do you see this issue in newer Emacs versions?
More information was requested, but no response was given within a
month, so I'm closing this bug report. If the problem still exists,
please respond to this email and we'll reopen the bug report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
bug closed, send any further explanations to
37007 <at> debbugs.gnu.org and Anders Rydvall <anders <at> rydvall.com>
Request was from
Lars Ingebrigtsen <larsi <at> gnus.org>
to
control <at> debbugs.gnu.org
.
(Sun, 29 May 2022 13:20:03 GMT)
Full text and
rfc822 format available.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Mon, 27 Jun 2022 11:24:05 GMT)
Full text and
rfc822 format available.
This bug report was last modified 1 year and 296 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.