From: Eli Zaretskii <eliz@gnu.org>
To: "fr_ml@t-online.de" <fr_ml@t-online.de>
Cc: 56695@debbugs.gnu.org
Subject: bug#56695: A new and old font problem with Arabic
Date: Sun, 14 Aug 2022 09:20:26 +0300 [thread overview]
Message-ID: <83h72fl51x.fsf@gnu.org> (raw)
In-Reply-To: <1660427925610.540824.409826e69b5c567fce3ea5120d2fb9a8fa5eb8c2@spica.telekom.de> (fr_ml@t-online.de)
> Date: Sat, 13 Aug 2022 23:58:45 +0200 (CEST)
> From: "fr_ml@t-online.de" <fr_ml@t-online.de>
> Cc: "56695-done@debbugs.gnu.org" <56695-done@debbugs.gnu.org>
>
>
> Unfortunately I have another question.
>
> Is it possible to force emacs to re-position the characters/glyphs?
>
> It doesn't help to re-open the file.
> The command:
> (set-fontset-font "fontset-default" 'arabic "ANOTHER FONT")
> helps only for one-time. After some typing re-using the command doesn't help.
>
> This command:
> M-: (clear-composition-cache) RET
> seems to change something but it doesn't help.
>
> Somehow Emacs seems to remember the false positioning of the characters.
> If I a start a new Emacs the problem disappears (for some time, as I said).
>
> So how can I let Emacs "forget" the false positioning and make a new one?
If clear-composition-cache doesn't help, I don't know any way short of
restarting Emacs. Sorry.
next prev parent reply other threads:[~2022-08-14 6:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 8:11 bug#56695: A new and old font problem with Arabic fr_ml
2022-07-22 11:08 ` Eli Zaretskii
[not found] ` <1658497265479.1589294.1e7fbe71a9c257912af2f6c3a3b45532d616817d@spica.telekom.de>
2022-07-22 14:18 ` Eli Zaretskii
2022-07-22 15:58 ` bug#56695: AW: " fr_ml
2022-07-22 16:21 ` Eli Zaretskii
2022-07-24 7:24 ` bug#56695: AW: " fr_ml
2022-07-24 8:58 ` Eli Zaretskii
2022-07-25 15:29 ` bug#56695: AW: " fr_ml
2022-07-25 16:06 ` Eli Zaretskii
2022-07-25 20:46 ` bug#56695: AW: " fr_ml
2022-08-13 21:58 ` fr_ml
2022-08-14 6:20 ` Eli Zaretskii [this message]
2022-08-14 12:11 ` fr_ml
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83h72fl51x.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=56695@debbugs.gnu.org \
--cc=fr_ml@t-online.de \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.