Celebrating 0.16.0, I was playing around the master branch for a couple of days and I wrote a little hex viewer with colors. Intro article with screenshots and the repo. It is a pretty small project with no dependencies.
I hope y’all like it.
Celebrating 0.16.0, I was playing around the master branch for a couple of days and I wrote a little hex viewer with colors. Intro article with screenshots and the repo. It is a pretty small project with no dependencies.
I hope y’all like it.
Very cool!
So what do these colors signify? Or is this just a pretty rainbow?
They signify the whimsy of the author :3
First link in the article: your hex editor should color-code bytes
This is genius ! I want this in my vscode hex viewer now !
I like it. Is there logic to the name 3sl? Trying to think how I’d remember I had it.
Arabic word for Honey.
Hey. I made a few updates to this to make it even better.
You can view the changelog here: https://git.sr.ht/~asibahi/3sl/tree/v0.1.4/item/CHANGELOG.md
The biggest change is the --windows or -w flag, where you can segment the file into different sections, skipping some if needed. Here is a simple screenshot example:
There is also some --range flag to get only a section of the file, and a small way to adjust color choices (customizable via environment flags). You can find all the necessary info with --help.
Yo I added —base64 flag to get the binary out in base64. For when you want to share the binary in base64 .
@lalinsky no reason to add the LLM tag
I’m sorry, I was going by the commit mentioning fixes by gemini.
Fair enough. I just threw the files at web Gemini to see if it found any bugs. No agents tho.
There’s no -Dcpu=baseline option when building the app.
You should probably use standardOptimizeOption and standardTargetOptions.
const mod = b.createModule(.{
.root_source_file = b.path("src/main.zig"),
.target = b.graph.host, // <<<<<<<<<<<<<<<<<<<<<<<<<<
.optimize = switch (b.release_mode) { // <<<<<<<<<<<<
.off => .Debug,
.any, .fast => .ReleaseFast,
.safe => .ReleaseSafe,
.small => .ReleaseSmall,
},
});
Feel free to send me a patch if you feel that’s important. I don’t know that the usual way to do these things is. The current setup works just fine for me.
Just added the standard options in 0.1.8.
Hello, Im a beginner with Zig, and I have a probably silly question about the code in the source .
I don’t see any code that uch as cwd.close().Is closing this kind of handle optional?
My understanding is that the operating system will clean used resources up (including memory and open files) after the process exits.
Thanks, I know that