From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Message Mode and bidi
Date: Wed, 28 Feb 2024 19:16:08 -0800 [thread overview]
Message-ID: <871q8wc64n.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <86sf1csdsh.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 28 Feb 2024 19:23:58 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Eric Abrahamsen <eric@ericabrahamsen.net>
>> Date: Wed, 28 Feb 2024 08:54:54 -0800
>>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>> > But beware: doing this in Emacs will cause effects that are unpleasant
>> > to readers of bidirectional text, because you could have "chess-like"
>> > text display, like this:
>> >
>> > asasasasasasasasasasasasassa
>> > ASASASASASASASASASASASASA
>> > xcxcxcxcxcxcxcxcxcxcxcxcxc
>> > JKJNJKKKNKNKNKNKNK
>> >
>> > etc. Here upper-case letters stand for RTL (like Arabic or Farsi)
>> > text and lower-case letters stand for LTR (like Latin or Cyrillic)
>> > text.
>>
>> This is the effect I was imagining in the header section of the message
>> buffer, and why I thought we should probably skip trying to handle this.
>> message-mode headers can be "continuation headers", as well, effectively
>> line-wrapped, which would make it even harder.
>
> Yes. But the same can happen in the body of the message, and will IMO
> be even more annoying, because people do care about the body.
>
>> Thanks for the background! I guess I was hoping that we could at least
>> support OP's original request, which is making the first paragraph of
>> the message body independent of the mail header separator as regards
>> BIDI display. I experimented with putting the value of
>> `mail-header-separator' into `bidi-paragraph-start|separate-re', but
>> couldn't get it to display that first paragraph starting on the right.
>> Do you think this is feasible, and worth the effort?
>
> No, I don't think it's worth the effort, even if you succeed. The
> price of leaving an empty line after the headers is so small that it
> isn't worth the hassle to try to avoid it. Once the user does that a
> few times, the technique will be burned into his/her muscle memory (I
> know because I went through that process myself, long ago).
Okay, fair enough! Thanks again.
next prev parent reply other threads:[~2024-02-29 3:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 1:12 Message Mode and bidi Christopher Culver via Emacs development discussions.
2024-02-19 3:36 ` Eli Zaretskii
2024-02-19 21:29 ` Christopher Culver via Emacs development discussions.
2024-02-19 21:50 ` Joost Kremers
2024-02-19 22:06 ` Christopher Culver via Emacs development discussions.
2024-02-20 0:46 ` Eric Abrahamsen
2024-02-20 3:37 ` Eli Zaretskii
2024-02-20 5:16 ` Eric Abrahamsen
2024-02-20 14:36 ` Eli Zaretskii
2024-02-28 16:54 ` Eric Abrahamsen
2024-02-28 17:23 ` Eli Zaretskii
2024-02-29 3:16 ` Eric Abrahamsen [this message]
2024-02-20 3:31 ` Eli Zaretskii
2024-02-20 3:29 ` 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=871q8wc64n.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=eliz@gnu.org \
--cc=emacs-devel@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).