unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Sineau Gh <sineaugh@gmail.com>
Cc: 42562@debbugs.gnu.org
Subject: bug#42562: Problem with rendering Persian text still exists in minibuffer and dired
Date: Fri, 31 Jul 2020 17:31:07 +0300	[thread overview]
Message-ID: <83h7tneoyc.fsf@gnu.org> (raw)
In-Reply-To: <CADVejcRww-DXzbBB-ThZMMv0O0wY1XPFGU-yR8bLhoQ4LjJtFg@mail.gmail.com> (message from Sineau Gh on Fri, 31 Jul 2020 18:02:19 +0430)

> From: Sineau Gh <sineaugh@gmail.com>
> Date: Fri, 31 Jul 2020 18:02:19 +0430
> Cc: 42562@debbugs.gnu.org
> 
> I have one more question. You have hinted in a previous email that
> setting the font for emacs may cause it to use a font that doesn't
> support arabic shaping. Are you suggesting that I can't use commands
> like `set-frame-font` or `default-aframe-list` like before? Or is
> there something else in my config that messes up the ligatures?

You can use those commands, but be careful which fonts you name there.
Especially if you use set-fontset-font for Persian characters.





  reply	other threads:[~2020-07-31 14:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-27 19:21 bug#42562: Problem with rendering Persian text still exists in minibuffer and dired Sineau Gh
2020-07-28  2:26 ` Eli Zaretskii
2020-07-29 15:50   ` Sineau Gh
2020-07-29 18:32     ` Eli Zaretskii
2020-07-30 12:57       ` Sineau Gh
2020-07-30 13:30         ` Eli Zaretskii
2020-07-30 19:12           ` Sineau Gh
2020-07-30 20:05             ` Sineau Gh
2020-07-31  5:13               ` Eli Zaretskii
2020-07-31  5:38                 ` Sineau Gh
2020-07-31  6:06                   ` Eli Zaretskii
2020-07-31  6:32                     ` Sineau Gh
2020-07-31 12:56                       ` Eli Zaretskii
2020-07-31 13:32                         ` Sineau Gh
2020-07-31 14:31                           ` Eli Zaretskii [this message]
2022-03-22 15:37                         ` Lars Ingebrigtsen

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=83h7tneoyc.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=42562@debbugs.gnu.org \
    --cc=sineaugh@gmail.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).