all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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 15:39:06 +0200	[thread overview]
Message-ID: <83v8mr9tl1.fsf@gnu.org> (raw)
In-Reply-To: <87o7sj1ezy.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 16:21:21 +0300
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > 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?
> 
> After cleaning fontconfig cache, rerunning "fc-cache -f -v", and
> restarting the system, it's still the same.  Are you sure that's the
> main reason?

It's the only explanation that makes sense, but maybe I got the details
wrong.

Please try the following, after starting GDB:

  (gdb) source /path/to/emacs/src/.gdbinit
  (gdb) break fontset.c:1701
  (gdb) commands
    > pp name
    > end
  (gdb) run -Q

Then, when the breakpoint breaks, look at the name it displays and see if
you see some pattern that has "Iosevka" in it.  You will have to type
"continue" each time the breakpoint breaks, to continue Emacs.  If I'm
right, you will see something with "Iosevka" in it.

> Thank you for your help.  I can migrate to different fonts by virtue of
> this bug. :-)

Yes.  One other idea is to use Fontconfig aliases, so that the font can be
named differently as far as Emacs is concerned, but I'm not sure it will
help.





  reply	other threads:[~2022-12-04 13:39 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
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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83v8mr9tl1.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 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.