From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 18601@debbugs.gnu.org, vetoshev@gmail.com
Subject: bug#18601: 24.3.94; set-fringe-mode with left fringe 0 breaks window width calculations on Mac OS
Date: Fri, 03 Oct 2014 09:19:11 +0300 [thread overview]
Message-ID: <83k34hiskg.fsf@gnu.org> (raw)
In-Reply-To: <542DB77C.9090806@gmx.at>
> Date: Thu, 02 Oct 2014 22:37:16 +0200
> From: martin rudalics <rudalics@gmx.at>
> CC: 18601@debbugs.gnu.org
>
> > I think this is the result of 1 column being reserved for continuation
> > glyph on the left (required for R2L lines). This is a "feature".
> > Packages that are sensitive to the number of columns in a window
> > should now account for this even when only the left fringe is zero.
>
> Did you really change that in between 24.3.93 and 24.3.94?
Yes, in r117500. That was one part of fixing display of truncated R2L
lines in the many use cases you presented.
Btw, a simple way to avoid this side effect is to have a 1-pixel left
fringe, i.e. "pay" 1 pixel. That's not a high cost, IMO, if the
motivation for removing the left fringe is to have 1 more column
available for the same frame size.
next prev parent reply other threads:[~2014-10-03 6:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-02 8:38 bug#18601: 24.3.94; set-fringe-mode with left fringe 0 breaks window width calculations on Mac OS Constantine Vetoshev
2014-10-02 18:44 ` martin rudalics
2014-10-02 19:22 ` Constantine Vetoshev
2014-10-02 19:51 ` Eli Zaretskii
2014-10-02 20:37 ` martin rudalics
2014-10-03 6:19 ` Eli Zaretskii [this message]
2014-10-03 6:55 ` martin rudalics
2014-10-03 6:54 ` martin rudalics
2014-10-03 17:55 ` Constantine Vetoshev
2014-10-03 18:36 ` Eli Zaretskii
2014-10-03 20:53 ` Constantine Vetoshev
2014-10-04 7:08 ` Eli Zaretskii
2014-10-04 17:45 ` Constantine Vetoshev
2014-10-04 18:49 ` Eli Zaretskii
2014-10-04 20:48 ` Constantine Vetoshev
2014-10-06 6:49 ` martin rudalics
2014-10-06 15:10 ` Eli Zaretskii
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=83k34hiskg.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=18601@debbugs.gnu.org \
--cc=rudalics@gmx.at \
--cc=vetoshev@gmail.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).