yamafaktory

In order to address several comments I got here, the readme and landing pages have been reworked. I can't change the title here but read as: An opinionated, zero-config status line and history picker for fish, bash and zsh, written in Zig. Also tackled several issues mentioned in different comments (including the install to ~/.local/bin).

Actually regarding the Nerd Font point, you might be using a terminal supporting it out the box. I'll adjust the readme and the landing page accordingly.

Thanks for the feedback :).

I'll try to make that a constructive argument and assume that the project shouldn't use the word "prompt".

Indeed, this is very opinionated (it's mentioned in the repo / landing page but that was too long for the ShowHN title).

If you see the glyphs correctly, you're very likely having Nerd Font installed. If not in git, it will show https://yamafaktory.github.io/whetuu/#modules. And to edit an entry in the list, hit tab :).

Thanks for the hint.

The XDG Base Directory spec covers config/data/cache/state, it does not define where executables go. Whetuu history & cache are both compliant as both go to respectively ~/.local/share/whetuu/ ($XDG_DATA_HOME) & ~/.cache/whetuu/ ($XDG_CACHE_HOME).Atuin, cargo and many other tools are doing the same. By the way, Atuin also rebinds the up arrow.

Fixed :)

I fixed it - you can go up and edit the last failing one. As soon as another cmd succeeds, it will not longer appear in the list and it's never stored into the tool history.

It already does. The releases page has prebuilt binaries for four targets plus a SHA256SUMS file. You can download the tarball straight from GitHub over TLS, verify it against the checksums, and run it. No script involved.

we are not talking about the same thing. I'm talking about ~/.whetuu - the tool doesn't hijack the shell history at all. You can rm -rf the store and your shell history is intact.

Why not, plenty of tools - atuin included - are doing that.

You're right. Whetuu is actually correct in ASCII. I did study study some Te reo Māori a while ago. Will fix.

Thanks for the feedback! You can run `whetuu paths` and will get that, I'll fix the readme.

Hey folks. I made this tool that I now use on a daily basis. My goal was to have a zero-configuration cross-shell prompt written in Zig (v0.17) that replaces tools like atuin & starship at the same time. This has been implemented using Claude and should be fast. It should also work on a Mac - though I can't test it myself.

Hey folks. I made this tool that I now use on a daily basis. My goal was to have a zero-configuration cross-shell prompt written in Zig (v0.17) that replaces tools like atuin & starship at the same time. This has been implemented using Claude and should be fast. It should also work on a Mac - though I can't test it myself.

I'm sorry if it was unclear. My comment was just a validation of your assertion. It does use Claude - or any openai compatible LLM - to perform the extraction.

Well, I can understand your frustration, but this is basically a pipeline that takes some code written by an LLM and attempts to prove its correctness using the Lean 4 theorem prover.

Author here - I'm not using pointers in my implementation but indexes as you mentioned.

It was initially called HyperZig but after talking with some "ziguanas", using the exact word "hypergraph" in the same felt more accurate.

Not really - yet. I made that as an exercise to learn some Zig and to see how fast/efficient it might be.

I'm honestly not sure if I can answer that question. There's plenty of applications for hypergraphs (e.g. https://www.sciencedirect.com/science/article/pii/S209580992...), so I'd say why not?

Internally both the hyperedges and the vertices are stored as an AutoArrayHashmap with the associated data and the relations ( https://github.com/yamafaktory/hypergraphz/blob/9f87e705afd7...). Then the implementation diverge since a given hyperedge can hold zero to n vertices, with self-loops (ArrayList). For vertices, we just need to keep track of the hyperedges (AutoArrayHashmap).

Thanks for the feedback! Developing/prototyping is a very pleasant experience in Zig compared to Rust. It's obviously a different approach and some might find the tooling less mature but I quickly realized that the build system (as per 0.13.0) is very solid. You can build the docs, run the tests, etc. I'm a Neovim user and honestly the LSP (ZLS) is stable and you can additionally get the compilation errors (you need to create a check step in your build file). In tests, using with the testing allocator to catch memory leaks guides you while prototyping.

Thanks!

What triggers the initial willingness to implement something with hypergraphs was indeed the Wolfram physics project! https://github.com/yamafaktory/hypergraph/discussions/11#dis...

Social media for example.

Maybe companies like Facebook modeled their "social graph" with hypergraphs?

Thanks a ton for the feedback!

You're right maybe the wording is wrong: query more than manipulate. By the way, querying like jq might be an interesting new feature. Don't know exactly in which direction it should go / what it should do / how exactly it should look like (grammar)

N.B.: I have another project called jql which is actually a simpler - and faster - jq made with Rust https://github.com/yamafaktory/jql