Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Your hex editor should color-code bytes

simonomi.dev

Post reply on HN
Print view View original

111–120 of 165 posts

Re: Your hex editor should color-code bytes

#111

Post by oblio »

davidmurdoch wrote: post #68
cubefox wrote: post #48

Earlier quoted context omitted.

> Everything should try do some basic syntax highlighting IMO. Interesting idea. So even syntax–highlighting natural language. Grammar highlighting, as it were. Prepositions, verbs, question marks, etc. An LLM could do it. Would it actually improve readability though? Seems likely!

I always enjoy to find people who think so drastically differently than myself. This sounds like an absolute nightmare to me and I would gauge my eyes out.

Everything in nature is colored. Our eyes are worse than dinosaur eyes but they can still distinguish millions of colors. We might as well use 5-10-20 for highlights.

Re: Your hex editor should color-code bytes

#112

Post by oblio »

NooneAtAll3 wrote: post #22

Why did author decide that best way to demonstrate his idea would be by cutting contrast in half? color-coding might be a great solution, but you don't really know beforehand which byte values are important. Manually selecting C0 to make it stand out it just ctrl+f with extra steps. (But I wouldn't mind something like "color 00 separate from ascii separate from the rest)

OP is automatically selecting similar colors across the spectrum. C0 is just very far from the rest so the color is very different to the other bytes.

Re: Your hex editor should color-code bytes

#113

Post by felooboolooomba »

jcalvinowens wrote: post #110

If you just want to see patterns, and don't actually need to see the values, you can go a step further and simply visualize the data as a bitmap, e.g. dd if=/dev/urandom bs=$[256*256] count=1 | display -size 256x256 -depth 8 GRAY:- You can do the same thing with audio, which makes different sorts of patterns obvious, e.g. dd if=/dev/urandom bs=$[256*256] count=1 | aplay -c 1

> dd if=/dev/urandom bs=$[256*256] count=1 | aplay -c 1

This plays sounds, sounds like "Liberate Mae?"

Re: Your hex editor should color-code bytes

#115

Post by gsich »

embedding-shape wrote: post #76
gsich wrote: post #45

Earlier quoted context omitted.

>1 in 12 men and 1 in 200 women go through the same sorts of experiences, and it’s worth it, if you aren’t color Not the same, it's a gradient.

Some people lack in vision, some lack in reading and some lack in stopping themselves to reply to comments misunderstanding others.

[flagged]

Re: Your hex editor should color-code bytes

#116

Post by ddingus »

dspillett wrote: post #11

Everything should try do some basic syntax highlighting IMO. Not too much, or it just becomes a sea of formatting that doesn't help at all. It is surprising how much difference just a little splash of colour can make if it isn't overdone. If possible, always include configuration options for the user though, so those with colour-blindness issues can tweak things to their needs, those who are just fussy can make the o…

A screen reader could use various aural means of emphasis that I bet would be as effective as this "color by pattern" idea is.

We have pitch, volume, enunciation speed, and for the voice itself the vocal formant frequency can change as can the harmonics. And that is a rich field we are good at differentiating in too.

One other screen reader idea I had upon seeing this is to use a brief sound either immediately before or after, maybe even slightly overlapping the vocalization.

30 [30 MS BEEP] CO [30 MS BEEP FOLLOWED BY A SHORT CHIRP THAT INDICATES A KNOWN ADDRESS]

Writing that out looks messy. All I can say is the sounds in my head right now make a lot more sense and would compliment the colors nicely.

Re: Your hex editor should color-code bytes

#117

Post by ddingus »

gsich wrote: post #115
embedding-shape wrote: post #76

Earlier quoted context omitted.

Some people lack in vision, some lack in reading and some lack in stopping themselves to reply to comments misunderstanding others.

[flagged]

Nope.

The greater point here being we definitely benefit when we all understand one another better.

Surely that point was not lost, yes?

Re: Your hex editor should color-code bytes

#118

Post by ddingus »

pc86 wrote: post #102
tosti wrote: post #87

Earlier quoted context omitted.

> They've been absolutely invaluable for making sure their kind of people can't use my apps properly. Why would you do that?

It's obviously a typo (or an excellently delivered joke) but I did get a chuckle out of the idea of someone going out of their way to ask color blind friends for feedback just to do the opposite out of spite for some reason.

I thought it was intended and excellent!

Re: Your hex editor should color-code bytes

#119

Post by ddingus »

cuechan wrote: post #23

For anyone who regularly has to look at/analyze binary files, i highly recommend ImHex [1]. Its a hex editor built with imgui and has a lot of built in tools. Imo the best feature is the data structure editor. You can write a data type definition similar to C and it overlays it on the hexdump and parses it in a structured way while you type. It also has a node based editor. 1: https://github.com/WerWolv/ImHex

THANK YOU.

This is another fine tool I can add to my collection.

And FUTO! Love it.

Re: Your hex editor should color-code bytes

#120

Post by contingencies »

shmerl wrote: post #90

Any good neovim plugin recommendation for hex editing?

I came to scan for the same thing, basically. Is there a vi(m) hex editor?

Hexmode https://github.com/fidian/hexmode or vim-deadc0de https://www.vim.org/scripts/script.php?script_id=6033

With decent color support? No.

Post reply on HN