https://sourceforge.net/p/clisp/bugs/738/2018-09-20T19:03:06.472000ZRecent changes to 738: Impnotes slightly misleading regarding Unix namestring contents2018-09-20T19:03:06.472000Z2018-09-20T19:03:06.472000ZRichard M Kreuterhttps://sourceforge.net/u/kreuter/https://sourceforge.net40888fad2002adbb824fa2a982c3603a999923e0

<div class="markdown_content"><p>The implementation notes (section 19.3) say that for Unix pathname namestrings "Name and type may be STRINGs of any LENGTH (consisting of printing CHARACTERs, except "/")".</p> <p>The documentation might be said not to describe all Clisp builds: the character repertoire that may occur in a Unix namestring turns out to be the set of characters whose encoding under CUSTOM::<em>DEFAULT-FILE-ENCODING</em> contains octets satisfying the expression VALID_FILENAME_CHAR in config.h. </p> <p>(What might be a separate issue is that for reasons I haven't figured out, on one OSX host where I've built Clisp without any specific configure options or config.h editing, VALID_FILENAME_CHAR excludes octets above #d127, even though the resulting Clisp supports the Unicode character set. Is there any reason for VALID_FILENAME_CHAR to do this when building a Clisp with Unicode characters?)</p></div>