From: martin rudalics <rudalics@gmx.at>
To: Robert Pluim <rpluim@gmail.com>
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: Tue, 10 Oct 2017 10:14:37 +0200 [thread overview]
Message-ID: <59DC816D.40707@gmx.at> (raw)
In-Reply-To: <87vajojv53.fsf@gmail.com>
>>>> But perhaps we should simply stop showing vertical borders on
>>>> graphical frames.
>>>
>>> Aren't they needed for resizing windows with a mouse?
>>
>> The majority of users probably has vertical scroll bars turned on, so
>> they can't do that anyway.
>
> I'm confused: If I have a vertical scoll bar, there's a small vertical
> bar just below the bottom of it that allows resizing the emacs window,
> so why do scroll bars preclude resizing?
The thing I would like to get rid of are the vertical borders. You can
make them more prominently visible by evaluating
(custom-set-faces
'(vertical-border ((t (:foreground "red")))))
(scroll-bar-mode -1)
with emacs -Q and typing C-x 3. You can resize your windows now by
dragging that red vertical line.
Notice that the "small vertical bar" you mention did not change color.
In fact, that bar does not exist at all. You can make it "disappear" by
resetting the face properties of ‘mode-line’ and ‘mode-line-inactive’ to
the default face. It's an artefact that allows resizing windows even in
the presence of scroll bars. It has not visual feedback but that of two
boxes meeting each other on screen and a two arrows symbol that appears
whenever the mouse cursor hovers above a nearby location.
martin
next prev parent reply other threads:[~2017-10-10 8:14 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=59DC816D.40707@gmx.at \
--to=rudalics@gmx.at \
--cc=27830@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=kaushal.modi@gmail.com \
--cc=rpluim@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.