From: Eli Zaretskii <eliz@gnu.org>
To: larsi@gnus.org
Cc: 39911@debbugs.gnu.org, neil.okamoto@gmail.com
Subject: bug#39911: 27.0.90; error in wisent-total-conflicts if no source filename
Date: Fri, 13 Mar 2020 11:43:44 +0200 [thread overview]
Message-ID: <83mu8k8u9b.fsf@gnu.org> (raw)
In-Reply-To: <83pndruo3j.fsf@gnu.org> (message from Eli Zaretskii on Thu, 05 Mar 2020 11:50:56 +0200)
Ping!
> Date: Thu, 05 Mar 2020 11:50:56 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 39911@debbugs.gnu.org
>
> > From: Neil Okamoto <neil.okamoto@gmail.com>
> > Date: Wed, 4 Mar 2020 09:23:36 -0800
> >
> > This bug was detected while running docker.el and other packages that depend on tablist [1]. Tablist is an
> > extension of tabulated-list-mode that provides the ability to filter the tabulated list via an expression language. I
> > am not the author of tablist however the author is aware of this issue.
> >
> > In 27.0.90, tablist is now giving an error when entering its expression editor. In the debugger I traced the error
> > to wisent-total-conflicts in lisp/cedet/semantic/wisent/comp.el line 2273, in commit
> > 390b4bc1e25fe691548d7ec982eb2f7027fe26a3 [2]. That commit introduced a mechanism to ignore
> > “expected conflicts” via a symbol whose name is constructed on the fly like this:
> >
> > (format "wisent-%s--expected-conflicts"
> > (replace-regexp-in-string "\\.el$" "" src)
> >
> > However, this code doesn’t handle the case where the filename “src” is nil.
>
> Thank you for your report.
>
> Lars, could you please look into this? It's a regression in Emacs 27.
>
>
>
>
next prev parent reply other threads:[~2020-03-13 9:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-04 17:23 bug#39911: 27.0.90; error in wisent-total-conflicts if no source filename Neil Okamoto
2020-03-05 9:50 ` Eli Zaretskii
2020-03-13 9:43 ` Eli Zaretskii [this message]
2020-03-14 12:18 ` Lars Ingebrigtsen
2020-03-14 13:01 ` Eli Zaretskii
2020-03-14 15:47 ` Neil Okamoto
2020-03-15 21:59 ` Neil Okamoto
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=83mu8k8u9b.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=39911@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=neil.okamoto@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 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).