Scott Lowe

This is still an issue in Cursive 1.12.4-2022.1.

I have just discovered that this issue relates to issue https://github.com/cursive-ide/cursive/issues/771.

@Robsteranium Don't see why we can't have both plain text and GUI versions; it's easy to do. I added the optional label in the example just in case the poor...

https://github.com/Swirrl/grafter/blob/7c1f6184b8fbe95f8a78d39d38d56db76068e8e7/src/grafter_2/rdf/protocols.cljc#L352-L354

Rick commented elsewhere: > Ok probably a grafter issue to do with the regex preprocessing. Grafter should probably strip all comment lines before doing that processing. I have found the...

> There are some edge cases to consider with `#` My test case looks like this, with hashes in URIs and it works: ```sparql #This is the first comment line;...

Some background to the Sesame issue. Although we believe the comments sometimes cause issues elsewhere within a SPARQL file, the following information specifically relates to a problem seen with SPARQL...

@RicSwirrl Yes, that's my experience too... comments occasionally cause issues elsewhere, but by stripping them all, we will have that secondary issue covered as well, as you've righty surmised.

@RickMoynihan Will do. I'll look at that 0.12.x version of Grafter. I don't need the tests; I can run some code in the REPL.

I've looked at the latest RDF4j code. It looks to be better structured overall and is architecturally different to Sesame, however, when you get into the details the Sesame logic...