Bjorn Neergaard

The issue here is `export PATH="$GOROOT/bin:$PATH"`. `$GOROOT` is evaluated when your `.zshrc` is read and not when the `PATH` is searched. As such you'll directly call the go binaries instead...

It looks like the offending lines came from the README -- it looks like this feature is not that well thought-out and potentially breaks stuff badly. I personally don't use...

There is one more option now in region.rs. No more unsafe (as any manual twiddling of virtual memory APIs will be), but also more active and more readable: https://github.com/darfink/region-rs

> This doesn't really remove `unsafe`, it just kicks the can to the `region-rs` crate which itself uses `unsafe` to call operating system APIs like `mprotect`. Err, I meant unsafe...

> Here I am not sure. Looks like it is enough to check if `/sys/module/overlay/parameters/metacopy` is present in sysfs. We discussed it with @rata previously and looks like there is...

There's no fixed specification, but most color schemes have a version for 16 color terminals. I'd prefer to have a pair of `[rgb, 16-color index]` in each theme, thus falling...

The proper way is to use terminfo (try `tput colors` on a system with modern ncurses and TERM set to `xterm-direct`, for instance). Personally, I'd prefer to have it configured...

(Making the color mode tri-state and adding a 4-bit mode would be perfect)

Also, themes could have automatic fallback support if they used the standard ANSI color names for 16 of their keys: black, red, green, blue, cyan, magenta, yellow, white (and bright...

I'd like to see this merged, or fixed up if it needs to be, if possible. @jstarks is there a list of blockers on merging this?