unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: goncholden <goncholden@protonmail.com>
Cc: larsi@gnus.org, stephen.berman@gmx.net, 53866@debbugs.gnu.org
Subject: bug#53866: face-attribute giving bold for ultra-bold attribute
Date: Tue, 08 Feb 2022 21:38:43 +0200	[thread overview]
Message-ID: <8335ktw3lo.fsf@gnu.org> (raw)
In-Reply-To: <CqXIPTZM4IJfwQFNY8dCeFQ_4guPLXobsCi479jOFNJzlnJxkB9XrTodwBxz175FMIq9tHsxx779ZVZSk_rWX9IHRzCGiIgPVMT7_y7sKqc=@protonmail.com> (bug-gnu-emacs@gnu.org)

> Cc: larsi@gnus.org, 53866@debbugs.gnu.org
> Date: Tue, 08 Feb 2022 17:00:38 +0000
> From:  goncholden via "Bug reports for GNU Emacs,
>  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
> 
> It is very confusing.  I loaded a random elisp file and run the command in the middle of the buffer
> to get
> 
> ---------
> 
> Type C-x 1 to delete the help window, C-M-v to scroll help.
> Char: C-j (10, #o12, #xa) point=11866 of 22678 (52%) column=0
> End of buffer
> 
>              position: 11866 of 22678 (52%), column: 0
>             character: C-j (displayed as C-j) (codepoint 10, #o12, #xa)
>               charset: ascii (ASCII (ISO646 IRV))
> code point in charset: 0x0A
>                script: latin
>                syntax: > 	which means: endcomment
>              to input: type "C-x 8 RET a" or "C-x 8 RET LINE FEED (LF)"
>           buffer code: #x0A
>             file code: #x0A (encoded by coding system prefer-utf-8-unix)
>               display: no font available

Put the cursor on a character that has a visible glyph.  You have put
it on a newline, which leaves no trace on display, so you get "no
font" for that.





  reply	other threads:[~2022-02-08 19:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-08  3:23 bug#53866: face-attribute giving bold for ultra-bold attribute goncholden via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-08  5:54 ` Lars Ingebrigtsen
2022-02-08  6:30   ` goncholden via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-08  6:42     ` Lars Ingebrigtsen
2022-02-08  6:56       ` goncholden via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-08  8:26         ` Stephen Berman
2022-02-08 17:00           ` goncholden via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-08 19:38             ` Eli Zaretskii [this message]
2022-02-08 22:34               ` goncholden via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-09  3:30                 ` Eli Zaretskii
2022-02-09  3:44                   ` goncholden via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-09  7:56         ` Lars Ingebrigtsen

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=8335ktw3lo.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=53866@debbugs.gnu.org \
    --cc=goncholden@protonmail.com \
    --cc=larsi@gnus.org \
    --cc=stephen.berman@gmx.net \
    /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).