Lix should include a `lix` executable #508

New issue

Closed

opened 2024-09-09 22:22:09 +00:00 by rbt · 3 comments

rbt commented

2024-09-09 22:22:09 +00:00

Owner

From @jade:

it was my understanding that we had planned to do the git thing and make it redirect lix foo to lix-foo (#342)

I don't think it should replicate the nix command because the nix command has known bad CLI design and we should take our time to carefully design a new CLI experience

From @jade: > it was my understanding that we had planned to do the `git` thing and make it redirect `lix foo` to `lix-foo` (#342) > > I don't think it should replicate the `nix` command because the `nix` command has known bad CLI design and we should take our time to carefully design a new CLI experience

rbt added the

Area/build-packaging

label

2024-09-09 22:22:09 +00:00

lix-bot commented

2024-09-09 22:29:37 +00:00

Member

This issue was mentioned on Gerrit on the following CLs:

commit message in cl/1901 ("install: Make lix a symlink to nix")
comment in cl/2119 ("feat: add support for external lix- prefixed commands in the CLI")
commit message in cl/2914 ("libmain: undo accidental lix command stabilization")

This issue was mentioned on Gerrit on the following CLs: * commit message in [cl/1901](https://gerrit.lix.systems/c/lix/+/1901) ("install: Make `lix` a symlink to `nix`") * comment in [cl/2119](https://gerrit.lix.systems/c/lix/+/2119) ("feat: add support for external `lix-` prefixed commands in the CLI") * commit message in [cl/2914](https://gerrit.lix.systems/c/lix/+/2914) ("libmain: undo accidental lix command stabilization")

pennae commented

2025-03-08 13:17:16 +00:00

Owner

we have such a command now, but it's a link to the old cli for custom command support. should we maybe throw an error when this link is used and the experimental feature for custom commands is not enabled?