Jonathan Arnett

It appears that [EDoc](https://www.erlang.org/doc/apps/edoc/chapter.html) supports special `%% @doc ...` comments, alongside other more specific constructs such as `%% @author ...`, which it can then compile into the EEP 48-compliant "chunks".

Sadly José's Google Doc appears to have been deleted (or else I specifically don't have access 😅) and the EEP hasn't yet been created.

+1. I will try to look into this if I find some extra time.

[Using `atom --no-sandbox` as mentioned in #23167](https://github.com/atom/atom/issues/23167#issuecomment-957818698) caused Atom to no longer crash for me. Actually, booting Atom with that flag once and clicking around seems to have fixed the...

Related to the first point, I think it might be appropriate to establish a convention for the file in which to use `Commanded.Application`. [The current Application documentation](https://hexdocs.pm/commanded/1.3.1/application.html) uses `MyApp.Application`, but...

> The `licenses` field is meant to list the licenses the project is licensed under, `or` or `and` does not matter to it. Does this mean that whether the licenses...

@supersimple Fortunately for us, the good folks over at SPDX have a solution to normalizing all kinds of crazy licenses, including composite licenses, licenses with exceptions, and even user-defined licenses:...

Speaking of Rust, a quick Google reveals that [the `license` field in a crate package manifest must be a valid SPDX 2.1 License Expression](https://doc.rust-lang.org/cargo/reference/manifest.html#the-license-and-license-file-fields).

A workaround is to add the following line to your configuration: ``` (setq projectile-generic-command "fd . -0 --type f --color=never") ```

This appears to be the same issue as #1765