Subject: Re: Logical pathname hosts. From: Erik Naggum <firstname.lastname@example.org> Date: 1998/12/23 Newsgroups: comp.lang.lisp Message-ID: <email@example.com> * Kent M Pitman <firstname.lastname@example.org> | In the examples I've seen, you're mapping all top-level dirs in that | device to the same directory, and so then it doesn't matter what the | "something;" is because it can have no effect. I would have shared your concern if that was what I observed. naturally, mapping everything to the root would be counterproductive, but at least under Allegro CL, the following mapping: (logical-pathname-translations "TDN") => ((#l"**;*.*" #p"/home/tdn/")) does not map everything to the root. I actually use several subdirectories under the TDN host, some of which have their own logical pathname host because it is useful to differentiate between absolute and relative pathnames, such as for an archive whose absolute mapping is to the root of the date-based archive directory hierarchy, and the relative mapping is to the current date within that archive. e.g., (logical-pathname-translations "archive") => ((#l";*.*" #p"archive:1998;12;23;") (#l"**;*.*" #p"tdn:archive;"))) this may look funny, but the point is that the first of these is actually recomputed every midnight, and does not want to do the mapping that the constant part does. I get the impression that you think there should have been a **;*.* at the end of the destinations, too. I have always figured they would have to be there. mapping everything to a single directory seems so utterly pointless that I can't see why it would be the expected behavior. #:Erik PS: mail to you fails for me at the moment -- Nie wieder KrF! Nie wieder KrF! Nie wieder KrF! Nie wieder KrF!