From: Juri Linkov <juri@linkov.net>
To: npostavs@gmail.com
Cc: 35689@debbugs.gnu.org
Subject: bug#35689: Customizable char-fold
Date: Thu, 16 May 2019 23:13:17 +0300 [thread overview]
Message-ID: <87zhnmgntu.fsf@mail.linkov.net> (raw)
In-Reply-To: <85v9ya1mng.fsf@gmail.com> (npostavs@gmail.com's message of "Thu, 16 May 2019 10:47:47 -0400")
>> I can't find a standard way of doing this. So instead of using eval-and-compile
>> I'll try to recalculate the value explicitly when variables are customized:
>>
>> (when (or (get 'char-fold-include-base 'customized-value)
>> (get 'char-fold-include-alist 'customized-value)
>> (get 'char-fold-exclude-alist 'customized-value))
>> (setq char-fold-table (char-fold-make-table)))
>
> Instead of looking at symbol property values, which can make for a
> confusing time when setting variables outside of customize, I think it
> would be nicer to do something like this:
>
> (eval-and-compile (defconst char-fold--include-base-default ...))
>
> (defcustom char-fold-include-base char-fold--include-base-default
> :initialize #'custom-initialize-changed
I tried different possible values of :initialize,
but not custom-initialize-changed. I'll try this now.
The problem I encountered with the previous solution it that
calling `(setq char-fold-table (char-fold-make-table))' above
while loading char-fold.el by autoload, garbled data returned
from `(unicode-property-table-internal 'decomposition)',
it just returned garbage, maybe due to a broken coding.
I was busy debugging unidata-get-decomposition to
understand where this data corruption occurs.
next prev parent reply other threads:[~2019-05-16 20:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-11 21:22 bug#35689: Customizable char-fold Juri Linkov
2019-05-12 19:12 ` Juri Linkov
2019-05-12 20:30 ` Noam Postavsky
2019-05-13 20:31 ` Juri Linkov
2019-05-13 22:18 ` Noam Postavsky
2019-05-14 6:37 ` Eli Zaretskii
2019-05-14 20:14 ` Juri Linkov
2019-05-16 14:47 ` npostavs
2019-05-16 20:13 ` Juri Linkov [this message]
2019-05-21 20:34 ` Juri Linkov
2019-05-21 21:45 ` npostavs
2019-06-06 20:49 ` Juri Linkov
2019-06-24 17:33 ` Lars Ingebrigtsen
2019-06-24 20:40 ` Juri Linkov
2019-07-23 20:28 ` Juri Linkov
2019-07-28 22:46 ` Juri Linkov
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=87zhnmgntu.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=35689@debbugs.gnu.org \
--cc=npostavs@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 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.