Currently there's an ambiguity with
where list could be interpreted as a command or a language. Currently it's a command, but whenever a language with the same name would appear (and conversely, if a new command named like an existing language appears) there could be some troubles with e.g. some scripts invoking bliss.
Commands and languages should be separated, possible options (please edit if you have other ideas):
- hyphens, e.g.
bliss --cache (bonus: shortened commands, i.e. bliss -c
- argument for languages, e.g.
bliss --lang rust
- add a
lang command, like this: bliss lang rust,python
Currently there's an ambiguity with
where
listcould be interpreted as a command or a language. Currently it's a command, but whenever a language with the same name would appear (and conversely, if a new command named like an existing language appears) there could be some troubles with e.g. some scripts invokingbliss.Commands and languages should be separated, possible options (please edit if you have other ideas):
bliss --cache(bonus: shortened commands, i.e.bliss -cbliss --lang rustlangcommand, like this:bliss lang rust,python