Aaron Sloman See text for reply address wrote:
> ENTER ved my report
>
> makes Ved attempt to read in a file called "my" and a file called
> "report".
>
> However since then it has become increasingly common for file stores for
> use on unix and on windows/NT to be integrated. E.g. in this school
> all users get the same login directory whether they are using PCs
> running NT or using machines running solaris, linux, etc. Thus files
> created on any of the systems are accessible on the others.
>
> This makes the current behaviour of Ved intolerable, and as far
> as I can tell there is no facility for turning it off.
I don't know how to turn it off, but there seems to be a different
itemiser for the command line, because ENTER ved 'junk 1' looks for
files 'junk and 1' (i.e., with quote marks as part of the names), rather
than treating 'junk 1' as a string.
I think the most natural thing would be to require the user to quote
names containing spaces (or other abnormal characters) in the way that
shells do. The procedure vedfilecomplete (bound to ESC 3 on my solaris
xved) could be made to assist the user by inserting quotes around words
that need them in the way that file completion in the bash shell does.
At the moment, if I have a file named 'junk 1', and ask ved to complete
a filename beginning with 'junk', it offers me 'junk 1' as a choice, but
then behaves as Aaron describes if I accept that choice.
Steve
|