From: Eli Zaretskii <eliz@gnu.org>
To: Boruch Baum <boruch_baum@gmx.com>
Cc: 39002@debbugs.gnu.org
Subject: bug#39002: [feature requests] calendar-hebrew [code included]
Date: Tue, 07 Jan 2020 19:33:25 +0200 [thread overview]
Message-ID: <835zhncgt6.fsf@gnu.org> (raw)
In-Reply-To: <20200107171141.rcapyzcwrd4hqdfn@E15-2016.optimum.net> (message from Boruch Baum on Tue, 7 Jan 2020 12:11:41 -0500)
> Date: Tue, 7 Jan 2020 12:11:41 -0500
> From: Boruch Baum <boruch_baum@gmx.com>
> Cc: 39002@debbugs.gnu.org
>
> Attached is a screenshot displaying three relevant buffers. Below the
> calendar buffer is the content of my ~/.emacs.d/diary file. Note the
> sequence of elements: 1) Title line (LTR, implicit; 2) Hebrew date
> (RTL); 3) sun times (LTR); 4) Parasha (RTL). However, in the diary
> output buffer, at the bottom of the screen shot, the lines are displayed
> in the sequence 1,4,2,3.
I don't think I see the part with the 1,4,2,3 order (sorry if I'm
blind), but did you try to use the function
bidi-string-mark-left-to-right? IIUC the problem, that function was
created exactly for these use cases, where bidi reordering causes a
jumble in what is supposed to be columnar display of several
substrings. You should wrap each substring in the wrapper produced by
bidi-string-mark-left-to-right, and then concatenate the results with
the "|" or whatever separators in-between.
IOW, it should not be necessary to change the paragraph direction in
these cases.
> That covers bugs B & C. Bug A and a fix for it
> would be reproduced by applying / removing the hook function at line 372
> of the previously submitted `cal-ivrit.el'
>
>
> (defun cal-ivrit-diary-fancy-display-mode-hook-function ()
> (setq bidi-paragraph-start-re "^")
> (setq bidi-paragraph-separate-re "^"))
>
> (add-hook 'diary-fancy-display-mode-hook
> 'cal-ivrit-diary-fancy-display-mode-hook-function)
Removing this and then doing what?
> For an illustration of emacs bug #15541 (nine+ years old!), see the
> attached org-mode file.
It is not a bug, it's the intended behavior. If you have Org files
with such long headings of RTL text, you should set the variable
bidi-paragraph-direction to nil in that buffer (or even to
right-to-left, if all of the headings use RTL text).
next prev parent reply other threads:[~2020-01-07 17:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-07 6:28 bug#39002: [feature requests] calendar-hebrew [code included] Boruch Baum
2020-01-07 15:54 ` Eli Zaretskii
2020-01-07 17:11 ` Boruch Baum
2020-01-07 17:33 ` Eli Zaretskii [this message]
2020-01-07 18:29 ` Boruch Baum
2020-01-07 18:48 ` Eli Zaretskii
2020-01-07 19:49 ` Boruch Baum
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=835zhncgt6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=39002@debbugs.gnu.org \
--cc=boruch_baum@gmx.com \
/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).