Release v18.4.0-beta.3

Releases
1

If you’re interested in testing out the GUI and giving feedback, please let me know!

Caveats

This is a pre-release, and is not as tested as a production build

  1. It may not always be easy and without manual steps to downgrade from a prerelease build to the last stable. It will be possible to upgrade automatically to the next stable after a prerelease.
  2. Prerelease builds are more likely to contain bugs or regressions. They are unlikely to lose data, but do be cautious when running the bleeding edge.
  3. Prerelease builds may contain functionality not yet in a production release. Please let us know what you think!

Download

If you’ve previously used our installer and have atuin-update in your path, you can use

atuin-update --prerelease

Otherwise, you can download prerelease binaries here: Release v18.4.0-beta.3 · atuinsh/atuin · GitHub

Or use the installer

curl --proto '=https' --tlsv1.2 -LsSf https://github.com/atuinsh/atuin/releases/download/v18.4.0-beta.3/atuin-installer.sh | sh

This will download a binary to ~/.atuin/bin/atuin, and add it to PATH. It will also install a binary called atuin-update, which will update users to the latest stable version by default. atuin-update --prerelease will update to the latest prerelease

Otherwise, the following command will work

cargo install --git https://github.com/atuinsh/atuin atuin --tag v18.4.0-beta.3

Testing

This is a smaller release, as I’d like to release 18.4.0 soon :slight_smile:

The main changes are

  1. Adjustments to the theming introduced previously. The default colours should be unaltered (and also allows for crossterm-serializable colours to be specified)
  2. A fix for store_failed, when users are not using the daemon. Previously, no history would be recorded :grimacing:
chore(release): prepare for release v18.4.0-beta.3 (#2305)
feat(gui): clean up home page, fix a few bugs (#2304)
fix(themes): Restore default theme, refactor (#2294)
feat(gui): background terminals and more (#2303)
chore(deps): bump highlight.js from 11.9.0 to 11.10.0 in /ui (#2298)
chore(deps): bump @tauri-apps/plugin-http in /ui (#2299)
chore(deps): bump @blocknote/mantine from 0.15.0 to 0.15.3 in /ui (#2300)
chore(deps-dev): bump tailwindcss from 3.4.4 to 3.4.6 in /ui (#2301)
chore(deps): bump docker/setup-buildx-action from 2 to 3 (#2295)
chore(deps): bump docker/build-push-action from 4 to 6 (#2296)
chore(deps): bump itertools from 0.12.1 to 0.13.0 (#2297)
chore(deps): bump zustand from 4.5.2 to 4.5.4 in /ui (#2302)
fix(history): logic for store_failed=false (#2284)
feat(tui): Fixed preview height option (#2286)
fix(gui): kill child on block stop (#2288)
3 Likes
2

@Adda The colors are still different; only the command text has changed back to white.

The blue is \e[38;5;12m. It was \e[38;5;4m before.
The green is \e[38;5;10m. It was \e[38;5;2m before.
The red is \e[38;5;9m. It was \e[38;5;1m before.

To summarize, it shifts from the first half of the 16 customizable colors to the second (brighter) one.

They were the Dark-prefixed version of crossterm::style::Color, but setting darkblue / darkgreen in the theme definition gives a different color. Also there seems to be no way to use the 16 colors in the theme definition (they are special because they are customizable via terminal settings).

Also, why is the current entry highlighted as an error? It feels wrong to me.

2 Likes
3

Aha. I am testing the prerelease now and you are right. The problem for me was the grey command text. I am happy with the white text again. However, I concur that the colours are indeed different. In my case, the brighter colours seem to better fit my environment. That may not be the case for others, though.

4

Other than the points discussed above, everything seems to be working as expected on my end.

5

Ah, thanks @lilydjwg - I see what is happening – crossterm and ratatui have different naming schemes, so Red<->DarkRed and LightRed<->Red. Had looked to see previously, but was looking at the wrong place so had missed that. Will PR a fix!

As a side-note, it should be possible to provide (since beta 3) any string in the theme map that crossterm’s serde_json support covers - examples here - by prefixing with an @. For instance, @ansi_(255) – however, I have an outstanding task to update the docs repo.

3 Likes
6

I didn’t know the @ansi_(n) syntax. I can use it to reproduce the exact same color as before, thanks!