From: npostavs@gmail.com
To: Juri Linkov <juri@linkov.net>
Cc: 35802@debbugs.gnu.org, npostavs@gmail.com
Subject: bug#35802: Broken data loaded from uni-decomposition
Date: Tue, 11 Jun 2019 10:18:41 -0400 [thread overview]
Message-ID: <854l4wb3y6.fsf@gmail.com> (raw)
In-Reply-To: <87v9xie9a8.fsf@mail.linkov.net> (Juri Linkov's message of "Thu, 06 Jun 2019 23:41:35 +0300")
Juri Linkov <juri@linkov.net> writes:
>> And possibly let-binding search-spaces-regexp in find-auto-coding would
>> make sense (although, there's probably more places like this that might
>> break, not sure if we can ever hope to find them all).
>
> This is almost the same class of problems as wrapping re-search-forward
> in save-match-data, so finding all places that affect matching elsewhere
> will take time.
Actually maybe it's just a matter of making isearch bind
search-spaces-regexp less widely. I'm not quite following when the your
problem happens though. Can you show a backtrace from your original
problem using
(add-hook 'after-load-functions
(lambda (f) (when (string-match-p "uni-decomposition" f)
(debug nil :search-spaces-regexp search-spaces-regexp))))
next prev parent reply other threads:[~2019-06-11 14:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-19 19:46 bug#35802: Broken data loaded from uni-decomposition Juri Linkov
2019-06-06 17:07 ` npostavs
2019-06-06 20:41 ` Juri Linkov
2019-06-11 14:18 ` npostavs [this message]
2019-06-11 21:11 ` Juri Linkov
2019-06-16 2:12 ` Noam Postavsky
2019-06-16 19:22 ` Juri Linkov
2019-06-21 11:16 ` Noam Postavsky
2019-06-21 19:16 ` Juri Linkov
2019-06-22 22:35 ` Noam Postavsky
2019-06-23 21:25 ` Juri Linkov
2019-06-26 2:08 ` Noam Postavsky
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=854l4wb3y6.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=35802@debbugs.gnu.org \
--cc=juri@linkov.net \
/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).