rmkaplan

In the Venue sysout, UNPACKFILENAME gives the same result for {DSK}/medley {UNIX}/medley {DSK}medley both give DIRECTORY > NAME medley. But at least the function DIR shows the same files for...

I'm still trying to make sense of this, here's another try. The current UNPACKFILENAME produces different results for /foo → DIRECTORY NIL NAME foo (NIL indicating the top-level directory, same...

However... What should happen if appears in the middle of a directory sequence: xyz>foo → DIRECTORY abc>xyz NAME foo or DIRECTORY abc>xyz NAME foo It would be the first, on...

This is the behavior of internal directory brackets in the Venue sysout, and I think I just tried to replicate that when I did the rewrite. That’s not a change...

@nbrigg notes that Maiko only receives a filename that has already been canonicalized at the Lisp level, presumably by different combinations of UNPACKFILENAME, PACKFILENAME, ADD.CONNECTED.DIR, etc. I'll further note that...

This all happens after the end of the host has been identified, if there is one. Pseudohost doesn't interact at the level of file-name manipulation, a pseudohost is just another...

UNPACKFILENAME has always made that distinction in another way (FWIW?): (UNPACKFILENAME “foo/bar/baz”) produces SUBDIRECTORY foo/bar NAME baz (UNPACKFILENAME “/foo/bar/baz”) produces DIRECTORY foo/bar NAME baz > On May 13, 2024, at...

I have also seen this or something like it from time to time, for years, but I haven’t been able to pin it down. It isn’t specific to commonlisp functions,...

This is new behavior as of several months ago. There used to be sporadic comment-warning messages that should have been dealt with to get a clean transcript, but those were...

Perhaps it could have been imlemented as a CL stream composition if that had been available in those days, although probably with less efficiency at least in the case of...