From: Mark Oteiza <mvoteiza@udel.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 24758-done@debbugs.gnu.org
Subject: bug#24758: 26.0.50; speedbar broken in -nw
Date: Mon, 24 Oct 2016 12:03:16 -0400 [thread overview]
Message-ID: <CAKyxw13O2ifP=j_qjSXc2x=0tNi_THCANRNNGbnjvGhKASXpsw@mail.gmail.com> (raw)
In-Reply-To: <83bmycr8yl.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1239 bytes --]
On Oct 22, 2016 6:10 AM, "Eli Zaretskii" <eliz@gnu.org> wrote:
>
> > Date: Sat, 22 Oct 2016 12:03:15 +0200
> > From: martin rudalics <rudalics@gmx.at>
> > CC: 24758@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.
[-- Attachment #2: Type: text/html, Size: 1778 bytes --]
prev parent reply other threads:[~2016-10-24 16:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 18:02 bug#24758: 26.0.50; speedbar broken in -nw Mark Oteiza
2016-10-21 18:43 ` Eli Zaretskii
2016-10-22 10:03 ` martin rudalics
2016-10-22 10:09 ` Eli Zaretskii
2016-10-24 16:03 ` Mark Oteiza [this message]
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='CAKyxw13O2ifP=j_qjSXc2x=0tNi_THCANRNNGbnjvGhKASXpsw@mail.gmail.com' \
--to=mvoteiza@udel.edu \
--cc=24758-done@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).