From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 27830@debbugs.gnu.org, kaushal.modi@gmail.com, dgutov@yandex.ru
Subject: bug#27830: 26.0.50; Left fringe gets truncated by a pixel in window not sharing that edge with frame
Date: Fri, 06 Oct 2017 12:45:56 +0300 [thread overview]
Message-ID: <83shewvcbv.fsf@gnu.org> (raw)
In-Reply-To: <59D73C1F.5010500@gmx.at> (message from martin rudalics on Fri, 06 Oct 2017 10:17:35 +0200)
> Date: Fri, 06 Oct 2017 10:17:35 +0200
> From: martin rudalics <rudalics@gmx.at>
> CC: kaushal.modi@gmail.com, 27830@debbugs.gnu.org, dgutov@yandex.ru
>
> > It's definitely not for NEWS. As for PROBLEMS, can one of you suggest
> > the wording we'd like to put there? It's hard for me to make a
> > decision with no description of the workaround in sight.
>
> When vertical scroll bars are disabled on GUI frames, Emacs draws a
> one-pixel wide border between side-by-side windows. This border
> occupies the first pixel column of the window on the right and may thus
> overwrite the leftmost pixels of any glyph displayed there. If these
> pixels convey important information, you can make them visible by
> enabling window dividers (from the Options/Show/Hide menu). Width and
> faces of these dividers can be customized appropriately. Note, however,
> that window dividers are also displayed when scroll bars are enabled.
This is OK for PROBLEMS, but maybe it should be in the user manual
instead?
Thanks.
next prev parent reply other threads:[~2017-10-06 9:45 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-25 20:19 bug#27830: 26.0.50; Left fringe gets truncated by a pixel in window not sharing that edge with frame Kaushal Modi
2017-07-26 7:53 ` martin rudalics
2017-10-03 20:19 ` Kaushal Modi
2017-10-04 9:04 ` martin rudalics
2017-10-04 13:47 ` Kaushal Modi
2017-10-04 13:54 ` Kaushal Modi
2017-10-05 8:11 ` martin rudalics
2017-10-05 8:47 ` Eli Zaretskii
2017-10-05 11:59 ` Kaushal Modi
2017-10-06 8:17 ` martin rudalics
2017-10-06 9:45 ` Eli Zaretskii [this message]
2017-10-07 8:08 ` martin rudalics
2017-10-07 8:24 ` Eli Zaretskii
2017-10-07 9:44 ` martin rudalics
2017-10-07 9:51 ` Eli Zaretskii
2017-10-09 7:59 ` martin rudalics
2017-10-09 8:28 ` Eli Zaretskii
2017-10-09 12:21 ` martin rudalics
2017-10-09 12:53 ` Kaushal Modi
2017-10-10 8:12 ` martin rudalics
2017-10-09 13:41 ` Robert Pluim
2017-10-10 8:14 ` martin rudalics
2017-10-10 8:46 ` Robert Pluim
2017-10-11 8:33 ` martin rudalics
2020-09-04 5:25 ` Lars Ingebrigtsen
2017-10-05 8:10 ` martin rudalics
2017-10-05 8:29 ` martin rudalics
2017-10-05 11:51 ` Kaushal Modi
2017-10-06 8:18 ` martin rudalics
2017-10-05 11:46 ` Kaushal Modi
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=83shewvcbv.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=27830@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=kaushal.modi@gmail.com \
--cc=rudalics@gmx.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 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).