Re: Conversion from invalid to valid utf8 strings

2020-05-09 Thread Alex Shinn
Without debugging I suspect the problem is in utf8-start-byte->length, which reports an encoded length of 0 for the bytes #xFE and #xFF. You can just replace those 0's with 1's and it will "skip over" these invalid bytes. This is by design for simplicity and convenience. If you want to provide

Conversion from invalid to valid utf8 strings

2020-05-09 Thread Vasilij Schneidermann
Hello, I'm currently writing a Git repository viewer and stumbled upon this wonderful repository with challenging file names [1]. After writing some code to correctly encode links and labels I've realized that encoding UTF-8 strings will incorrectly escape bytes inside sequences that correspond

Re: Default file creation mode for core/scsh-process sets executable bit

2020-05-09 Thread Jörg F. Wittenberger
On Thu, 7 May 2020 16:43:47 +0200 Vasilij Schneidermann wrote: > Hello, > > I've noticed that when using process redirection in the scsh-process > egg, they're always marked as executable. Observe: > > ^_^ csi -R scsh-process -e '(run (ls -l) (> ls.txt))' > ^_^ ls -l ls.txt >