You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(I observed the failure on older versions before, but I tried to make the issue go away by upgrading.)
How I traced the error to the _CoqProject
I googled "Bad bounding indices", there were no hits whatsoever on the Coq resources, but some Github issues on some totally unrelated Emacs modes that were related to the cl-subseq function.
I then grepped the PG sources, there is a single use of cl-subseq:
(warn"Invalid _CoqProject: not enough arguments for %S" switch))))
(cons switch arguments))
switch))
It looks like the code is trying to be robust against failures, but for some reason (maybe the unless-debug part?) this attempt fails on my machine and PG is unusable with broken _CoqProject files -- with a very obscure error message.
The text was updated successfully, but these errors were encountered:
gasche
added a commit
to gasche/PG
that referenced
this issue
Oct 3, 2023
The error
I have an incorrect _CoqProject file with the following content:
When running Emacs+PG on a .v file in the same directory, the "Next step" or "Use buffer" commands error with an obscure message:
Repro script:
Versions:
(I observed the failure on older versions before, but I tried to make the issue go away by upgrading.)
How I traced the error to the _CoqProject
I googled "Bad bounding indices", there were no hits whatsoever on the Coq resources, but some Github issues on some totally unrelated Emacs modes that were related to the
cl-subseq
function.I then grepped the PG sources, there is a single use of
cl-subseq
:PG/coq/coq-system.el
Lines 550 to 559 in e7aad1d
It looks like the code is trying to be robust against failures, but for some reason (maybe the
unless-debug
part?) this attempt fails on my machine and PG is unusable with broken _CoqProject files -- with a very obscure error message.The text was updated successfully, but these errors were encountered: