From: Anders Lindgren <andlind@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 22891@debbugs.gnu.org
Subject: bug#22891: 25.0.92; set-fringe-mode with left fringe 0 breaks window width calculations on Mac OS (again)
Date: Fri, 15 Apr 2016 10:05:19 +0200 [thread overview]
Message-ID: <CABr8ebZHHnjzZ8L9s-EXTA88jtKW3GVNe6_7oFwxuoNAd=3ijQ@mail.gmail.com> (raw)
In-Reply-To: <8360vje2rr.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1160 bytes --]
Hi!
To see what I meant, create a new buffer with "C-x b", then paste the
> same text there, after setting the left fringe width to zero.
>
Yes, now I see it. (However, the continuation characters disappeared when
L2R text was entered on the line before the R2L text.)
> Also, I noticed that `window-max-chars-per-line' does not take into
> account the variable `left-frame-width' (and
> > presumably `right-frame-width').
>
> You mean left-fringe-width, I presume? Yes, that's probably a bug.
>
Yes, I mean `left-fringe-width'.
> Why is this useful, when we already have window-max-chars-per-line?
> IOW, when would you like to know about the continuation glyph, and not
> about how many characters can be displayed on a line?
>
I intended it as a way to implement `window-max-chars-per-line' in a more
robust way than today.
In addition, I can think of a use case. If you want to create a window of a
specific width, excluding the continuation glyph, this can be used:
(split-window-right (if (continuation-glyph-visible-p (selected-window))
(+ width 1)
width))
-- Anders
[-- Attachment #2: Type: text/html, Size: 2170 bytes --]
next prev parent reply other threads:[~2016-04-15 8:05 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 6:38 bug#22891: 25.0.92; set-fringe-mode with left fringe 0 breaks window width calculations on Mac OS (again) Constantine Vetoshev
2016-04-11 6:58 ` martin rudalics
2016-04-15 1:24 ` Constantine Vetoshev
2016-04-20 13:48 ` martin rudalics
2016-04-14 5:33 ` Anders Lindgren
2016-04-14 15:17 ` Eli Zaretskii
2016-04-14 18:19 ` Anders Lindgren
2016-04-14 19:24 ` Eli Zaretskii
2016-04-15 7:11 ` Anders Lindgren
2016-04-15 7:42 ` Eli Zaretskii
2016-04-15 8:05 ` Anders Lindgren [this message]
2016-04-15 8:25 ` Eli Zaretskii
2016-04-23 18:42 ` bug#22891: Anders Lindgren
2016-04-23 19:03 ` bug#22891: Daniel Colascione
2016-04-24 8:40 ` bug#22891: martin rudalics
2016-04-24 13:04 ` bug#22891: Anders Lindgren
2016-04-24 19:07 ` bug#22891: Anders Lindgren
2016-04-26 6:34 ` bug#22891: martin rudalics
2016-04-26 6:44 ` bug#22891: Eli Zaretskii
2016-04-26 19:10 ` bug#22891: Anders Lindgren
2016-04-26 19:17 ` bug#22891: Eli Zaretskii
2016-04-26 21:07 ` bug#22891: Anders Lindgren
2016-04-27 6:21 ` bug#22891: Eli Zaretskii
2016-04-27 21:30 ` bug#22891: Anders Lindgren
2016-04-28 6:33 ` bug#22891: martin rudalics
2016-04-26 19:03 ` bug#22891: Constantine Vetoshev
2016-04-27 21:38 ` bug#22891: Fixed: 25.0.92; set-fringe-mode with left fringe 0 breaks window width calculations on Mac OS (again) Anders Lindgren
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='CABr8ebZHHnjzZ8L9s-EXTA88jtKW3GVNe6_7oFwxuoNAd=3ijQ@mail.gmail.com' \
--to=andlind@gmail.com \
--cc=22891@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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).