[Date Prev] [Date Next] [Thread Prev] [Thread Next] Date Index Thread Index Search archive:
Date:Mon May 11 14:07:35 2001 
Subject:Re: Editing filenames with spaces 
From:Roger . Evans 
Volume-ID:1010511.08 

Hmm, thanks for finding this Steve (I have the poplog sources but have never got
round to installing them).
The actual test is for a space in the filename and an empty directory part which
is why it didn't work for me - I was using a full pathname.  I wonder why Rob did
it like that?

But anyway, I don't see why this should be a windows-specific fix. The point is
that restrictions on the form of filenames (or tokens) are/should be restrictions
on the shell/compiler reading them in, not the underlying objects themselves...

Roger

Stephen Isard wrote:

> Roger.Evans@itri.brighton.ac.uk wrote:
>
> > 2) More seriously, I refer you to ref vedprocs, line 134ff. Ved's treatment
> > of filenames with spaces in them is to create a pseudo-buffer instead of
> > opening a real file.  There doesn't appear to be any way to disable this
> > (since someone seems to think 'sensible' filenames would never have spaces
> > in them :-) ), so it would rather scupper Aaron's plan. Personally I'd be
> > very happy to see this 'feature' removed or at least made controllable.
> > Apart from the general principle of not making unnecessary arbitrary
> > assumptions about filenames, it is a real pain for poplog under windows
>
> Someone (Robert Duncan in fact, according to the revision history) seems
> to have at least tried to address the problem, because the definition of
> ved_ved in vdprocess.p contains (line 812)
>
> #_IF DEF WIN32
>         ;;; filenames can include spaces, so treat vedargument as a single
>         ;;; file (and not as a workbuff -- see Is_file_name in "vdfiles.p")
>
> Does this not work?  (I guess this question is addressed to Roger, if he
> is the only Windows poplog user.)  If it does, then simply adopting the
> #_IF DEF WIN32 clauses here and in Is_file_name should be pretty
> straightforward.  (And ref vedprocs should be revised.)
>
> A comment in the definition of Is_file_name notes that you still can't
> create a new file in the current directory with a space in its name
> using ved_ved, but that doesn't sound nearly as serious as Aaron's
> original problem.
>
> Steve