luxe update and /update, editable question answers, and a version bump owed once per release
- luxe update and /update update Luxe with the command for however it was installed (cargo or Homebrew), run one program at a time with the terminal attached, then check that the luxe on PATH is the new version. Luxe never downloads or replaces its own binary. The start screen says "Update available · /update". - A question's typed answer edits at its caret: arrows, word jumps, Home, End and Delete work, and up and down move through a wrapped answer before leaving it. - The version check owes a bump once per release: the version on main is the next release, and only a released one (a v-tag) has to move. - Dependency updates arrive through the sync, so Dependabot and the weekly jobs no longer run here.
This commit is contained in:
@@ -139,17 +139,33 @@ This is local to your machine and on by default. Outside herdr nothing is sent.
|
||||
{ "herdr": false }
|
||||
```
|
||||
|
||||
### Update notice
|
||||
### Updates
|
||||
|
||||
Once a day, Luxe checks whether a newer release exists and says so on the start screen, with the
|
||||
command to update. Luxe never updates itself. The check sends nothing about you or your machine; the
|
||||
comparison happens locally.
|
||||
Once a day, Luxe checks whether a newer release exists, and when one does the start screen says
|
||||
*Update available · /update*. The check sends nothing about you or your machine; the comparison
|
||||
happens locally.
|
||||
|
||||
`/update`, or `luxe update` in a shell, updates Luxe with the command for however you installed
|
||||
it, showing each one before it runs:
|
||||
|
||||
| Installed with | `luxe update` runs |
|
||||
| --- | --- |
|
||||
| Cargo | `cargo install --locked --force luxe-cli` |
|
||||
| Homebrew | `brew update`, then `brew upgrade luxe` |
|
||||
|
||||
Luxe never downloads or replaces its own program; the package manager that installed it does. A
|
||||
copy your system's package manager owns is left to it, and a downloaded one points you at the
|
||||
releases page. On Windows, Luxe can't be replaced while it runs, so it prints the command to run
|
||||
once it has exited. Afterwards it checks that the `luxe` your shell finds is the new version, and
|
||||
says so if another copy earlier on your `PATH` is in the way. `luxe update --check` only reports.
|
||||
|
||||
To stop the daily check:
|
||||
|
||||
```json title="~/.config/luxe/config.json"
|
||||
{ "update": { "check": false } }
|
||||
```
|
||||
|
||||
`LUXE_UPDATE_CHECK=0` turns it off as well.
|
||||
`LUXE_UPDATE_CHECK=0` turns it off as well. `luxe update` still checks when you run it.
|
||||
|
||||
### Launchers
|
||||
|
||||
|
||||
Reference in New Issue
Block a user