quick recap if you missed v0.1.0: undo journals your mv/cp/rm/mkdir/etc and lets you reverse them, deleted stuff goes to the trash instead of getting nuked so even rm is recoverable.

what's new in v0.1.1:

- undo search <name> - find journal entries by filename or path, useful once your history gets long and you can't remember which command touched what

- undo log - activity view, shows when something ran, which command, and which files it touched. cleaner than digging through undo history

- undo repair - checks the journal db and rebuilds it if it's corrupted, backs up the old one first. your trash is never touched by this

- switched the license to MIT starting this version (v0.1.0 stays GPLv3)

next up:

- v0.1.2: a config file + TUI for settings, and a prune command that cleans up old journal entries. it's hybrid by default, keeps your trashed files around unless you explicitly opt into emptying the trash too

- v0.1.3: a small plugin system so you can alias your own command names to the built-ins, plus self-update so you don't have to manually grab new releases

grab it: https://github.com/nvrmnd-png/undo/releases/tag/v0.1.1

thanks again to everyone who gave feedback on the last post, some of this came directly from your suggestions

A few days ago I shared EasyAlias here and got some really useful feedback.

Since then I added Linux support and it’s now also available through Homebrew.

The idea is simple: instead of manually editing .zshrc, PowerShell profiles or other config files, you can create and manage aliases through a small desktop UI.

It’s open source and I’d love to hear what you think or what features you’d like to see.

GitHub: https://github.com/hannesgnann-hub/easyalias

rm -rf'd the wrong folder a while back, so I built this instead of learning to be careful. undo hooks into mv, cp, rm, mkdir, rmdir, chmod, chown, ln and rename through a shell function, logs what happened to sqlite, and rm doesn't actually delete anything, it just moves stuff to your trash. run undo and it puts back whatever you just broke.

rust, has a tui for browsing history if you don't wanna guess, zsh/bash/fish all work.

github.com/nvrmnd-png/undo
Happy to answer questions, still pretty early so bug reports are welcome too.

Visualization support (bash)

Try it here https://8gwifi.org/online-bash-compiler/

Tracers

CodeTracer, Array1DTracer, MapTracer, CallStackTracer, LogTracer

Supported

• Variables & scope — x=5, local n=1, declare -i c, readonly MAX, export ENV split into globals vs current-frame locals panels; locals clear when the function returns; integer/readonly/exported shown as badges
• Arrays — arr=(a b c), arr+=(x), arr[i]=v build, grow, index, sort in place
• Associative arrays (maps) — declare -A m, m[key]=val, ((m[$w]++)) counting, grouping, config maps
• Loops — for x in ..., for ((i=0;i<n;i++)), while, until line highlights each iteration; loop var + body vars update per pass
• Functions & recursion — name() { ... }, local v=..., direct recursive calls call stack push/pop per call
• Positional parameters — $1..$9, $#, $@ (for x in "$@") script args (viz `args` field) populate $1..$@ at top level; a function's args shown per call (recursion shows each frame); $#=0 when none
• Exit status ($?) — grep x file, (( n > 10 )), ((count++)) panel appears on first non-zero; tracks failing commands and false (( ))/[[ ]] tests (incl. the classic ((i++)) from 0 returning 1)
• Output — echo, printf shown next to the command that printed it

Not supported yet

