i wrote a thing about why you should copy text instead of taking screenshots of text
| www | https://benjaminwil.info |
| pronouns | he/him/they/them |
| www | https://benjaminwil.info |
| pronouns | he/him/they/them |
i wrote a thing about why you should copy text instead of taking screenshots of text
julia evans mentioned this issue with ngrok in a blog post, “Terminal colours are tricky,” and reasons about why colour #16 might be orange instead of black with her base16 which is interesting.
https://jvns.ca/blog/2024/10/01/terminal-colours/#problem-5-programs-setting-a-background-color
but i’ve found this to be the case with all the base16 colour schemes i’ve tried. while i’m semi-mad at base16, i’m more mad that ngrok sets a background colour at all and that it’s outside of the ANSI 0-15 colours.
pro tip for base16 color scheme ngrok users…
if your terminal emulator uses a base16 colour scheme and you want to be able to read the text output by the ngrok program, simply prefix your ngrok command with
TERM=ngrok-sucks
and use the web client to view the request log. before and after screenshots below.
a couple of projects i work on document why ruby dependencies have been added to the gemfile and why those dependencies are locked to specific versions. we do this inline, in the gemfiles. i highly recommend doing this.
as a reader, this gives me a lot of context about the codebase at-a-glance. it tells me about how valuable a given dependency is.
as a dev adding gems, it forces me to *really* justify them and think critically about if i need a version lock or if i’m just giving into fear.