3 ms·
I don't think that's a macOS bug. Your terminal emulation might be borked. What terminal are you using? I just tested on Terminal.app and iTerm2.app -- `man fo
by quesera 3y ago
I don't think that's a macOS bug. Your terminal emulation might be borked.
What terminal are you using? I just tested on Terminal.app and iTerm2.app -- `man fopen` looks correct on both.
The following should be equivalent, but might perform differently for you depending on what part of your config is bad:
cat /usr/share/man/man3/fopen.3 | nroff -man | more
- jerrysievert 3y agoiterm2.app - but I also use fish as my shell TERM=xterm-256color and LESS_TERMCAP_us=In
- iamthad 3y agoYour LESS_TERMCAP_us is the issue here; it's literally putting "In" wherever an underline is supposed to start.