Description:
GNU Emacs bug reports and suggested fixes.
|
|
|
Processed: Re: bug#4884: 23.1; I can not open some menu
|
| |
Processing commands for cont...@emacsbugs.donarmstrong .com: ...bug#4122: 23.1; GTK menu contents don't change bug#4884: 23.1; I can not open some menu bug#4125: 23.1; GTK menu contents don't change bug#4134: 23.1; Problems with gtk+ >= 2.7.19 bug#4843: creating menus bug#4866: Buffer list in Buffers menu is not updated on the fly... more »
|
|
bug#4653: marked as done (23.1.50; ordering of bookmark-jump menu)
|
| |
Your message dated Sun, 08 Nov 2009 18:02:30 -0500 with message-id <87iqdkk4c9....@stupidchicken. com> and subject line Re: bug#4653: 23.1.50; ordering of bookmark-jump menu has caused the Emacs bug report #4653, regarding 23.1.50; ordering of bookmark-jump menu to be marked as done. This means that you claim that the problem has been dealt with.... more »
|
|
bug#4818: marked as done (23.1; checkdoc noun at end of sentence)
|
| |
Your message dated Mon, 09 Nov 2009 09:02:34 +1100 with message-id <873a4osmit....@blah.blah> and subject line Re: 23.1; checkdoc noun at end of sentence has caused the Emacs bug report #4818, regarding 23.1; checkdoc noun at end of sentence to be marked as done. This means that you claim that the problem has been dealt with.... more »
|
|
bug#4887: 23.1; list-load-path-shadows produces broken buffer
|
| |
Please describe exactly what actions triggered the bug and the precise symptoms of the bug: * turn on global-linum-mode * run list-load-path-shadows * observe that the resulting buffer, *Shadows*, has no line numbering, even if you change into that buffer, move around, and change text. [BUG] Some debugging shows that:... more »
|
|
Processed: close 4879
|
| |
Processing commands for cont...@emacsbugs.donarmstrong .com: ...bug#4879: Crash in xmenu_show 'close' is deprecated; see [link]. bug closed, send any further explanations to Juri Linkov <j...@jurta.org> ...Stopping processing here. Please contact me if you need assistance.... more »
|
|
bug#4888: 23.1.50; emacsclient vs. daemon
|
| |
Hi, I found some issues while playing around emacs --daemon. Here are the first ones. 1. In (info "(emacs) emacsclient Options") I see: 'As a special exception, if COMMAND is the empty string, then `emacsclient' starts Emacs in daemon mode and then tries connecting again.' This is not really true: as -a has a mandatory, non-empty COMMAND,... more »
|
|
|