u/Ra77a3l3

hello, i have installed ghostty with nix and for some reason the icon is this squared one instead of the one with the rounded corner. Why is that, and is there any way i can change it?

its still a simple plugin allowing for some basic customizations I would be really happy to see contributions to increse the possible customizations. One thing mising right now is diagnostics indicators, but for now there isn't an api that exposes diagnostic info to plugins. I doing a pr for it.

https://github.com/Ra77a3l3-jar/moka.hx

its a very simple file tree just like snacks explorer in neovim and i was able to add also icons

https://github.com/Ra77a3l3-jar/forest.hx

hi i made trail a plugin for browsing your recent projects. You can pick a project and it cds you straight into it, so the native file picker and everything else behaves exactly as if you'd cd into that folder yourself.

There are still somethings to polish, so i would appreciate any feedback and bug reports.

https://github.com/Ra77a3l3-jar/trail.hx

Does anyone have a fix for the pane becoming dimmed when making an ai request, while by default with my theme it does not look like this. This is my theme

---

background: "#0a0a0a"

accent: "#ff6b6b"

foreground: "#ffffff"

background_image:

path: /home/raffaele/.local/share/warp-terminal/themes/national-park-4k.jpg

opacity: 50

blur: 8

scale: 1.0

details: darker

terminal_colors:

normal:

black: "#2d2d2d"

red: "#ff6b6b"

green: "#4ec9b0"

yellow: "#ffc66d"

blue: "#4895ef"

magenta: "#f92672"

cyan: "#6be6c1"

white: "#e0e0e0"

bright:

black: "#555555"

red: "#ff8e8e"

green: "#74ee91"

yellow: "#ffe48b"

blue: "#82cfff"

magenta: "#ff79c6"

cyan: "#8be9fd"

white: "#ffffff"

name: vibrant-ink

hi, i switched from steel installed with cargo to installing it with nix. Now when i use the steel repl there is no problem but i get always this error when using forge. Im installing steel with nixpkgs unstable, does anyone have a fix for this?

hello im new to 3d printing and its my first time using a Prusa printer. When i use the slicer and i import an stl model from fusion its always offset by 20mm on the z axis. When i change the z to 0 i loose half of the model under the plane. In fusion everything looks fine the base is at 0 and the tip is at 40mm. In the slicer the world coor are x = 125mm, y = 105mm and z = 20mm while the object coordinates are x = 0, y = 0, z = 0. The printer is a Prusa i3 MK3S, i would be using generic PLA, the slicers version is 2.9.5 and i havent touched any settings. Any help would be appreciated thank you

replay allows you to record a sequence of commands, and wraps them into something you can rerun with variables, conditions, and step descriptions. So the same workflow works for staging, production, or your laptop just by changing a flag. Every step can have a short description so the workflow also serves as documentation for your team or future you.

Why not history, fzf,script. history and fzf are usefull to find a single command at the time. script records raw terminal output that you have to manually select to obtain somethng useful. A bash script you write once everything works while replay wants to create these scripts when you are still experimenting and iterating on a sequence of commands.

Claude helped for some refactors and Mistral was used mainly for some ai assisted coding.

[https://github.com/Ra77a3l3-jar/replaySh](https://github.com/Ra77a3l3-jar/replaySh)

[https://crates.io/crates/replaySh](https://crates.io/crates/replaySh)

replay allows you to record a sequence of commands, and wraps them into something you can rerun with variables, conditions, and step descriptions. So the same workflow works for staging, production, or your laptop just by changing a flag. Every step can have a short description so the workflow also serves as documentation for your team or future you.

Why not history, fzf,script. history and fzf are usefull to find a single command at the time. script records raw terminal output that you have to manually select to obtain somethng useful. A bash script you write once everything works while replay wants to create these scripts when you are still experimenting and iterating on a sequence of commands.

Claude helped for some refactors and Mistral was used mainly for some ai assisted coding.

[https://github.com/Ra77a3l3-jar/replaySh](https://github.com/Ra77a3l3-jar/replaySh)

[https://crates.io/crates/replaySh](https://crates.io/crates/replaySh)

I recently started building replaySh, a small CLI tool to record and replay terminal workflows.

GitHub: replaySh repository
Crate: replaySh on crates.io

Originally I made it to help me and my friends while preparing for a robotics competition create fast and reproducible workflows for testing and also to help some classmates that arent really comfortable with bash/fish scripting and just wanted something simple and quick to use.

With replaySh you basically start recording, use the terminal normally while testing/debugging/fixing something, and when you exit the recording it saves the workflow. Its not meant to replace bash or python scripts or compete with them, its more just a convinient way to keep track of workflows while experimenting and make reproducing fixes easier later.

Right now every command gets saved automatically, but one feature I really want to add soon is allowing after each comand execution the option to keep or discard the command from being added to the worklow. I think this would make workflows way cleaner especially during debugging where half the commands are failed attempts. Still an early project but its already been pretty useful to me.

Would really appreciate any suggestions.