From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Dima Kogan <dima@secretsauce.net>
Cc: 61196@debbugs.gnu.org
Subject: bug#61196: 30.0.50; X11 rendering of horizontal line in log-edit mode fails with some fonts
Date: Wed, 01 Feb 2023 09:29:08 +0800 [thread overview]
Message-ID: <87ilgmxjff.fsf@yahoo.com> (raw)
In-Reply-To: <877cx3xg24.fsf@secretsauce.net> (Dima Kogan's message of "Tue, 31 Jan 2023 00:29:39 -0800")
Dima Kogan <dima@secretsauce.net> writes:
> Hi. I'm using a bleeding-edge build of emacs from git, but this
> particular issue I've been seeing for maybe 6 months now, or maybe even
> a year.
>
> I'm using a GTK build of Emacs running on X11 on GNU/Linux. Some of that
> is significant.
>
> I can tickle the bug by selecting a particular font, entering
> log-edit-mode, and entering some text:
>
> rm /tmp/xxx;
>
> emacs -Q -geometry 40x8 \
> --eval "(progn (setf (alist-get 'font default-frame-alist) \"-adobe-courier-medium-r-*-*-12-*-*-*-*-*-iso8859-*\")
> (require 'log-edit)
> (find-file \"/tmp/xxx\")
> (log-edit-mode)
> (insert \"a:b\\n\\nc d\"))"
>
> The result looks like the attached 12.png. Note the unrendered 000A
> character block. This is a bug. It should be rendering a horizontal line
> instead. And if I select a different font, it does work. I can do that
> by changing the "-12-" in the above command to "-22-". The result is
> attached in 22.png.
>
> I see it in the wild all the time when making version control commits in
> emacs, and typing the commit message.
>
> Thanks
When I last investigated this problem (I use the X core font backend all
the time), it was that X fonts typically have no glyph for the newline
character, which Emacs seems to expect.
next prev parent reply other threads:[~2023-02-01 1:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 8:29 bug#61196: 30.0.50; X11 rendering of horizontal line in log-edit mode fails with some fonts Dima Kogan
2023-01-31 17:44 ` Eli Zaretskii
2023-01-31 18:52 ` Dima Kogan
2023-02-01 1:29 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-02-01 3:37 ` Eli Zaretskii
2023-02-01 3:42 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-01 12:19 ` Eli Zaretskii
2023-02-01 10:44 ` Gregory Heytings
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=87ilgmxjff.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=61196@debbugs.gnu.org \
--cc=dima@secretsauce.net \
--cc=luangruo@yahoo.com \
/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).