HNHacker News
TopNewBestAskShowJobs

ellieh

1,103 karma · joined December 17, 2021

https://ellie.wtf

building atuin.sh

ellie@elliehuxtable.com

submissionscomments
ellieh··on Tell HN: YC companies scrape GitHub activity, send spam emails to users
this happens to me so often that I wonder if it's something YC suggest people do
ellieh··on Zed editor switching graphics lib from blade to wgpu
gpui existing in the first place is a result of them raising VC
ellieh··on Asahi Linux with Sway on the MacBook Air M2 (2024)
> In other words: get an actually Linux supported laptop for Linux.

40% battery for 4hrs of real work is better than pretty much any linux supported laptop I've ever used

ellieh··on Atuin’s New Runbook Execution Engine
The main difference otherwise is that Atuin stores much more data + syncs it

We shelled out to fzf in the very early days, but found the initial indexing to be a bit slower + add latency vs SQLite

ellieh··on Atuin’s New Runbook Execution Engine
Let me know if there’s anything I can help with!
ellieh··on Atuin’s New Runbook Execution Engine
You’re very welcome! Glad it’s working well for you
ellieh··on Atuin’s New Runbook Execution Engine
One of the main things we’re aiming to do here is make these manual processes much less manual! I’m a big believer in automating things gradually, which runbooks enable
ellieh··on Atuin’s New Runbook Execution Engine
Not just yet! We support a bunch of features that don’t fit into markdown very well.

We will have better markdown support soon

ellieh··on Atuin’s New Runbook Execution Engine
Very happy to hear you find it so useful! Please do let me know if there’s anything we can do to make it better for you
ellieh··on The terminal of the future
> It could be interesting to see if it would be enough to add shell history as a completion source.

Atuin runbooks (mentioned in the article) do this! Pretty much anywhere we allow users to start typing a shell command we feed shell history into the editor

ellieh··on CRDTs: Convergence without coordination
this is so cool! really excited to see where it goes
ellieh··on Atuin desktop: Runbooks that run
Yes! Working on that soon, the same runtime can be used elsewhere. Wanted to start with the GUI so we could really make it what we want, but up next

1. TUI for interactive terminal runbooks

2. CLI for hands-off execution, CI, etc

ellieh··on Atuin desktop: Runbooks that run
Thanks for sharing! Maintainer here, lmk if you have any questions <3
ellieh··on Atuin Desktop: Runbooks That Run – Now Open Source
we could absolutely plug it into the codemirror linter! thanks for mentioning

issue: https://github.com/atuinsh/desktop/issues/47

ellieh··on Atuin Desktop: Runbooks That Run – Now Open Source
absolutely!

we already support execution of script + terminal blocks over SSH, but want much tighter integration. Parallel execution is certainly a part of that too. anything else you'd want to see?

ellieh··on Atuin Desktop: Runbooks That Run – Now Open Source
I agree! We're definitely not trying to avoid them as users haha, I can certainly see how it would be useful. There's so much automation that just can't fit into a strict schema, and always needs a human or customization for 10% of it

We're aiming to be flexible enough, so that if you can do it in a terminal then you can _also_ do it with a runbook

ellieh··on Atuin Desktop: Runbooks That Run – Now Open Source
It's aimed at replacing developer docs realistically - anything where you're explaining how to run or query things.

BUT it does also make a nice environment for rich text, with markdown support, so can easily replace internal docs in general

ellieh··on Atuin Desktop: Runbooks That Run – Now Open Source
big fan <3
ellieh··on Atuin Desktop: Runbooks That Run – Now Open Source
copy-paste of another comment but I think it answers everything here! The only addition I'll add is that if you copy-paste into another Atuin instance, the richness is preserved. If you copy paste to anything else, it'll be pasted as markdown.

---

The runbook files are just YAML (for now). They're more verbose than I'd like, but do convey a lot of information - both rich text and executable.

There's an example here: https://github.com/atuinsh/desktop/blob/8ebed35d7efe68a92363...

I'm aware this isn't ideal, and longer term we want something that looks much more like markdown. A key requirement for us here is that it's easy + convenient to type - just like normal markdown - so putting everything as a code block annotation isn't ideal.

The current sketch of what that could be looks like this: https://forum.atuin.sh/t/desktop-devlog-markdown-vim-local-f...

Would love to know if you have any thoughts!

ellieh··on Atuin Desktop: Runbooks That Run – Now Open Source
The runbook files are just YAML (for now). They're more verbose than I'd like, but do convey a lot of information - both rich text and executable.

There's an example here: https://github.com/atuinsh/desktop/blob/8ebed35d7efe68a92363...

I'm aware this isn't ideal, and longer term we want something that looks much more like markdown. A key requirement for us here is that it's easy + convenient to type - just like normal markdown - so putting everything as a code block annotation isn't ideal.

The current sketch of what that could be looks like this: https://forum.atuin.sh/t/desktop-devlog-markdown-vim-local-f...

Would love to know if you have any thoughts!

ellieh··on Atuin Desktop: Runbooks That Run – Now Open Source
Mostly - we have ssh blocks that cause the subsequent shell and terminals blocks to run remotely

We don’t yet support full remote execution, but should do soon!

ellieh··on Atuin Desktop: Runbooks That Run – Now Open Source
Huge fan of gradual automation

It’s definitely baked into the approach here. You could just write a bullet point list of what needs doing. Then maybe sprinkle some blocks on top so the user can do things faster. Then in the end, work towards the whole thing being automated

No all or nothing, no YAML needed ;)

ellieh··on Atuin Desktop: Runbooks That Run – Now Open Source
Yes exactly! I have so many systems both personally + professionally, and Desktop has made it so much easier to maintain and work with them all

Let us know if you try it and have any feedback or questions at all

ellieh··on Atuin Desktop: Runbooks That Run – Now Open Source
Hello! Atuin maintainer here

Happy to answer any questions

ellieh··on Atuin Desktop: Runbooks That Run – Now Open Source
(Hi, author here!)

I can’t guarantee we never will, but I am only interested in such things if they are genuinely useful

If we won’t use it internally, and no significant % of users will, then it won’t happen

ellieh··on Atuin – Magical Shell History
I don't mean to be rude but this has been the case since the project first started in 2021. You have always had to sign in to sync anything at all

It's always been opt-in, or "opt-out by default".

ellieh··on Starship: A minimal, fast, and customizable prompt for any shell
Atuin was until it was bumped to page 2/3 and beyond :(
ellieh··on Atuin – Magical Shell History
It is configurable!

And also the default is now to use 40 lines, not the alt screen (has its own drawbacks)

You can set “inline_height”

https://docs.atuin.sh/guide/basic-usage/#inline-window

ellieh··on Atuin – Magical Shell History
Atuin stores much more context than ctrl-r does - exit codes, command duration and directory, etc

Also has functions for filtering command search by directory

Being backed by SQLite tends to mean your history is more durable + is properly saved across shells too

ellieh··on Atuin – Magical Shell History
The main thing would be opt-in syncing, and I think we might store a little more context than fish does in their SQLite!

Otherwise consistency is nice if you use a few setups

← PreviousPage 2 of 5Next →