• Pipelines a|b, command substitution $(...), subshells ( ), background & — Each forks a child shell whose variables can't report back; only the main shell is traced. So recursion written as v=$(f) won't show — call the function directly. Use instead: Planned Track B shell-model visualizer (process tree, redirection, expansion order)
• Parameter/string expansion (${x#pre}, ${x/a/b}, ${#x}, ${x:-def}), $PIPESTATUS, redirection & FD rewiring, traps / set -e flow — Track A shows the resulting variable state, not the expansion/process/IO model; variable reads aren't highlighted (bash has no embeddable source rewriter) Use instead: Track B

I don't use a plugin manager and I lazy load pretty much all the tools I use!
I only source those 7 plugins and I can't figure why my right here:

zsh-users/zsh-completions

mattmc3/ez-compinit

aloxaf/fzf-tab

zsh-users/zsh-autosuggestions

zsh-users/zsh-history-substring-search

houssamouhra/colored-man-pages

zdharma-continuum/fast-syntax-highlighting

But, my bench is still slow, here:

creates_tty=0
has_compsys=1
has_syntax_highlighting=1
has_autosuggestions=1
has_git_prompt=1
first_prompt_lag_ms=512.604
first_command_lag_ms=545.887
command_lag_ms=110.416
input_lag_ms=15.662
exit_time_ms=329.175

any suggestions I should do to make first_prompt_lag_ms or first_command_lag_ms lower?
here is my zsh dotfiles: https://github.com/houssamouhra/dotfiles/tree/master/zsh/.config/zsh

EDIT: I managed to optimize the bench to something like this by keeping the same plugins, and am very proud of my zsh config

creates_tty=0
has_compsys=1
has_syntax_highlighting=0
has_autosuggestions=0
has_git_prompt=1
first_prompt_lag_ms=180.828
first_command_lag_ms=181.454
command_lag_ms=54.614
input_lag_ms=13.955
exit_time_ms=121.106

Hello everyone,

I am never to command lines and zsh overall. I have been working on getting better with c++, and zsh almost daily trying new things, finding new ways to do things, and reading as well. I'm not sure if this is the right place for this question, but I hope it is. The issue I have been having is I use micro text editor, and found out that I can make shortcuts using bindings.json, so I have been trying to set it up for being able to replicate some excel short cuts like ctrl-; for date ctrl-shift-; for time. Well, I have tried everyway to do it from capitalizations to writing out semi-colon to instead of - using +. I keep end up in the same spot of command line telling me it's not a bindable event. I am not sure if maybe I just don't fully understand how to do it correctly(which is very plausible) or I am missing maybe a key thing? the way I did it was micro ~/.config/micro/bindings.json The llast attempt I made was able to open without saying it's not a bindable event. However, it doesn't do anything when I attempt to do it inside micro example.txt the way I set it up within bindings.json is:

{

"Ctrl-;": "command:insert sh -c \\"date +%m/%d/%Y)\\"",

"Ctrl-Shift-;": "command:insert sh -c \\"date +%H:%M:%S)\\""

}

Thank you for the help! I'm still learning, so I appreciate help and advice!

I use a script as VISUAL like export VISUAL=/bin/nvim which is my own script that calls the real nvim with extra args. It works for EDITOR but not VISUAL.

If I type something in the zsh prompt and run edit-command-line with a keyboard shortcut it opens the VISUAL editor but there's an error in nvim E471: Argument required: normal!.

The arguments passed to the script are -c normal! 8go -- /tmp/zshiBXqrc.zsh. 8 is the number of letters I typed on the prompt. Do you know what I need to change in export VISUAL or the /bin/nvim script?

Hey everyone! 👋

I wanted to share a small, open-source Zsh plugin I’ve been working on lately: Git Commit Prefixer.

If you try to follow the Conventional Commits standard (or just like having a clean, semantic, and visual Git history), manually typing out prefixes and searching for emojis for every commit can get a bit tedious. To speed up this workflow, I created this super lightweight plugin.

✨ What exactly does it do?

It allows you to automatically add predefined prefixes and (optional) icons to your Git commit messages, right from your terminal.

Usage example: Instead of typing all of this manually: git commit -m "✨ [feat]: add dark mode toggle"

You just use the command (I highly recommend setting up a short alias for it): git-commit-prefixer feat "add dark mode toggle" (This generates the exact same result as above).

🛠️ Main Features

• Prefix styles: Choose between brackets style ([fix]:, [feat]:) or labels style (Fix:, Feature:).
• Icon themes: Use classic emojis (🐛, ✨, 🏗️), a minimal set (✖, ✦, ▲), or disable them entirely for a cleaner look.
• Fully configurable: Everything can be tweaked easily by changing a couple of variables in the icons.conf file.
• Easy integration: Installs in seconds if you use Oh My Zsh by cloning the repo into your custom plugins folder.

📦 Repository & Installation

You can check out the source code, installation instructions, and a demo GIF here: 👉 GitHub Repo: dvigo/git-commit-prefixer

🔧 Roadmap / Next Steps

I am currently planning to add:

