On Wed, 24 Feb 2021 at 10:18, Michael Hennebry <hennebry@xxxxxxxxxxxxxxxxxxxxx> wrote:
[...]
In other people's posts, I've occasionally seen what I think was
supposed to be whitespace as question marks in black diamonds..
This time my own blanks came back to me that way.
They stay that way in alpines default editor.
Using its vim editor, I see blue vertical strokes followed by blanks.
Any idea what is happening?
I suspect it might have something to do with me using alpine through ssh.
That said, I thought blanks were immune to that sort of thing.
If the original text was Unicode, there are many new possible types of
"blanks": n-space, m-space, non-breaking space, etc. Conversions to
other encodings often have problems. This can be particularly
annoying in PDF handouts were cutting and pasting a block of
code into an editor looks "correct" but won't compile/execute.
It is one more reason to avoid spaces in file and directory names
that may be shared with others.
George N. White III
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
