u/AbdSheikho

This is my first Zig project!!!

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.

Since it's my first project, I'm looking for some feedback, or if someone can review my code. I want to learn more about Zig, but it's tiresome to feel I'm working alone. So any input is welcomed.

Another point is that, I use bash and I never used zsh or any other shell. And I think I could benefit some feedback regarding them, or if some use cases could generate bugs or unexpected output.

A list of things I still don't understand enough to have full confidence about:

• build.zig and the build system.
• fuzzy testing.

My goal in any project I work on is to reach the sudo make install point. Which means:

• the binary is built to the user $PATH.
• a man-page is created and available.

What should I do, apply, read, or learn to get the zig build system to this point?

Note: I should be able to reverse the installation process also.

Self-explanatory

I'm doing some io stuff where I'm doing the usual read/write from file. But I want to backup the file (with .backup postfix) before I do any read or write to it.

Is there a way to copy/backup the file based on the Io.File type?

Self-explanatory...

For me the Enter (Return) key is so far that I never use it, but I always see the Mod+Enter used throughout many configs and suggestions. Like really.. why?

I always associated the semicolon with commands, so it's the most logical key to launch a terminal.

Note: I know everyone can do what they like, but that's why it's a discussion, and I'll be glad to hear your thoughts.

So... I'm diving into st terminal to have a my own custom "alacritty with ligatures, image rendering, and vim bindings".

Question #1... What are some of the must have patches? Scrollback for sure.

Question #2... Is there any patch that is redundant now? Meaning st-0.9.3 cover it.

Question #3... What is the most annoying patch that conflicts each time it gets applied? I'm looking at kitty protocol patch and it looks huge, so I'm guessing it will cause conflict for sure.

With the 0.16 release I thought that I should restart my Ziglings track, since the first time went without me recording/documenting what I learnt.

So the first thoughts that came to my mind is... I need to 1) clone/fork Ziglings 2) solve the exercises 3) push my solutions to my dedicated repo.

I opened github to initial an empty repo, but then I realised that I'll be providing Ziglings to github in that why.

Is that ethical? What should I do? Or am I overthinking stuff here, and it's irrelevant?