Sergio A. Vargas

To be clear, the problem here is that there's no way of knowing what's code, i.e. input, and what's not code, i.e. the prompt and the **output.** A possible solution...

> How difficult would it be to adapt the existing rules here for a new grammar that could handle multi-line inputs? No idea. I know some repos have multiple grammars...

There's two seperate issues here, so I'll address them separately. ### Querying inner blocks The block rule used in the grammar is not visible (see #73). There's no technical limitation...

Thanks for the PR. I worked on refactoring string parsing in 803b97f641a67587ba40b6415dc384cca5fda2a0, mainly to fix a couple of bugs, but also to remove the serialization stuff from the scanner. The...

Note that this was allowed in the flisp parser. ```sh julia +lts -E ':(a.[1])' :(a.:([1])) ```

Hi @steffenhaug, thanks for the report. We don't handle `@doc` at all. This is probably a bug in the scanner with the way we parse the start of the string....

No concrete stats. I tried extracting my local `General.tar.gz`, but the `Project.toml` files there don't include that metadata. But looking at the [most popular packages](https://juliahub.com/ui/Packages), I see the following don't...

Also, @juliohm mentioned that there's a difference between an author and maintainer. _Author_ suggests the original creator of the package, while _maintainer_ suggests the person currently in charge of the...

Git history is a noisy channel. For example, most of the recent commits in Flux are just compat maintenance, dep bumping, etc. This doesn't necessarily reflect code ownership. We're also...