@prologic@twtxt.net well, I think OP mother tongue isn’t English, so certainly not an encoding I might be familiar with.
@bender@twtxt.net I’m using both machines in English.
Checked my locale and it spits out:
LANG=en_US.UTF-8
LC_CTYPE=“en_US.UTF-8”
LC_NUMERIC=“en_US.UTF-8”
LC_TIME=“en_US.UTF-8”
LC_COLLATE=“en_US.UTF-8”
LC_MONETARY=“en_US.UTF-8”
LC_MESSAGES=“en_US.UTF-8”
LC_PAPER=“en_US.UTF-8”
LC_NAME=“en_US.UTF-8”
LC_ADDRESS=“en_US.UTF-8”
LC_TELEPHONE=“en_US.UTF-8”
LC_MEASUREMENT=“en_US.UTF-8”
LC_IDENTIFICATION=“en_US.UTF-8”
LC_ALL=
🤷🏽 … and that only happens when vi, vim or nvim are launched by Jenny to compose a twt.
@prologic@twtxt.net Thank
you! and here’s a twt with the said random characters, since I’ve been
cleaning them up manually, earlier before scp-ing my twtxt.txt file. And
maybe a screenshot of how things look in my editor?
Those new lines are added automatically as I type (except for the ones
after the screenshot.
@prologic@twtxt.net sure! Give me a couple of minutes to set things up.
Also, you can check the charset again, I did set it up even tho I do observe the problem in my twtxt.txt file on my local machine way before doing scp to the remote one. They show up when I use bat but not when I cat the file nor on neomut.