unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Kaushal Modi <kaushal.modi@gmail.com>, 27830@debbugs.gnu.org
Cc: Dmitry Gutov <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: Thu, 05 Oct 2017 10:10:55 +0200	[thread overview]
Message-ID: <59D5E90F.70203@gmx.at> (raw)
In-Reply-To: <CAFyQvY28L9jvytrcg7a-RiDtwOc5GPrrvF986t58wrWVAv0SrQ@mail.gmail.com>

 > The screenshots attached in my previous email show the truncation arrows
 > with/without scrollbars.. they look the same in both cases to me (see
 > below, without scrollbars on left, and with, on right):
 >
 > I am using diff-hl-mode because the truncation is very evident as you see
 > in that same image.
 >
 > [image: image.png]

Unfortunately, I don't see any image here.

 > Oh no, can this be please fixed in emacs 26.1? I am pretty sure that people
 > using emacs without scroll bars and without window dividers are not in
 > minority. This artifact will be pretty evident to people using fringe
 > elements like in diff-hl-mode.
 >
 > @Eli: Can this be a blocker for 26.1?

This behavior has been with us ever since the vertical border has been
used for GUI frames so it hardly qualifies as a blocker for the release.

 > Should the dumps be updated with more info to help catch this?

No, thanks.

martin





  parent reply	other threads:[~2017-10-05  8:10 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
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 [this message]
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=59D5E90F.70203@gmx.at \
    --to=rudalics@gmx.at \
    --cc=27830@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    --cc=kaushal.modi@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).