unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Alexandre Garreau <galex-713@galex-713.eu>
To: help-gnu-emacs@gnu.org
Subject: Re: RTL lines
Date: Wed, 27 Oct 2021 21:26:18 +0200	[thread overview]
Message-ID: <4537597.zJ5D36GCzO@galex-713.eu> (raw)
In-Reply-To: <83h7deeajw.fsf@gnu.org>

Pardon me, I think I missed that mail too, and caused you to loose time 
because of that (given the relatedness of many conversations now) :/

I really should read all emacs manual, I even have it printed…

Le lundi 18 octobre 2021, 15:18:11 CEST Eli Zaretskii a écrit :
> > From: Alexandre Garreau <galex-713@galex-713.eu>
> > Date: Mon, 18 Oct 2021 14:40:42 +0200
> > 
> > Is there a var to make any line whose first either rtl or ltr char is
> > RTL be displayed RTL (so for instance an org-mode definition list
> > (with ::) would be displayed RTL with the bullets at right, if the
> > defining terms (at the beginning, just after the */+/-/etc.) are in
> > arabic/hebrew/etc.)?
> Set bidi-paragraph-direction to the nil value.  It's a per-buffer
> variable.

Thank you!

> > Another idea I have is is there a way to do that per-paragraph (for
> > instance for a defun that would use a such language)?
> 
> The above will do that per paragraph.  That is, each paragraph will be
> LTR or RTL depending on the first "strong directional" character in
> that paragraph.

Thinking to it, yes, a paragraph is the most meaningful semantical unit to 
do that.  I guess in any file where lines can be filled (like, except csv 
files for instance) there wouldn’t be sense to do that…

…but I thought the definition of a paragraph was contextual, and determined 
what M-q would do… but here I notice it isn’t: it’s barely “any portion of 
text separated by a blank line”, so many bullets within org-mode (whose 
each would be filled/wrapped separately by M-q), and even several 
*sections* in org/outline-mode would be considered as a paragraph, until 
the next blank line, even in the middle of a subsection…

> (This all is supposed to be well documented in the Emacs manual.
> Hint, hint...)

Emacs is very big and so is its manual, but yes I should get more of an 
habit of searching within it, instead of simply limiting myself to doing 
C-h (maybe both kind of documentations could be hyperlinked? maybe they 
already are…)

> > and arbitrarily (for direction-agnostic languages such as some
> > extreme-
> > oriental ones)?
> 
> I don't think I understand what kind of "arbitrariness" you have in
> mind here.

Like “I want chinese to be written TTB” (well, let’s say japanese and LTR, 
given what you say thereafter).

> > and does emacs support TTB/BTT (top to bottom, bottom to top)
> 
> No.  if you want to submit patches to that effect,l they will be most
> welcome, though.

Thank you very much for the encouragement, if I succeed getting again into 
hacking I certainly will.



  reply	other threads:[~2021-10-27 19:26 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-18 12:40 RTL lines Alexandre Garreau
2021-10-18 13:18 ` Eli Zaretskii
2021-10-27 19:26   ` Alexandre Garreau [this message]
2021-10-28  6:04     ` Eli Zaretskii
2021-10-28  6:08       ` Alexandre Garreau
2021-10-28  7:03         ` tomas
2021-10-28  8:59         ` Eli Zaretskii
2021-10-27 14:50 ` Verticality and future of display engine and lines (bis) [Was: Re: RTL lines] Alexandre Garreau
2021-10-27 16:18   ` Eli Zaretskii
2021-10-27 18:46     ` Alexandre Garreau
2021-10-27 18:58       ` Eli Zaretskii
2021-10-27 19:54         ` Alexandre Garreau
2021-10-28  6:53           ` Eli Zaretskii
2021-10-28  7:12             ` Alexandre Garreau
2021-10-28  9:23               ` Eli Zaretskii
2021-10-28 14:40                 ` Alexandre Garreau
2021-10-28 16:11                   ` Eli Zaretskii
2021-10-28  7:18             ` Alexandre Garreau
2021-10-28  9:28               ` Eli Zaretskii
2021-10-28 14:28                 ` Alexandre Garreau
2021-10-28 16:07                   ` 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=4537597.zJ5D36GCzO@galex-713.eu \
    --to=galex-713@galex-713.eu \
    --cc=help-gnu-emacs@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.
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).