Skip to content
Snippets Groups Projects
  1. Nov 04, 2011
  2. Sep 25, 2011
  3. Mar 01, 2011
  4. Nov 08, 2010
  5. Jun 07, 2010
    • rtoy's avatar
      code/filesys.lisp: · 01274f39
      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.
      01274f39
    • rtoy's avatar
      code/fd-stream.lisp: · c5eff503
      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.
      c5eff503
  6. Apr 20, 2010
  7. Apr 19, 2010
  8. Mar 19, 2010
  9. Jun 11, 2009
  10. Jun 19, 2008
  11. Jun 18, 2008
  12. Sep 10, 2007
  13. Aug 04, 2007
  14. Jan 20, 2007
  15. Jan 16, 2007
  16. Mar 14, 2006
    • rtoy's avatar
      o Add docstring for *IGNORE-WILDCARDS*. · 172f99d7
      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.
      172f99d7
  17. Dec 04, 2005
  18. Nov 07, 2005
  19. Nov 04, 2005
  20. Oct 22, 2005
  21. Oct 21, 2005
  22. Oct 05, 2005
    • rtoy's avatar
      Fix a couple of issues with ENOUGH-NAMESTRING not returning the · afe77f2a
      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.
      afe77f2a
  23. Sep 30, 2005
    • rtoy's avatar
      parse-unix-namestring: · c0715083
      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.
      c0715083
  24. Sep 25, 2005
    • rtoy's avatar
      extract-name-type-and-version: · c2cdcb87
      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.
      c2cdcb87
  25. Sep 22, 2005
  26. Sep 21, 2005
    • rtoy's avatar
      code/filesys.lisp: · ad045f27
      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?)
      ad045f27
  27. Sep 12, 2005
    • rtoy's avatar
      Fix some issues with printing (make-pathname :directory '(:relative)), · c33b7b7a
      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.
      c33b7b7a
  28. Aug 31, 2005
  29. Aug 22, 2005
  30. Feb 10, 2005
  31. Dec 13, 2004
  32. Oct 18, 2004
    • rtoy's avatar
      EXTRACT-NAME-TYPE-AND-VERSION: · 488afce7
      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.
      488afce7
  33. Sep 27, 2004
    • rtoy's avatar
      Do not signal errors when a version is given without a name. This · aa27fcc2
      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.
      aa27fcc2
  34. Sep 13, 2004
  35. Jun 02, 2004
  36. Apr 01, 2004
    • rtoy's avatar
      Helmut Eller notes on cmucl-imp on 2004-04-24 that · 70cf5703
      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.
      70cf5703
  37. Jan 09, 2004
Loading