all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@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: Tue, 31 Jan 2023 19:44:04 +0200	[thread overview]
Message-ID: <83wn521twb.fsf@gnu.org> (raw)
In-Reply-To: <877cx3xg24.fsf@secretsauce.net> (message from Dima Kogan on Tue,  31 Jan 2023 00:29:39 -0800)

> From: Dima Kogan <dima@secretsauce.net>
> Date: Tue, 31 Jan 2023 00:29:39 -0800
> 
> 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.

Looks like some subtle issue with font selection.  Can you bisect?
Initial investigation seems to indicate that this started happening
sometime in last August, but I could be mistaken, as what I see here
is not exactly what you see (I don't have that font installed).

In general, this is what happens in Emacs when some face fails to find
a suitable font for a GUI frame.  Then we fall back to the "glyphless"
display method.






  reply	other threads:[~2023-01-31 17:44 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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83wn521twb.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=61196@debbugs.gnu.org \
    --cc=dima@secretsauce.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.