Joe Pea

Here's the simplest reproduction of the problem I could make (a Meteor 1.3 app): https://github.com/trusktr/site/tree/regenerator-issue-236 To run, just ``` sh git clone [email protected]:trusktr/site.git cd site git checkout regenerator-issue-236 meteor ```...

Closing this one, since I deleted the account I used to open this issue, and making a new clean issue: #240. EDIT: Oh wait, I can't close it.

> > See comment. Basically this still has other problems. The solution is to handle paths and queries separately > > Hi, > > Any new updates on this issue....

> Any chance this will get done soon? I've actually never committed to a public repo, but this looks pretty straightforward. I'd be willing to try. @zomgbre willing to take...

Thank you John for making this extensive tracking of all the URL problems. I haven't read the whole issue, but we should eliminate custom URL handling and use the standardized...

> Will the code help you? > > ``` > > > let newMarked = marked; // I find that marked will be overwritten by Docsify, so save it before...

I think we should be letting the browser handle URLs natively. F.e. maybe we can use `new URL('./relative/file.foo', base)` where `base` could be the site base path like `http://localhost:3000/#/page/any_doc`. So...

@proke03 basically the docsify-themeable CSS depends on the DOM of Docsify. I think what we should do is in a totally separate pull request lets get a docsify-themeable deployment for...

It looks like it works on the Docsify site. Can you start with the config for search like in here: https://github.com/docsifyjs/docsify/blob/a69c22ac79f117f091fcfc96c46dc440ef151e48/index.html#L70 And then carefully convert to your languages and see...

Ah, good find a out the ordering. We should definitely mention that in the docs. I guess `/` matches everything, so it doesn't have a chance to fall through to...