• Interactive commit type selection using fzf (so you don't even have to remember the types).
• A CLI command to switch styles/themes without manually editing the config file.
• Support for 100% user-defined custom commit types.

I’d love to know what you think, if you find it useful for your daily workflow, or if there is any feature you feel is missing. Feedback, suggestions, or Pull Requests are super welcome! 😊

Hope it saves you a few seconds of typing today!

Looking for a more retro look. Thanks

Part of my workflow is to use fzf to search my command history. And I always wanted to have a cli-tool to clean duplicate commands from my history (I don't know if such a tool already exists, I never searched). I could've tried to write that tool in any other language (Python, bash, C#) but the task wasn't interesting, and I wanted it to be a proper bin.

When I started learning Zig, it seemed a proper starting point to make a file manipulation project. So, histclean was born. A cli-tool to clean command history to its latest unique commands.

Since I only use bash and I never used zsh or any other shell. I think I can benefit some feedback regarding them, or if some use cases could generate bugs or unexpected output.

Happy to hear any feedback.

EDIT: SOLVED:
the issue i had is a feature called "Transient Prompt". it can be disabled in the powerlevel10k configure tool, simply by running:
p10k configure
and clicking through the options. i'm sure you could find it elsewhere, but this is the easiest way imo, and worked for me.

----------------------------------------------------------------------------------------------------------------------------------------

Hello, i'm somewhat new to linux and zsh. I use Manjaro. After (presumably) an update, the zsh command line changed, and after executing a command, it doesn't show the working directory (picture 1) as it used to (picture 2). I can't find any settings or mention of this in the documentation (probably don't know the right keyword tbh), any ideas what i can change to get back to pic2?

Now it's really annoying, because when i execute a command, it both jumps a long way to the left, and also if i cd a lot, i don't see what directory the command was run from.

.zshrc: https://pastebin.com/xDSUDyGE
manjaro-zsh-config: https://pastebin.com/5rFQujng
manjaro-zsh-prompt: https://pastebin.com/1yA75LLY
powerlevel10k.zsh-theme: https://pastebin.com/uzaupHGV

if anyone has ideas how to fix it, i'd be very grateful. thank you!

I use iterm2 on Mac with zsh today and I have evaluated ghosttly also.

I like starship for my prompt but I also liked oh-my-zsh in the past.

I have the same problem with iterm2 and ghosttly. Tab title is bad and the font is too small.

In iterm I am able to set the title to exactly PWD regardless if I e.g. start Claude code. In ghost it is not possible. I also like the color options in iterm2 much more. I don’t want pwd, just the current directory, but that seem impossible.

Iterm has some advanced settings that increases the font, but that breaks pwd as title.

Did anyone figure out how to enjoy large font tab title that is just the directory? And also hopefully possible to set the tab color across the whole tab

I got tired of this cycle:

• Figure out some annoying kubectl/docker command
• Use it successfully
• Forget it exists
• Spend 10 minutes digging through history trying to find it again

Shell history records everything, but after a while it's just a giant list of commands with no context.

I wanted to answer questions like:

• What commands do we actually use in this repo?
• Which ones worked?
• Which commands keep coming up over time?

So I built Yore.

A few things it does:

• yore here shows commands used in the current repository
• commands are ranked by frequency + recency instead of raw history order
• yore here --ok filters to commands that previously succeeded
• commands can be saved as reusable recipes

The part I haven't seen elsewhere is that project recipes live in a .yorefile that can be committed to Git.

That means useful commands can live with the repository instead of somebody's shell history. Clone the repo and you get the project's command knowledge too.

Repo: https://github.com/Dev-Bilaspure/yore

Curious how others handle this today.

PowerLens is a lightweight Oh-My-Zsh plugin that embeds live macOS system metrics (power, battery, CPU, temperature, fan speed, memory, network) directly
  into your zsh RPROMPT.

  A single Go daemon collects all data every 2 seconds; the prompt reads a cached JSON file on each precmd — adding less than 5ms regardless of how many
  terminal windows you have open. 

  Key features:
  - 7 metrics with per-value color thresholds
  - Singleton daemon (1 process shared across N terminals)
  - Crash recovery (auto-restarts if data is stale)
  - SSH-aware (graceful degradation in remote shells)
  - Native macOS APIs (IOKit/SMC), no sudo needed
  - Apple Silicon and Intel, macOS 12+

  GitHub: https://github.com/luyangkk/powerlens
  Release: https://github.com/luyangkk/powerlens/releases/tag/v1.0.0

I've been experimenting with AI-assisted debugging on larger codebases and kept running into the same problem:

The model wasn't wrong because it was bad at reasoning.

It was wrong because it didn't have enough repository context.

Most AI workflows either:

• paste snippets manually
• rely on repository indexing
• dump huge amounts of code into the prompt

I wanted something more explicit.

So I built grab, a terminal tool that progressively accumulates repository context using ripgrep, function indexing, exact range extraction, and clipboard/tmux integration.

The workflow is:

1. Search for relevant symbols/functions.
2. Build a lightweight function index.
3. Let the AI request exact code ranges.
4. Accumulate context incrementally.
5. Keep expanding only the parts of the repository that matter.

Instead of indexing the entire repo, the AI acquires context as needed.

The idea is:

"You are not copying results. You are exporting context."

Repo:
https://github.com/johnsellin93/grab

I'm curious whether others have run into the same context-acquisition problem when debugging with AI tools.