From: Lennart Borgman <lennart.borgman@gmail.com>
To: David Reitter <david.reitter@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Hl-line and visual-line
Date: Tue, 25 May 2010 01:03:34 +0200 [thread overview]
Message-ID: <AANLkTin8aMI6bTkHyBuOHmbd3apqYNbGE37ibO26z7BJ@mail.gmail.com> (raw)
In-Reply-To: <D4A02368-F5F9-4D86-9EB2-DB0CDD1F0CDE@gmail.com>
On Tue, May 25, 2010 at 12:47 AM, David Reitter <david.reitter@gmail.com> wrote:
> On May 24, 2010, at 6:37 PM, Lennart Borgman wrote:
>>>
>>> is your definition of `bovl' and `eovl'.
>>
>> I mean the same difference as between beginning-of-line and
>> line-beginning-position (point-at-bol). (I prefer the shorter versions
>> here. They are easier to read and easy to understand.)
>>
>> The first one moves point, but the second does not.
>
> (save-excursion
> (beginning-of-visual-line)
> (point))
>
> The presence of such functions may reinforce the impression that they could be used as "beg" and "end" parameters to any other function that will process the text between "beg" and "end", in order to make it operate on the visual line.
>
> This works for L2R or even R2L text, but as this thread has made clear, not in the bidirectional case.
>
> So one would want a warning in their DOC strings, if those functions are needed.
Good point of course. Maybe instead functions like
min-point-visual-line etc would better? Hm, that would be problematic
too because the direction of text might change from min to max on the
line. I think I am beginning to understand what the details here have
been about.
I think then it might be a bad idea to have those functions I suggest, yes.
A comment about that the text shown between beginning-of-visual-line
and end-... is not necessarily the text between those points when
bidirectional text is in the buffer would be good.
I did not realize that "bidi" meant bidirectional (i.e. text in both
directions) simultaneously before. I can realize Eli had some trouble
with this and the display engine. Great work.
next prev parent reply other threads:[~2010-05-24 23:03 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-20 20:30 Hl-line and visual-line David Reitter
2010-05-20 21:02 ` Eli Zaretskii
2010-05-21 2:35 ` David Reitter
2010-05-21 6:34 ` Tassilo Horn
2010-05-21 8:17 ` Eli Zaretskii
2010-05-21 10:16 ` Tassilo Horn
2010-05-21 14:22 ` David Reitter
2010-05-21 14:57 ` Eli Zaretskii
2010-05-23 17:26 ` Eli Zaretskii
2010-05-23 19:13 ` David Reitter
2010-05-23 20:33 ` Eli Zaretskii
2010-05-23 23:04 ` David Reitter
2010-05-24 18:16 ` Eli Zaretskii
2010-05-24 18:46 ` Stefan Monnier
2010-05-24 19:06 ` Lennart Borgman
2010-05-24 22:24 ` Eli Zaretskii
2010-05-24 22:37 ` Lennart Borgman
2010-05-24 22:47 ` David Reitter
2010-05-24 23:03 ` Lennart Borgman [this message]
2010-05-21 16:54 ` Lennart Borgman
2010-05-21 17:39 ` Eli Zaretskii
2010-05-21 20:24 ` Stefan Monnier
2010-05-21 22:31 ` Lennart Borgman
2010-05-22 0:18 ` Stefan Monnier
2010-05-22 2:35 ` Lennart Borgman
2010-05-22 13:10 ` Lennart Borgman
2010-05-22 17:04 ` Lennart Borgman
2010-05-21 6:36 ` 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=AANLkTin8aMI6bTkHyBuOHmbd3apqYNbGE37ibO26z7BJ@mail.gmail.com \
--to=lennart.borgman@gmail.com \
--cc=david.reitter@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).