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: Thu, 05 Oct 2017 11:51:06 +0000 [thread overview]
Message-ID: <CAFyQvY14qDo86gj85+ZkKLmFM_7+ojjuHh_5==8SUFVPy0Po+Q@mail.gmail.com> (raw)
In-Reply-To: <59D5ED55.7020607@gmx.at>
[-- Attachment #1: Type: text/plain, Size: 1119 bytes --]
On Thu, Oct 5, 2017 at 4:29 AM martin rudalics <rudalics@gmx.at> wrote:
> > > [image: image.png]
> >
> > Unfortunately, I don't see any image here.
>
> Apologies, I see them now. But that's not what I meant. I need a
> screenshot showing the truncation glyphs in the _window on the right_.
> Your image shows them in the window on the left only. And better make
> it a frame with three side by side windows all showing truncation
> glyphs.
>
I have already sent those images.. the way debbugs is presenting them is
messing us up (You will find the images I attached then when to scroll to
the bottom of this message:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=27830#17 )
(1) Image of frame with 3 windows, scroll-bars OFF, truncation glyphs in
all windows:
https://debbugs.gnu.org/cgi/bugreport.cgi?att=2;msg=11;bug=27830;filename=image.png
(2) Image of frame with 3 windows, scroll-bars ON, truncation glyphs in all
windows:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=27830;filename=image.png;att=3;msg=11
The glyphs in the right-most window in both cases look the same/fine to me.
--
Kaushal Modi
[-- Attachment #2: Type: text/html, Size: 1879 bytes --]
next prev parent reply other threads:[~2017-10-05 11:51 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
2017-10-05 8:29 ` martin rudalics
2017-10-05 11:51 ` Kaushal Modi [this message]
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='CAFyQvY14qDo86gj85+ZkKLmFM_7+ojjuHh_5==8SUFVPy0Po+Q@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).