- Jun 07, 2010
-
-
rtoy authored
o FILE-WRITE-DATE merges the filename with *DEFAULT-PATHNAME-DEFAULTS*, as required by CLHS sec 19.2.3. general-info/release-20b.txt: o Update.
-
rtoy authored
o OPEN merges the filename with *DEFAULT-PATHNAME-DEFAULTS*, as required by CLHS sec 19.2.3. code/filesys.lisp: o DELETE-FILE, ENSURE-DIRECTORIES-EXIST, and FILE-AUTHOR merge the filename with *DEFAULT-PATHNAME-DEFAULTS*, as required by CLHS sec 19.2.3. general-info/release-20b.txt: o Update.
-
- Apr 20, 2010
-
-
rtoy authored
may get confused with source locations if the reader macros are installed.
-
- Apr 19, 2010
-
-
rtoy authored
-
- Mar 19, 2010
-
-
rtoy authored
boot-2010-02-1 as the bootstrap file. You should probably also use the new -P option for build.sh to generate and update the po files while building.
-
- Jun 11, 2009
-
-
rtoy authored
unicode-utf16-extfmt-2009-06-11.
-
- Jun 19, 2008
-
-
rtoy authored
Basically, don't use delete-duplicates but do it ourselves since the list is already sorted. From Lynn Quam, cmucl-imp, 2008/06/05, slightly modified. code/filesys.lisp: o New DIRECTORY function general-info/release-19f.txt: o Update
-
- Jun 18, 2008
-
-
rtoy authored
with the original filespec, not the truename of the filespec. Also fixes the issue where defaulted-new-name should be an LPN if new-name is. From Madhu, cmucl-imp, 2008/06/01.
-
- Sep 10, 2007
-
-
rtoy authored
bug that #p"..." didn't have a namestring. Some further changes were also applied to fix the problem that #p"..a" had directory = (:relative), name = nil, and type "a". This is now directory = nil, name = ".", type ="a".
-
- Aug 04, 2007
-
-
fgilham authored
-
- Jan 20, 2007
-
-
fgilham authored
source comment associated with change.
-
- Jan 16, 2007
-
-
rtoy authored
print/read consistency because "foo.~01~ is printed as "foo.~1~". This could be fixed in other places, but it seems best not to allow leading zeroes in the version number. Patch from Madhu, cmucl-imp, 2007-01-14.
-
- Mar 14, 2006
-
-
rtoy authored
o Make UNPARSE-UNIX-PIECE honor *IGNORE-WILDCARDS*. Requested by Lynn Quam so namestrings can be given to run-program and friends without pathname wildcards escaped.
-
- Dec 04, 2005
-
-
rtoy authored
namestring. Bug noted by Lynn Quam, cmucl-imp, 2005/12/02.
-
- Nov 07, 2005
-
-
rtoy authored
-
- Nov 04, 2005
-
-
rtoy authored
component contains a "/" or "." because we can't print these readably.
-
- Oct 22, 2005
-
-
rtoy authored
name. (But we still have problems with print/read for :newest and :unspecific.)
-
- Oct 21, 2005
-
-
rtoy authored
so signal an error when we try to generate the the namestring.
-
- Oct 05, 2005
-
-
rtoy authored
shortest namestring: (enough-namestring #p"/foo" #p"/") => "foo", not "./foo" (enough-namestring #p"foo/bar" #p"foo/") => "bar", not "foo/bar" We check for a common prefix for all cases first now, instead of just when the pathname is :absolute.
-
- Sep 30, 2005
-
-
rtoy authored
o Don't allow a namestring to be parsed as a search-list if a logical host with the same host name already exists. Allowing this causes confusing in printing such pathnames because, when read, the logical host takes precedence. unparse-unix-file: o Preserve version :NEWEST when printing out logical pathnames. This makes #p"host:foo.bar.newest" readable.
-
- Sep 25, 2005
-
-
rtoy authored
o Leave some debugging prints in, but commented out. o In the last case for EXPLICIT-VERSION, when looking for digits surrounded by ~'s, return version NIL if we don't find just digits. #p"foo.*" was returning version :newest. I think we really want :version nil. unparse-unix-enough: o If the pathname has no directory, it's relative to the defaults. Returning NIL is probably as good as returning '(:RELATIVE), and results in a shorter namestring.
-
- Sep 22, 2005
-
-
rtoy authored
the first path in a search-list to determine the appropriate namestring. This is mostly intended to work with the "home:" search-list, which only has one path, by default.
-
- Sep 21, 2005
-
-
rtoy authored
o Make the #p reader treat ".." as a directory, not a file. o Make the #p reader treat "<lots of dots>" be a file with that name instead of name with one fewer dot and type "". So #p"..." has :name "...", :type nil instead of :name "..", :type "". code/pathname.lisp: o Issue a warning if someone wants :name to be ".." or ".". We allow it, but doing so will break print/read consistency. (Should we make such pathnames not readably printable?)
-
- Sep 12, 2005
-
-
rtoy authored
which used to print as #p"", and with reading #p".", #p"./". code/filesys.lisp: o When parsing a unix namestring, delete any "." elements of the directory list. o If we've parsed a namestring such that the file name is ".", replace that with :name NIL and adjust the :directory component appropriately, because on Unix, "." can't be the name of a file. o Make :directory '(:relative) be printed as "./" code/pathname.lisp: o If the :directory argument to MAKE-PATHNAME contains strings with #\/, print a warning that this is not a valid element. o Remove all "."'s from a :relative directory component.
-
- Aug 31, 2005
-
-
rtoy authored
instead of #p"a/b/c/". Fix it.
-
- Aug 22, 2005
-
-
rtoy authored
creation. From Eduardo Munoz, cmucl-imp, 2005/07/31.
-
- Feb 10, 2005
-
-
rtoy authored
accepted when computing namestrings. CLHS 19.2.2.2.3.1 says :unspecific components should not appear in the namestring. Make it so.
-
- Dec 13, 2004
-
-
rtoy authored
when converting to a namestring. Bug and fix from Artem V. Andreev, cmucl-imp, 2004-12-12.
-
- Oct 18, 2004
-
-
rtoy authored
o Was not treating "foo.lisp.*" as having a version :wild, like cmucl used to. Reinstate this. o Honor *ignore-wildcards* when extracting versions. This prevents errors if there's a file named like "foo.lisp.~*~". %ENUMERATE-FILES: o Was handling the case when the version is :wild. We now search the directory for versions that match. Issue reported by Lynn Quam, cmucl-imp, 2004-10-15.
-
- Sep 27, 2004
-
-
rtoy authored
needs to be rethought because there's confusion on what pathnames can be printed readably or not. In particular (probe-file "logical-host:dir;") gets an error because there's a merge-pathname that creates a pathname without a name, but version :newest.
-
- Sep 13, 2004
-
-
rtoy authored
o If we have a version, but no name, we can't print readably, so signal an error instead.
-
- Jun 02, 2004
- Apr 01, 2004
-
-
rtoy authored
(delete-file (open "/tmp/tmp-file" :direction :output :if-does-not-exist :create :if-exists :supersede)) signals an error because delete-file is unlinking the file twice, because CLOSE is called with the option :ABORT T. Don't do that, so that any reversion of the file isn't done, and we file is deleted.
-
- Jan 09, 2004
- Aug 05, 2003
-
-
toy authored
(version NIL) and we're looking for version :NEWEST, since that's what no explicit version means.
-
- Jun 11, 2003
-
-
toy authored
purge-files, which is just too vague. (directory): Specify a default-version of :WILD for merge-pathnames to make sure we can match any version when looking for files.
-
- Jun 10, 2003
-
-
toy authored
*default-pathname-defaults* changed from :newest to :unspecific, so merging doesn't automatically create versioned files. (extract-name-type-and-version): When no explicit version is given in a namestring, return version NIL instead of :NEWEST.
-
toy authored
o Fix a number of spelling errors. o Add EXT:PURGE-FILES (hmm, should that be renamed to purge-backup-files?) to delete old versions of files. o Opening a file with :if-exists :append shouldn't set the Unix append flag, else you can't seek back to a point before you started appending. (Actually from Rudi Schlatte.) o Fix a bug in logical pathname parsing. o Fix FASL-file versioning so we don't create versioned fasl files.
-