unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Kaushal Modi <kaushal.modi@gmail.com>
To: martin rudalics <rudalics@gmx.at>, 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: Wed, 04 Oct 2017 13:47:13 +0000	[thread overview]
Message-ID: <CAFyQvY28L9jvytrcg7a-RiDtwOc5GPrrvF986t58wrWVAv0SrQ@mail.gmail.com> (raw)
In-Reply-To: <59D4A41F.7080603@gmx.at>


[-- Attachment #1.1: Type: text/plain, Size: 2290 bytes --]

On Wed, Oct 4, 2017 at 5:04 AM martin rudalics <rudalics@gmx.at> wrote:

>
> I see that the continuation arrows in the rightmost fringe have their
> tips truncated.  Do you really need diff-hl-mode enabled to see that?
>

Can you try again with a buffer with wide enough lines to see the
> continuation arrows in the window on the right?  This is important
> because it would constitute another, probably different bug.
>

Hi Martin,

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]


>  I see: The first pixel of each fringe in a window that has another one
> on the left gets overwritten by the "vertical window border".  With
> window dividers or scroll bars on, that border is not drawn.  I think we
> should remove that border completely and draw a one pixel wide window
> divider instead when scroll bars are disabled in a window and dividers
> are off.  Tricky because scroll bars can be turned off individually for
> windows and dividers are frame wide.  Strictly for Emacs 27.
>

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?

As a workaround for things to come I suggest using a one pixel wide
> right only window divider with scroll bars off.
>

The workaround doesn't behave the same because now the windows have a white
line show up for the window dividers:

[image: image.png]

The "vertical window border" looks very much elegant IMO (with the window
dividers disabled, but that then truncates the fringe):

[image: image.png]

It this workaround is needed, then:
1) Would it be possible to customize the divider color?
2) It should also go in NEWS and /etc/PROBLEMS

The best case of course is if this can be fixed before 26.1 release.


> Both dumps are completely normal.
>

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

Thanks!
-- 

Kaushal Modi

[-- Attachment #1.2: Type: text/html, Size: 3820 bytes --]

[-- Attachment #2: image.png --]
[-- Type: image/png, Size: 203384 bytes --]

[-- Attachment #3: image.png --]
[-- Type: image/png, Size: 34079 bytes --]

[-- Attachment #4: image.png --]
[-- Type: image/png, Size: 33431 bytes --]

  reply	other threads:[~2017-10-04 13:47 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 [this message]
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
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=CAFyQvY28L9jvytrcg7a-RiDtwOc5GPrrvF986t58wrWVAv0SrQ@mail.gmail.com \
    --to=kaushal.modi@gmail.com \
    --cc=27830@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    --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).