From: Eli Zaretskii <eliz@gnu.org>
To: rgm@gnu.org
Cc: eggert@cs.ucla.edu, 22207@debbugs.gnu.org
Subject: bug#22207: emacs-25 mishandles info code text on Fedora 23
Date: Sat, 19 Dec 2015 21:25:30 +0200 [thread overview]
Message-ID: <831taiutp1.fsf@gnu.org> (raw)
In-Reply-To: <8337uyutvn.fsf@gnu.org> (message from Eli Zaretskii on Sat, 19 Dec 2015 21:21:32 +0200)
> Date: Sat, 19 Dec 2015 21:21:32 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: eggert@cs.ucla.edu, 22207@debbugs.gnu.org
>
> > From: Glenn Morris <rgm@gnu.org>
> > Cc: eggert@cs.ucla.edu, 22207@debbugs.gnu.org
> > Date: Sat, 19 Dec 2015 14:16:19 -0500
> >
> > Actually I see Emacs has a font called fixed-width that does exactly that.
Do you mean the fixed-pitch _face_? I don't think I see the
fixed-width font.
> > So my simple suggestion for fixing this issue:
> >
> > Info-quoted and tex-verbatim face should inherit from fixed-width by default.
Here you mean a face, not a font, and again I don't see any face named
fixed-width. What am I missing?
next prev parent reply other threads:[~2015-12-19 19:25 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-18 18:25 bug#22207: emacs-25 mishandles info code text on Fedora 23 Paul Eggert
2015-12-18 18:57 ` Glenn Morris
2015-12-18 19:40 ` Eli Zaretskii
2015-12-18 19:49 ` Glenn Morris
2015-12-18 20:32 ` Eli Zaretskii
2015-12-19 14:21 ` Wolfgang Jenkner
2015-12-19 14:42 ` Eli Zaretskii
2015-12-19 15:28 ` Wolfgang Jenkner
2015-12-19 16:07 ` Wolfgang Jenkner
2015-12-19 16:57 ` Eli Zaretskii
2015-12-19 19:16 ` Glenn Morris
2015-12-19 19:21 ` Eli Zaretskii
2015-12-19 19:25 ` Eli Zaretskii [this message]
2015-12-19 19:31 ` Glenn Morris
2015-12-19 19:51 ` Eli Zaretskii
2015-12-20 3:40 ` Glenn Morris
2015-12-20 15:44 ` Eli Zaretskii
2015-12-20 21:14 ` Paul Eggert
2015-12-21 16:18 ` Eli Zaretskii
2016-02-13 1:29 ` Paul Eggert
2016-02-13 8:53 ` Eli Zaretskii
2016-02-13 18:33 ` Paul Eggert
2016-05-05 20:48 ` Paul Eggert
2016-05-05 21:29 ` Glenn Morris
2016-05-05 22:54 ` bug#19889: " Paul Eggert
2016-05-06 6:49 ` Eli Zaretskii
2016-05-06 15:47 ` Glenn Morris
2016-05-06 15:58 ` Eli Zaretskii
2016-05-06 16:24 ` Paul Eggert
2016-05-06 17:15 ` Eli Zaretskii
2016-05-06 15:59 ` Paul Eggert
2016-05-06 17:18 ` Eli Zaretskii
2016-05-06 18:24 ` Paul Eggert
2016-05-06 19:01 ` Eli Zaretskii
2016-05-07 3:03 ` Paul Eggert
2016-05-07 7:01 ` Eli Zaretskii
2016-05-07 17:05 ` Paul Eggert
2016-05-07 17:27 ` Eli Zaretskii
2016-05-07 20:37 ` Paul Eggert
2016-05-13 21:33 ` Paul Eggert
2016-05-14 7:48 ` Eli Zaretskii
2016-05-14 8:24 ` Paul Eggert
2016-05-14 9:28 ` Eli Zaretskii
2016-05-06 19:32 ` Stefan Monnier
2016-05-07 6:50 ` Eli Zaretskii
2016-05-06 20:08 ` bug#19889: Glenn Morris
2016-05-06 20:22 ` bug#19889: Glenn Morris
2016-05-07 6:53 ` bug#19889: Eli Zaretskii
2016-05-07 16:56 ` bug#19889: bug#22207: emacs-25 mishandles info code text on Fedora 23 Paul Eggert
2016-05-06 6:37 ` Eli Zaretskii
2016-05-06 16:02 ` bug#19889: tex-verbatim face: don't specify :family? Glenn Morris
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=831taiutp1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=22207@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=rgm@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).