Hi,
On Mon, Apr 1, 2019 at 9:26 PM Torsten Bergmann <[email protected]> wrote: > If one downloads images with Launcher on Windows and accepts default names > like "Pharo 7.0 - 32bit (stable)" this will end up in path names like > > "C:/Users/Admin/Documents/Pharo/images/Pharo 7.0 - 32bit (stable)" > > The dot and space combination in such files can later make trouble when > downloading projects (like Seaside) using Iceberg and libgit and leading > later to the "IceGenericError: failed to stat file ... The filename or > extension is too long" problem. > > I guess the dot in combination with spaces in the name is sometimes seen > as the path element on current directory. > > If one gives an own name like "LatestPharo7" in Launcher (having > C:/Users/Admin/Documents/Pharo/images/LatestPharo7 then) Seaside loads > even from the FileTree format. > Wow, this is weird :) Would this be related too to this: https://github.com/OpenSmalltalk/opensmalltalk-vm/commit/e8f235ef313990acae0cda037bb0b35a9c88b7ad ? > As many people prefer to use Launcher now these days they might easily hit > this problem. > > I opened an issue already for Launcher so this discussion here on ML is > watched: > https://github.com/pharo-project/pharo-launcher/issues/327 > > Feedback and tests from Windows users are welcomed. > > But still, the bug looks like a libgit bug, doesn't it? I have in my hyper long TODO list to try to enhance libgit's windows support and contribute it back to libgit...
