lemmonade

joined 1 year ago
[โ€“] lemmonade@lemmy.world 7 points 1 year ago* (last edited 1 year ago) (1 children)

no, it's just squiggly lines, no writing on that paper.

[โ€“] lemmonade@lemmy.world 3 points 1 year ago* (last edited 2 months ago)

you can read "dumber" books, but the internet literally responds to you.

[โ€“] lemmonade@lemmy.world 11 points 1 year ago (1 children)

what? where? look at the username, that's clearly anonymous, the hacker group.

[โ€“] lemmonade@lemmy.world 3 points 1 year ago

thanks! this didn't solved my specific problem but caused another problem for me (e.g. _M_A_N(1)), but while searching about MANROFFOPT I came across a reddit post I had somehow missed when searching for a solution, and it it the actual solution was mentioned. what worked for me is export MANPAGER='nvim +Man!' instead.

 

I use zsh and have export MANPAGER="nvim -Rc 'set ft=man' -" in my .zshrc. this used to work well but since a couple of weeks ago, whenever I run man (e.g. man man) I get many weird escape characters (e.g. MAN(1)). when running man and manually piping the output to another program (e.g. man man | nvim -Rc 'set ft=man' -) I don't get these characters (e.g. MAN(1)). I haven't been able to figure out why this happens or how to fix it. does anyone else have an idea?

edit: turns out :h man had a solution, using export MANPAGER='nvim +Man!'' instead of export MANPAGER="nvim -Rc 'set ft=man' -".

[โ€“] lemmonade@lemmy.world 3 points 1 year ago

I update every weekend because that's when I have time to fix the issues that (rarely) come up because of updates. I also update and restart if there's a problem I don't understand as a way to try to solve that.

[โ€“] lemmonade@lemmy.world 3 points 1 year ago* (last edited 1 year ago)

didn't notice this, I use a couple of alts and create a new one from time to time (although I do this less and less because I mostly use lemmy instead now)