GNU bug report logs -
#24758
26.0.50; speedbar broken in -nw
Previous Next
Reported by: Mark Oteiza <mvoteiza <at> udel.edu>
Date: Fri, 21 Oct 2016 18:03:01 UTC
Severity: normal
Found in version 26.0.50
Done: Mark Oteiza <mvoteiza <at> udel.edu>
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 24758 in the body.
You can then email your comments to 24758 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#24758
; Package
emacs
.
(Fri, 21 Oct 2016 18:03:01 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Mark Oteiza <mvoteiza <at> udel.edu>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Fri, 21 Oct 2016 18:03:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
From -Q -nw, just do M-x speedbar. The message buffer is filled with:
tty-create-frame-with-faces: Can’t change the ‘minibuffer’ parameter of
this frameInval\
id face reference: font-lock-comment-delimiter-face
Invalid face reference: font-lock-comment-face
Invalid face reference: font-lock-comment-delimiter-face
Invalid face reference: font-lock-comment-face
Invalid face reference: mode-line-buffer-id
Invalid face reference: font-lock-comment-delimiter-face
Invalid face reference: font-lock-comment-face
Invalid face reference: font-lock-comment-delimiter-face
Invalid face reference: font-lock-comment-face
Invalid face reference: mode-line-buffer-id
<snip>
In GNU Emacs 26.0.50.2 (x86_64-unknown-linux-gnu, X toolkit, Xaw scroll bars)
of 2016-10-21 built on logos
Repository revision: 76b08a35bb6b3b32e5e5fda53e374769ceae6ed8
Configured using:
'configure --prefix=/usr --sysconfdir=/etc --libexecdir=/usr/lib
--localstatedir=/var --without-gconf --with-modules
--with-x-toolkit=lucid 'CFLAGS=-march=x86-64 -mtune=generic -O2 -pipe
-fstack-protector-strong --param=ssp-buffer-size=4 -g
-fvar-tracking-assignments -g -fvar-tracking-assignments'
CPPFLAGS=-D_FORTIFY_SOURCE=2
LDFLAGS=-Wl,-O1,--sort-common,--as-needed,-z,relro'
Configured features:
XPM JPEG TIFF GIF PNG RSVG IMAGEMAGICK SOUND GPM DBUS GSETTINGS NOTIFY
ACL GNUTLS LIBXML2 FREETYPE M17N_FLT LIBOTF XFT ZLIB TOOLKIT_SCROLL_BARS
LUCID X11 MODULES LIBSYSTEMD
Important settings:
value of $LC_COLLATE: C
value of $LANG: en_US.UTF-8
locale-coding-system: utf-8-unix
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#24758
; Package
emacs
.
(Fri, 21 Oct 2016 18:44:01 GMT)
Full text and
rfc822 format available.
Message #8 received at 24758 <at> debbugs.gnu.org (full text, mbox):
> From: Mark Oteiza <mvoteiza <at> udel.edu>
> Date: Fri, 21 Oct 2016 14:02:22 -0400
>
> >From -Q -nw, just do M-x speedbar. The message buffer is filled with:
>
> tty-create-frame-with-faces: Can’t change the ‘minibuffer’ parameter of
> this frameInval\
> id face reference: font-lock-comment-delimiter-face
> Invalid face reference: font-lock-comment-face
> Invalid face reference: font-lock-comment-delimiter-face
> Invalid face reference: font-lock-comment-face
> Invalid face reference: mode-line-buffer-id
> Invalid face reference: font-lock-comment-delimiter-face
> Invalid face reference: font-lock-comment-face
> Invalid face reference: font-lock-comment-delimiter-face
> Invalid face reference: font-lock-comment-face
> Invalid face reference: mode-line-buffer-id
> <snip>
Martin, can you take a look? I think the first error message above is
the key to the problem. It only happens on master.
Thanks.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#24758
; Package
emacs
.
(Sat, 22 Oct 2016 10:04:01 GMT)
Full text and
rfc822 format available.
Message #11 received at 24758 <at> debbugs.gnu.org (full text, mbox):
>> tty-create-frame-with-faces: Can’t change the ‘minibuffer’ parameter of
>> this frameInval\
>> id face reference: font-lock-comment-delimiter-face
>> Invalid face reference: font-lock-comment-face
>> Invalid face reference: font-lock-comment-delimiter-face
>> Invalid face reference: font-lock-comment-face
>> Invalid face reference: mode-line-buffer-id
>> Invalid face reference: font-lock-comment-delimiter-face
>> Invalid face reference: font-lock-comment-face
>> Invalid face reference: font-lock-comment-delimiter-face
>> Invalid face reference: font-lock-comment-face
>> Invalid face reference: mode-line-buffer-id
>> <snip>
>
> Martin, can you take a look? I think the first error message above is
> the key to the problem. It only happens on master.
Asking for a minibuffer-less frame on a TTY doesn't sound like a good
idea. Hopefully fixed now.
martin
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#24758
; Package
emacs
.
(Sat, 22 Oct 2016 10:10:02 GMT)
Full text and
rfc822 format available.
Message #14 received at 24758 <at> debbugs.gnu.org (full text, mbox):
> Date: Sat, 22 Oct 2016 12:03:15 +0200
> From: martin rudalics <rudalics <at> gmx.at>
> CC: 24758 <at> debbugs.gnu.org
>
> >> tty-create-frame-with-faces: Can’t change the ‘minibuffer’ parameter of
> >> this frameInval\
> >> id face reference: font-lock-comment-delimiter-face
> >> Invalid face reference: font-lock-comment-face
> >> Invalid face reference: font-lock-comment-delimiter-face
> >> Invalid face reference: font-lock-comment-face
> >> Invalid face reference: mode-line-buffer-id
> >> Invalid face reference: font-lock-comment-delimiter-face
> >> Invalid face reference: font-lock-comment-face
> >> Invalid face reference: font-lock-comment-delimiter-face
> >> Invalid face reference: font-lock-comment-face
> >> Invalid face reference: mode-line-buffer-id
> >> <snip>
> >
> > Martin, can you take a look? I think the first error message above is
> > the key to the problem. It only happens on master.
>
> Asking for a minibuffer-less frame on a TTY doesn't sound like a good
> idea. Hopefully fixed now.
It's certainly fixed for me here. Thanks.
Reply sent
to
Mark Oteiza <mvoteiza <at> udel.edu>
:
You have taken responsibility.
(Mon, 24 Oct 2016 16:04:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
Mark Oteiza <mvoteiza <at> udel.edu>
:
bug acknowledged by developer.
(Mon, 24 Oct 2016 16:04:02 GMT)
Full text and
rfc822 format available.
Message #19 received at 24758-done <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
On Oct 22, 2016 6:10 AM, "Eli Zaretskii" <eliz <at> gnu.org> wrote:
>
> > Date: Sat, 22 Oct 2016 12:03:15 +0200
> > From: martin rudalics <rudalics <at> gmx.at>
> > CC: 24758 <at> debbugs.gnu.org
> >
> > >> tty-create-frame-with-faces: Can’t change the ‘minibuffer’
parameter of
> > >> this frameInval\
> > >> id face reference: font-lock-comment-delimiter-face
> > >> Invalid face reference: font-lock-comment-face
> > >> Invalid face reference: font-lock-comment-delimiter-face
> > >> Invalid face reference: font-lock-comment-face
> > >> Invalid face reference: mode-line-buffer-id
> > >> Invalid face reference: font-lock-comment-delimiter-face
> > >> Invalid face reference: font-lock-comment-face
> > >> Invalid face reference: font-lock-comment-delimiter-face
> > >> Invalid face reference: font-lock-comment-face
> > >> Invalid face reference: mode-line-buffer-id
> > >> <snip>
> > >
> > > Martin, can you take a look? I think the first error message above
is
> > > the key to the problem. It only happens on master.
> >
> > Asking for a minibuffer-less frame on a TTY doesn't sound like a good
> > idea. Hopefully fixed now.
>
> It's certainly fixed for me here. Thanks.
Indeed, thanks.
[Message part 2 (text/html, inline)]
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Tue, 22 Nov 2016 12:24:03 GMT)
Full text and
rfc822 format available.
This bug report was last modified 8 years and 213 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.