How does anyone do this? I’ve heard that companies sometimes do code reviews on paper, so I figured this would be a solved problem.
Still, I couldn’t find a decent solution anywhere. So there’s the question for Ask HN. How in the world does anyone print code in a reasonable way?
By “reasonable”, I mean:
1. with line numbers,
2. with syntax highlighting,
3. and preferably some sane separation of source files.
Smol:
https://github.com/stjepang/smol
You lose facilities like: goto source, search/replace, modifications (I might modify/format a piece of code temporarily, to help me understand it better, might rename functions, variables, add lines to visually separate parts of code, etc) and many more.
You re-enforce your discomfort with reading/writing code on the screen. I'm trying to assume different reasons that you might have to learn a code and for all of them that I can imagine, you'll be better off as someone who feels at home with the screen. So I suggest you to resist this temptation and do what you ultimately will do.
Out of curiosity, Is your job/situation/skills in a way that being good with screen will not seriously benefit you? How?
I think it is a good idea to print it out to help you understand. I consider it on occasion but don't want to pay for the ink and paper. Plus printers have some unspoken vendetta against me...they hate me and I hate them.
$ mkdir rtfs
$ for F in src/**.rs; do
> pygmentize -o rtfs/$(basename $F .rs).rtf -O linenos=1 $F
> done
Now open the .rtf files with a word processor and print them.To change the highlighting theme, e.g. to "pastie":
$ pygmentize -O style=pastie,linenos=1 ....
https://marketplace.visualstudio.com/items?itemName=nobuhito...