From: Eli Zaretskii <eliz@gnu.org>
To: Jim Porter <jporterbugs@gmail.com>
Cc: 68881@debbugs.gnu.org, juri@linkov.net
Subject: bug#68881: 30.0.50; [PATCH] Field properties confuse 'outline-minor-mode'
Date: Sun, 11 Feb 2024 08:07:47 +0200 [thread overview]
Message-ID: <865xyvttxo.fsf@gnu.org> (raw)
In-Reply-To: <254d7a98-d39d-2481-5a2a-01eea80fb657@gmail.com> (message from Jim Porter on Sat, 10 Feb 2024 13:14:34 -0800)
> Date: Sat, 10 Feb 2024 13:14:34 -0800
> Cc: 68881@debbugs.gnu.org, juri@linkov.net
> From: Jim Porter <jporterbugs@gmail.com>
>
> On 2/10/2024 11:23 AM, Eli Zaretskii wrote:
> > I don't understand what text directionality has to do with the issue
> > at hand. If you elaborate, I could perhaps be of assistance in this
> > matter.
>
> I think nothing in this case. I just wasn't sure initially whether
> 'pos-bol' and 'line-beginning-position' handled directionality
> differently. Since they handle it the same way, I think there's no harm
> in using 'pos-bol' in this case.
They both go to the smallest buffer position of the line (modulo the
fields issue). If an LTR line starts with RTL characters, that buffer
position will not be the leftmost one, but that's all. (I don't think
we have a function to go to the position that is the leftmost on
display, probably because that was never needed.)
next prev parent reply other threads:[~2024-02-11 6:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 23:51 bug#68881: 30.0.50; [PATCH] Field properties confuse 'outline-minor-mode' Jim Porter
2024-02-07 17:37 ` Juri Linkov
2024-02-10 18:22 ` Jim Porter
2024-02-10 19:23 ` Eli Zaretskii
2024-02-10 21:14 ` Jim Porter
2024-02-11 6:07 ` Eli Zaretskii [this message]
2024-02-11 7:08 ` Jim Porter
2024-02-11 17:40 ` Juri Linkov
2024-02-11 18:19 ` Jim Porter
2024-02-12 18:25 ` Juri Linkov
2024-02-13 4:03 ` Jim Porter
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=865xyvttxo.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=68881@debbugs.gnu.org \
--cc=jporterbugs@gmail.com \
--cc=juri@linkov.net \
/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).