all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: triska@metalevel.at, 52929@debbugs.gnu.org
Subject: bug#52929: 27.1; Images are sometimes not fully displayed
Date: Sat, 01 Jan 2022 18:17:37 +0200	[thread overview]
Message-ID: <83ee5rfn1a.fsf@gnu.org> (raw)
In-Reply-To: <83f2f02c-9276-44e8-f15b-70cdf666dcd8@gmx.at> (message from martin rudalics on Sat, 1 Jan 2022 17:01:27 +0100)

> From: martin rudalics <rudalics@gmx.at>
> Date: Sat, 1 Jan 2022 17:01:27 +0100
> Cc: 52929@debbugs.gnu.org
> 
> When a window has no right fringe, Emacs by default usurps the rightmost
> character on each text line so it can indicate there whether that line
> is truncated or continued.  The maximum width of the special glyph to be
> displayed there (typically a "$" or a "\") is subtracted from the
> maximum width of the display area of that window.  So with the right
> fringe turned off, you as a rule always lose one column to the display
> engine even when displayed lines are never truncated or continued.
> 
> But Eli can explain it better.

I think you explained it very clearly, I have nothing to add, except
the obvious: the no-special-glyphs frame parameter, if its value is
non-nil, suppresses the display of the truncation and continuation
glyphs, and thus the column that the display engine needs for that is
free for other needs.





  reply	other threads:[~2022-01-01 16:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-01  9:00 bug#52929: 27.1; Images are sometimes not fully displayed Markus Triska
2022-01-01 10:06 ` martin rudalics
2022-01-01 10:11   ` Markus Triska
2022-01-01 16:01     ` martin rudalics
2022-01-01 16:17       ` Eli Zaretskii [this message]
2022-01-01 17:06         ` Markus Triska

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=83ee5rfn1a.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=52929@debbugs.gnu.org \
    --cc=rudalics@gmx.at \
    --cc=triska@metalevel.at \
    /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.