refactor: rename binary invocations from lux -> lx

Author: vhyrro

docs/tutorial/02-getting-started.md

@@ -38,12 +38,12 @@ Make sure that `~/.cargo/bin/` is part of your shell's `$PATH`!
 
 ## Checking Installation
 
-Ensure that installation was successful by running `lux help`.
+Ensure that installation was successful by running `lx help`.
 You should see output similar to the following:
 ```
 A fast and efficient Lua package manager
 
-Usage: lux [OPTIONS] <COMMAND>
+Usage: lx [OPTIONS] <COMMAND>
 
 ...
 ```

docs/tutorial/03-creating-a-project.md

@@ -11,7 +11,7 @@ We'll store our code in a `my-lua-project/` directory.
 To do so, we can run:
 
 ```bash
-lux new my-lua-project
+lx new my-lua-project
 ```
 
 We'll now be asked to provide information about our project so `lux` can generate
@@ -75,7 +75,7 @@ To check whether our project was made successfully, first make sure you're in th
 Now, you can run a secret command:
 
 ```bash
-lux debug project
+lx debug project
 ```
 
 This will show information about the project if it was properly created. If everything

docs/tutorial/04-adding-dependencies.md

@@ -7,7 +7,7 @@ Lua has a very little standard library, so let's download some dependencies to g
 Since we want to develop a CLI, we need a library capable of parsing flags and arguments.
 To do so, we will use [`argparse`](https://luarocks.org/modules/argparse/argparse). We'll install it with the following command:
 ```sh
-lux add [email protected]
+lx add [email protected]
 ```
 
 :::note
@@ -24,14 +24,14 @@ with our code. However, just running `lua` will *not* load our dependenices. To
 `lua` REPL with our dependencies loaded, we need to run the following command:
 
 ```sh
-lux lua
+lx lua
 ```
 
 This acts as a direct wrapper around the `lua` program.
 Once in the REPL, let's try to require our `argparse` code. Type `require("argparse").version`
 and press enter. Below is the successful output:
 
-```sh title="lux lua"
+```sh title="lx lua"
 Lua 5.4.7  Copyright (C) 1994-2024 Lua.org, PUC-Rio
 > require("argparse").version
 0.7.1

docs/tutorial/05-making-the-application.md

@@ -74,11 +74,11 @@ end
 We've transformed our program to check if the input contains the word "hello".
 Below are some example outputs:
 
-```none title='lux run "Hello, world!"'
+```none title='lx run "Hello, world!"'
 Your input has the word 'hello' in it!
 ```
 
-```none title='lux run "Hi, world!"'
+```none title='lx run "Hi, world!"'
 Your input does not have the word 'hello' in it!
 ```
 

docs/tutorial/06-testing.md

@@ -81,10 +81,10 @@ end)
 
 ## Running the Tests
 
-We're now ready to run our tests! `lux test` will run all the tests in your
+We're now ready to run our tests! `lx test` will run all the tests in your
 project. After the automatic installation of `busted` you should see the following output:
 
-```sh title="lux test"
+```sh title="lx test"
 ●●
 2 successes / 0 failures / 0 errors / 0 pending : 0.001615 seconds
 ```

docs/tutorial/07-code-hygiene.md

@@ -14,21 +14,21 @@ Linting is the process of analyzing code for potential errors and stylistic issu
 `lux` comes with `luacheck`, a linter for Lua code, built-in. To run `luacheck` on your project, use the following command:
 
 ```sh
-lux check
+lx check
 ```
 
-<!--TODO: Add output of `lux check` command for our current code and see if there are any issues.-->
+<!--TODO: Add output of `lx check` command for our current code and see if there are any issues.-->
 
 ## Formatting with `stylua`
 
 `stylua` is a Lua code formatter that can automatically format your Lua code to a consistent style.
 It's highly recommended to use `stylua` to ensure that your code is consisent across the board.
 
 ```sh
-lux fmt
+lx fmt
 ```
 
-`lux fmt` will format all Lua files in your project to the style defined in
+`lx fmt` will format all Lua files in your project to the style defined in
 your
 [`.stylua.toml`](https://github.com/JohnnyMorganz/StyLua?tab=readme-ov-file#options)
 file, defined in the project root. Otherwise, it will use the default style.
@@ -44,8 +44,8 @@ project directory with the following content:
 ```sh
 #!/bin/sh
 
-lux check
-lux fmt
+lx check
+lx fmt
 ```
 
 Make sure to make the file executable:

docs/tutorial/08-publishing.md

@@ -64,7 +64,7 @@ type = "builtin"
 With the API key in hand, we can now publish our rock. Run the following command in your project directory:
 
 ```sh
-LUX_API_KEY=your-api-key lux upload
+LUX_API_KEY=your-api-key lx upload
 ```
 
 `lux` will now package your project and upload it to luarocks!