unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Culver via "Emacs development discussions." <emacs-devel@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Message Mode and bidi
Date: Mon, 19 Feb 2024 22:29:15 +0100	[thread overview]
Message-ID: <8734to16tw.fsf@aura.christopherculver.com> (raw)
In-Reply-To: <867cj1qg4m.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 19 Feb 2024 05:36:57 +0200")

Eli Zaretskii <eliz@gnu.org> writes:
> I cannot reproduce this.  What I see is that Message mode supports
> bidirectional text as expected, including what you describe in the
> previous paragraph regarding right-aligning the RTL text.  So please
> tell more what you did by describing in detail the commands you typed.

I have tried this with a completely virgin Emacs installation, but
Message Mode continues to show less than full support for bidi text. The
steps were as follows:

* Move .emacs.d directory and .gnus.el[c] files to some other location.

* Launch Emacs.

* M-x gnus

* Gnus will pop up an error about unconfigured nntp support, but ignore.

* Press a in order to begin composing a new email in Message Mode.

* Move the cursor down to the message-body section, switch input method
  to farsi-translit-banan, and begin typing. The text does not
  automatically align to the right side of the window, nor does the
  cursor appear correctly to the left of the text being
  entered. (However, I do get full bidi support in a new .txt file
  created in text-mode.)

I am using Emacs 29.1 as packaged by Debian Stable Backports
(stable-bpo) on Wayland, so presumably the pure-gtk UI.

Because email is a special case, with decades-old standards, I thought I
should ask the devs if this phenomenon represented a deliberate choice
on the part of the Emacs devs. If this is indeed a bug, then please let
me know whether it should be reported to Debian as the packager, or if
it is something to be resolved by the Emacs devs themselves.



  reply	other threads:[~2024-02-19 21:29 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. [this message]
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
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=8734to16tw.fsf@aura.christopherculver.com \
    --to=emacs-devel@gnu.org \
    --cc=crculver@christopherculver.com \
    --cc=eliz@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).