unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: emacs-devel@gnu.org
Subject: Re: Message Mode and bidi
Date: Tue, 20 Feb 2024 05:37:04 +0200	[thread overview]
Message-ID: <86y1bfolgf.fsf@gnu.org> (raw)
In-Reply-To: <87ttm4klnl.fsf@ericabrahamsen.net> (message from Eric Abrahamsen on Mon, 19 Feb 2024 16:46:22 -0800)

> From: Eric Abrahamsen <eric@ericabrahamsen.net>
> Date: Mon, 19 Feb 2024 16:46:22 -0800
> 
> Christopher Culver via "Emacs development discussions."
> <emacs-devel@gnu.org> writes:
> 
> > Joost Kremers <joostkremers@fastmail.fm> writes:
> >> When you compose a new message, is there a line "--text follows this line--"
> >> separating the headers and the message text? In my case, there is (I use mu4e)
> >> and when I type Arabic text on the line below this text, I get the effect you
> >> mention. If I leave an empty line after "--text follows this line--", bidi works
> >> as expected.
> >
> > Indeed, if I just go down one line and then begin typing, bidi works as
> > expected. I am feeling very foolish that I did not even try this. Thank
> > you for clearing up this problem, and for shedding light on how Emacs
> > considers paragraphs.
> 
> This is a bit weird, because the value of `mail-header-separator'
> ("--text follows this line--") is added to both `paragraph-start' and
> `paragraph-separate') in `message-mode'. You'd think one of those would
> do it.

Emacs doesn't use paragraph-separate and paragraph-start to define
where a paragraph starts and ends, for the purposes of determining the
base directionality of a paragraph.  It uses separate variables for
that, see the node "Bidirectional Editing" in the Emacs user manual.
The reason for using separate variables is because several modes,
including (but not limited to) message-mode, set the former variables
to regexps that get in the way of bidi reordering, and could easily
produce wrong results on display.



  reply	other threads:[~2024-02-20  3:37 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 [this message]
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
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=86y1bfolgf.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=eric@ericabrahamsen.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).