From: Eli Zaretskii <eliz@gnu.org>
To: "YUSUF ALPER ÇIKIŞIR" <yusufcikisir@std.iyte.edu.tr>
Cc: 59715@debbugs.gnu.org
Subject: bug#59715: 28.2; Emacs crashes after ``turkish-case-conversion-enable''
Date: Sun, 04 Dec 2022 14:56:03 +0200 [thread overview]
Message-ID: <83y1rn9vks.fsf@gnu.org> (raw)
In-Reply-To: <87edtf1gmi.fsf@std.iyte.edu.tr> (yusufcikisir@std.iyte.edu.tr)
> From: YUSUF ALPER ÇIKIŞIR
> <yusufcikisir@std.iyte.edu.tr>
> Cc: 59715@debbugs.gnu.org
> Date: Sun, 04 Dec 2022 15:46:13 +0300
>
> That's hilarious. I mean, I'm not writing "Iosevka". Why does it need
> to do something like this in the first place?
We usually downcase when we intern strings to produce symbols.
> I had:
>
> <alias>
> <family>monospace</family>
> <prefer>
> <family>Iosevka Comfy</family>
> </prefer>
> <default><family>Iosevka Comfy</family></default>
> </alias>
>
> in ~/.config/fontconfig/fonts.conf file. I've changed "Iosevka Comfy"
> with "iosevka comfy". I had also "Emacs.font: Iosevka Comfy-10" in
> ~/.Xresources file. I've also changed it with "iosevka comfy-10".
>
> But unfortunately, it's still the same.
I think there's some caching involved. Can you do whatever is needed to
force Fontconfig to refresh its caches? And maybe also restart the system,
in case X also caches stuff?
I will try to think about a cleaner solution to this. It isn't easy.
next prev parent reply other threads:[~2022-12-04 12:56 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 3:10 bug#59715: 28.2; Emacs crashes after ``turkish-case-conversion-enable'' YUSUF ALPER ÇIKIŞIR via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-30 16:12 ` Eli Zaretskii
2022-12-01 2:11 ` YUSUF ALPER ÇIKIŞIR via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-01 7:26 ` Eli Zaretskii
2022-12-01 22:26 ` YUSUF ALPER ÇIKIŞIR via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-02 7:23 ` Eli Zaretskii
2022-12-03 22:09 ` YUSUF ALPER ÇIKIŞIR via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-04 7:16 ` Eli Zaretskii
2022-12-04 8:29 ` YUSUF ALPER ÇIKIŞIR via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-04 8:33 ` YUSUF ALPER ÇIKIŞIR via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-04 10:20 ` Eli Zaretskii
2022-12-04 11:44 ` YUSUF ALPER ÇIKIŞIR via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-04 12:09 ` Eli Zaretskii
2022-12-04 12:17 ` Eli Zaretskii
2022-12-04 12:46 ` YUSUF ALPER ÇIKIŞIR via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-04 12:56 ` Eli Zaretskii [this message]
2022-12-04 13:10 ` Eli Zaretskii
2022-12-04 13:21 ` YUSUF ALPER ÇIKIŞIR via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-04 13:39 ` Eli Zaretskii
2022-12-04 13:56 ` YUSUF ALPER ÇIKIŞIR via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-04 17:38 ` Eli Zaretskii
2022-12-05 2:29 ` YUSUF ALPER ÇIKIŞIR via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-05 13:23 ` Eli Zaretskii
2022-12-06 16:09 ` YUSUF ALPER ÇIKIŞIR via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-06 16:20 ` Eli Zaretskii
2022-12-01 2:23 ` YUSUF ALPER ÇIKIŞIR via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=83y1rn9vks.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=59715@debbugs.gnu.org \
--cc=yusufcikisir@std.iyte.edu.tr \
/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).