From: martin rudalics <rudalics@gmx.at>
To: Eli Zaretskii <eliz@gnu.org>
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: Sat, 07 Oct 2017 10:08:26 +0200 [thread overview]
Message-ID: <59D88B7A.9040202@gmx.at> (raw)
In-Reply-To: <83shewvcbv.fsf@gnu.org>
> This is OK for PROBLEMS, but maybe it should be in the user manual
> instead?
It's probably too internal in order to be mentioned in PROBLEMS. But is
the user manual really a suitable place for this? I understand your
concerns but, for example, the last paragraph of section "14.14 Window
Fringes" appears to me merely distracting for people who want to learn
basic things about fringes. Maybe that part should better go to section
"39.3 Truncation" of the Elisp manual.
As for the vertical borders I don't know. We would need to describe
them somewhere in a context of "resizing side-by-side windows with the
mouse" but we curently do that rather cryptically in section 21.5 of the
Emacs manual as
Furthermore, by clicking and dragging `mouse-1' on the divider
between two side-by-side mode lines, you can move the vertical boundary
to the left or right.
Nothing special about windows without vertical scroll bars.
martin
next prev parent reply other threads:[~2017-10-07 8:08 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 [this message]
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=59D88B7A.9040202@gmx.at \
--to=rudalics@gmx.at \
--cc=27830@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=eliz@gnu.org \
--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).