From: Eli Zaretskii <eliz@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 21012@debbugs.gnu.org
Subject: bug#21012: 25.0.50; eww: last char of a line sometimes not fully visible
Date: Fri, 10 Jul 2015 09:03:17 +0300 [thread overview]
Message-ID: <83pp40blcq.fsf@gnu.org> (raw)
In-Reply-To: <87egkh3xl3.fsf@web.de>
> From: Michael Heerdegen <michael_heerdegen@web.de>
> Cc: 21012@debbugs.gnu.org
> Date: Thu, 09 Jul 2015 22:06:16 +0200
>
> The problem described by me (from the screenshot) is however not
> completely fixed (recipe follows).
>
> What I originally posted seems to happen with any text, it is more
> likely to happen when you use positive text-scale-mode, and it still
> happens.
>
> If you want a precise recipe (though it's just a random example): emacs
> -Q, C-h C-a, click on the first link (named "Gnu Emacs") with mouse-2.
> In line 135, the last char is truncated.
>
> If you hit C-x C-+, you will find more and more partly visible chars the
> more you scale up.
>
> Using `end-of-visual-line' seemed to fix this, but we can't use it.
> Is `window-text-pixel-size' useful?
The problem here is that shr assumes that the last character on a
visual line is always fully visible, which is false when
truncate-lines is non-nil. The last call to forward-char in
shr-vertical-motion should _not_ be made when the character we ended
up at is too wide to be fully visible at the end of a visual line.
The problem is that functions we have that can tell if that happens
require the relevant portion of the buffer to be displayed in some
window, so I think shr.el cannot use them.
If the result of what we have now is too annoying, the only way to
solve it I could think of is to artificially reduce the available
window width by one more column. This would lose us one column in
some cases, and will not solve the issue completely (a _very_ wide
character will still be partially visible), but it could be a stopgap.
Better ideas are welcome.
next prev parent reply other threads:[~2015-07-10 6:03 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-08 18:10 bug#21012: 25.0.50; eww: last char of a line sometimes not fully visible Michael Heerdegen
2015-07-08 20:03 ` Eli Zaretskii
2015-07-08 20:24 ` Michael Heerdegen
2015-07-09 2:38 ` Eli Zaretskii
2015-07-09 11:01 ` Michael Heerdegen
2015-07-09 14:43 ` Eli Zaretskii
2015-07-09 19:42 ` Michael Heerdegen
2015-07-09 15:34 ` Eli Zaretskii
2015-07-09 20:06 ` Michael Heerdegen
2015-07-10 6:03 ` Eli Zaretskii [this message]
2015-07-10 12:55 ` Michael Heerdegen
2015-07-10 13:06 ` Eli Zaretskii
2015-07-10 14:16 ` Michael Heerdegen
2015-07-10 14:43 ` Eli Zaretskii
2015-07-10 18:04 ` Michael Heerdegen
2015-07-10 18:45 ` Eli Zaretskii
2015-07-10 19:19 ` Michael Heerdegen
2015-07-10 19:31 ` Eli Zaretskii
2015-07-11 12:02 ` Michael Heerdegen
2015-07-11 13:45 ` Eli Zaretskii
2015-07-20 16:33 ` Michael Heerdegen
2015-07-20 16:34 ` Eli Zaretskii
2015-07-21 18:49 ` Michael Heerdegen
2015-09-25 4:00 ` Katsumi Yamaoka
2015-09-25 14:45 ` Michael Heerdegen
2015-09-28 21:30 ` Michael Heerdegen
2015-09-29 5:37 ` Eli Zaretskii
2015-10-03 8:08 ` Michael Heerdegen
2015-10-03 9:42 ` Eli Zaretskii
2015-10-03 12:41 ` Michael Heerdegen
2015-10-04 6:31 ` Michael Heerdegen
2015-10-04 7:09 ` Eli Zaretskii
2015-10-04 7:11 ` Michael Heerdegen
2015-10-04 7:39 ` Michael Heerdegen
2015-10-04 8:49 ` Eli Zaretskii
2015-10-04 10:18 ` Michael Heerdegen
2015-07-08 20:31 ` Michael Heerdegen
2015-10-07 6:34 ` bug#21012: Close Michael Heerdegen
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=83pp40blcq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=21012@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
/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.