@Shachar Itzhaky @Emilio Jesús Gallego Arias
In most of jscoq, coqdoc is displayed as html. Is there a way to enable this in the scratchpad?
it should be possible I understand
tho in the branch we work with markdown documents natively, and use prosemirror to display them
so depending on your case, it could be better to do that; @Shachar Itzhaky maybe we could deploy the fleche branch with prosemirror somewhere?
yes we sort of did not have time to do that. @Bas Spitters what you see in other pages is actually the coqdoc precompiled into HTML and just served statically, which is why the HTML part is not editable. You can ofc compile such documents yourself using jscoqdoc
but you will get the same behavior. If you want a document where both the text and the code are editable then the ProseMirror version that Emilio made is the way to go.
See https://x80.org/rhino-taur/?frontend=pm&content_type=plain or just https://x80.org/rhino-taur
you can press Ctrl+Enter to display goals at point
that was pretty quick Emilio :)
yeah just an rsync from the build tree
I've push a little commit to set the frontend by url, seems much more practical
I'm puzzled tho the wa backend works locally but not on my server, mmm
oh there are symlinks in node_modules, it's a very bad hack I'm trying to get rid of
perhaps your server does not like symlinks? Vercel also doesn't like them
The error is super strange, jsoo version works fine
Screenshot-2022-11-10-at-18.52.18.png this?
Yup
locally with make serve
works fine
puzzling
that's Chrome's fault
maybe it's because the URL?
instead of reporting a normal "failed to fetch" it tries to interpret the 404 as wasm
welp
look at the "network" tab, you will see some wasms are not found
my guess is that because they are symlinked
oh yes, maybe this is suspicious ? await this.core.run("/lib/icoq.bc", [], ["wacoq_post"])
I just saw your message, indeed it is because of the url
let's see where the problem is
I think this line should be
var icoq = new IcoqPod('../backend/wasm', '../node_modules');
instead of
var icoq = new IcoqPod('../backend/wasm', '../../../node_modules');
in my current setup
when wacoq comes from installed it should be the latter
Fixed in the deployment
asset uris are the devil
Yes, as always tooling / build setup takes a huge amount of time
@Emilio Jesús Gallego Arias That looks pretty impressive!
I got confused for a minute by the cursor placement. If I put my cursor after rewrite IHl. It says "No more goals."
I would expect this to only happen after putting my cursor after the r of reflexivity.
Is there a way to take an existing Coqdoc file and convert it into markdown to be used in rhino?
Bas Spitters said:
Emilio Jesús Gallego Arias That looks pretty impressive!
I got confused for a minute by the cursor placement. If I put my cursor after rewrite IHl. It says "No more goals."
I would expect this to only happen after putting my cursor after the r of reflexivity.
yes, this is precisely the kind of UI design choices that we still need to make before the Fleche model is usable. This is good feedback, we know that the current goal display is not intuitive yet; what we have now was mostly for us to test that we can extract and print goals properly.
a coqdoc → markdown translation sounds like it would be useful; perhaps Alectryon has this capability? I remember @Clément Pit-Claudel mentioning bidirectional translation in that area.
Yes, that would be useful. I'd imagine we may want to deprecate coqdoc syntax at some point and use something standard.
Last updated: Jun 01 2023 at 12:01 UTC