Hacker Newsnew | past | comments | ask | show | jobs | submit | seedie's commentslogin

From the atuin.sh website

> Sync your shell history to all of your machines

I think of my shell history as very machine specific. Can you give some insights on how you benefit from history sync? If you use it.


That feature is entirely optional and disabled by default. Atuin stores your shell history locally in a sqlite db regardless of whether you choose to sync it. I thought fzf was fast, but atuin makes it look slow by comparison.


Same, I find shared history not very useful.

However what I do find useful is eternal history. It's doable with some .bashrc hacks, and slow because it's file based on every command, but:

- never delete history

- associate history with a session token

- set separate tokens in each screen, tmux, whatever session

- sort such that backward search (ctrl-R) hits current session history first, and the rest second

Like half my corporate brain is in a 11M history file at this point, going back years.

What I would love is to integrate this into the shell better so it's using sqlite or similar so it doesn't feel "sluggish." But even now the pain is worth the prize.


I just want to give a perspective of someone that uses the 'eternal history' in bash per Eli Bandersky [1] and reluctance to use something like atuin (without/ignoring shared history).

First, as for speed and responsiveness, if there is a degradation, it is imperceptible to me. I wouldn't have a clue that my interactive shell is slowing down because it is logging a command to ~/.persistent_history.

My persistent_history is 4MB and has been migrated from machine to machine as I've upgraded, it's never felt slow to edit with (neo)vim or search with system supplied grep.

Eli's way of doing it also includes the timestamps for all commands, so it's easy to trace back when I had run the command, and duplicates are suppressed. In fact my longest persistent_history goes back to 2019-07-04, so I've been using it for quite some time now.

But the larger point I wanted to make is that I wouldn't feel comfortable switching this, in my opinion, quite efficient setup to displace it with an sqlite database. That would require a special tool to drill through the history and search rendering simple unix utilities useless. As Eli suggested, if your history gets too big, simply rotate the file and carry on. I have the alias phgrep to grep ~/.persistent_history, but I can easily have another alias to grep ~/.persistent_history*.

[1]: https://eli.thegreenplace.net/2013/06/11/keeping-persistent-...


You don't have to setup shared history with Atuin if you don't want to and that's what's holding you back. Otherwise it hits the rest of your requirements. Just don't hesitate to change from the default config.


1. work on a project on host_foo in /home/user/src/myproject

2. clone it on host_bar in /home/user/src/myproject

If you set filter_mode = "directory", you can recall project specific commands from host_foo for use on host_bar even though you're working on different machines and the search space won't be cluttered with project specific commands for other projects.


I sync Atuin to my home server but I also configure it to be host specific by default.


Great advice, but don't treat it as a checklist. If you like to go to the gym, do it. If not don't do it, leave alone every day.

Your focus should not be in improving yourself and being the best you can be. It's about getting to know yourself better.

What is it that you enjoy. And if you don't know, now's the time to find out. Maybe it's going to the gym, maybe it's finding a great breakfast place. Sitting there, having breakfast, being around other people.

Finding activities that you enjoy doing outdoors, bonus points.

You've already done the first step in asking for advice. Even though it might sound neglectible, that's a great achievement. So many people suffer from depression and have a hard time to take this first step. Congratulations!

Get out there try things, learn who you are. Maybe there's this thing that you always wanted to do places you always wanted to see. Now is the best time to do it. And if there's no such thing, you've been given a great list of things to try.

Best luck to you in this new phase of life!


Just because OP takes medication after a break up, doesn't mean it's a "normal" life situation for them. They could have suffered from depression before, it's not even clear if they started only after medication. The break up could also bring up some childhood trauma, like the loss of a loved one. What seems to be a normal life situation to someone might not be a normal life situation for someone else. I agree though that if no depression is diagnosed it's a bad idea to take antidepressants.


You gotta love the "humor" of Gemini. On Fast it told me:

> Drive. Unless you plan on pushing the car there


Imo they explain pretty well what they are trying to achieve with SIMA and Genie in the Google Deepmind Podcast[1]. They see it as the way to get to AGI by letting AI agents learn for themselves in simulated worlds. Kind of like how they let AlphaGo train for Go in an enormous amount of simulated games.

[1] https://youtu.be/n5x6yXDj0uo


That makes even less sense, because an AI agent cannot learn effectively from a hallucinated world without internal consistency guarantees. It's an even stronger case for leveraging standard game engines instead.


"I need to go to the kitchen, but the door is closed. Easy. I'll turn around and wait for 60 seconds." -AI agent trained in this kind of world


If that's the goal, the technology for how these agents "learn" would be the most interesting one, even more than the demos in the link.

LLMs can barely remember the coding style I keep asking it to stick to despite numerous prompts, stuffing that guideline into my (whatever is the newest flavour of product-specific markdown file). They keep expanding the context window to work around that problem.

If they have something for long-term learning and growth that can help AI agents, they should be leveraging it for competitive advantage.


You can still pipe bat output as it falls back to unformated output when it detects a non-interactive terminal. https://github.com/sharkdp/bat?tab=readme-ov-file#file-conca...


Love the simplicity of your to to-do list syntax highlighter in comparison to todo.txt. That's more how my brain works, as simple as possible. Especially your take on the due date vs. date when you plan to do it. Will definitely try it out.


What they mean is that on a standard german keyboard layout to type []{}~ one would press

  [ Alt Gr-8
  ] Alt Gr-9
  { Alt Gr 7
  } Alt Gr 0
  ~ Alt Gr +
While on an Apple keyboard you use

  [ ⌥-5
  ] ⌥-6
  { ⌥-8
  } ⌥-9
  ~ ⌥-n


I just tested the German – Standard layout on a Mac, it's the first one you indicate. Apple calls right-⌥ the Compose key, not AltGr, but works the same way, other than being transposed with the Command key from the familiar Windows style of layout.

There's also a keyboard layout just called German, maybe that one works the way you refer to? But surely it's not too much to ask that someone select the keyboard style they're accustomed to using?


Don’t confuse “standard” with “what IBM and Microsoft implemented in the 80s”.


Congrats on the launch. I'll take a closer look soon and only played around a bit.

Would be great if you could extend the documentation.

If you're not open sourcing the app, what about at least open sourcing the documentation?

One thing I'd like to extend is on https://www.grafychat.com/d/docs/intro

3. Configure Ollama server to make sure it allows connection from grafychat.

That's not very helpful. Something along the line Set the environment variable OLLAMA_ORIGINS to "https://www.grafychat.com" and rerun "ollama serve". Use your custom host if your using the self-host option.

  ```sh
  OLAMA_ORIGINS="https://www.grafychat.com" ollama serve
  ```
Is not that much more text but makes it way easier for people to go and try out your app with ollama.


Thanks for the feedback!

Open sourcing documentation is an interesting idea.

> Something along the line Set the environment variable OLLAMA_ORIGINS

I'll test it out and update the docs.


What I usually do for Open Source, instead of browsing the website, check on GitHub. https://github.com/penpot/penpot

The license on GitHub is featured prominently as MPL-2.0


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: