From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Verticality and future of display engine and lines (bis) [Was: Re: RTL lines]
Date: Thu, 28 Oct 2021 12:23:58 +0300 [thread overview]
Message-ID: <83k0hxtscx.fsf@gnu.org> (raw)
In-Reply-To: <9299581.M7KuVC2vgW@galex-713.eu> (message from Alexandre Garreau on Thu, 28 Oct 2021 09:12:38 +0200)
> From: Alexandre Garreau <galex-713@galex-713.eu>
> Cc: Eli Zaretskii <eliz@gnu.org>
> Date: Thu, 28 Oct 2021 09:12:38 +0200
>
> > I guess you are unaware, or perhaps forgot, that the display engine
> > itself scrolls the window when it finds that necessary.
>
> oh… but still that’s a few functions right…? I hope… like “scroll down”
> and “scroll up” calls that should be conditionally changed to “scroll
> forward” and “scroll backward”
I guess you think that scrolling, in whatever direction, is a simple
business. It isn't; what those "few functions" do has a lot of
implicit assumptions, most of them will be wrong with the change of
direction. Someone(TM) will have to come up with the necessary logic
that doesn't exist, and make it support all the scroll-related
features we have, like scroll-step, scroll-conservatively,
scroll-up/down-aggressively, scroll-preserve-screen-position, etc.
And then the low-level code which scrolls the screen by moving pixels
will have to be rethought as well.
> > > Did you really look at the screenshots? don’t you see all the blank
> > > between the lines?
> >
> > I'm talking about what I see in my Emacs session where I read your
> > email. If any Emacs session displays that as you describe, that's
> > either a font configuration problem or some rendering bug that isn't
> > present in my build of Emacs.
>
> But did you look at the screenshots? doesn’t your gnus support simple and
> direct display of mime attachments?
(I don't use Gnus.) Of course, I looked at them. Why do you ask?
they look like display bugs to me, as I said.
> > and I'm not even sure I understand why would you like to
> > do something like that.
>
> I already said it was to make reading more comfortable without having to
> lump from one part of the text to another, read, and yet again go there to
> resume reading, so the direction of reading is always consistent (and
> ideally to have even less jumping, one would need to use boustrophedon as
> a script direction, but afaik no existing software supports that)
I cannot imagine it will be easy to read an RTL text that wasn't
reordered for display. You'd have to read it one character at a time,
something that is extremely slow.
next prev parent reply other threads:[~2021-10-28 9:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-18 12:40 RTL lines Alexandre Garreau
2021-10-18 13:18 ` Eli Zaretskii
2021-10-27 19:26 ` Alexandre Garreau
2021-10-28 6:04 ` Eli Zaretskii
2021-10-28 6:08 ` Alexandre Garreau
2021-10-28 7:03 ` tomas
2021-10-28 8:59 ` Eli Zaretskii
2021-10-27 14:50 ` Verticality and future of display engine and lines (bis) [Was: Re: RTL lines] Alexandre Garreau
2021-10-27 16:18 ` Eli Zaretskii
2021-10-27 18:46 ` Alexandre Garreau
2021-10-27 18:58 ` Eli Zaretskii
2021-10-27 19:54 ` Alexandre Garreau
2021-10-28 6:53 ` Eli Zaretskii
2021-10-28 7:12 ` Alexandre Garreau
2021-10-28 9:23 ` Eli Zaretskii [this message]
2021-10-28 14:40 ` Alexandre Garreau
2021-10-28 16:11 ` Eli Zaretskii
2021-10-28 7:18 ` Alexandre Garreau
2021-10-28 9:28 ` Eli Zaretskii
2021-10-28 14:28 ` Alexandre Garreau
2021-10-28 16:07 ` Eli Zaretskii
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=83k0hxtscx.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@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.
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).