[Date Prev] [Date Next] [Thread Prev] [Thread Next] Date Index Thread Index Search archive:
Date:Mon May 11 09:28:27 2001 
Subject:Re: Editing filenames with spaces 
From:Roger . Evans 
Volume-ID:1010511.02 

--------------12A04B55EAED5774523FF7CE
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Two comments on Aaron's suggestion:

1) I don't use <enter> ved file1 file2, but I do find multiple files on the
shell command line useful , such as
        % ved *.pl
I don't know whether this uses the same mechanism, but if it does, any
change should take account.

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 (Ok
so I appear to be the *only* windows user on this list, since no-one
responded to my earlier message :-) ). It  makes it awkward to install
poplog in the 'standard' windows place for applications (C:\Program Files\),
because it means you can't edit files in the poplog tree (such as
$popsys/init.p, or the whole of poplocal if you want to put it in the same
area).  Argh!

Roger


Aaron Sloman See text for reply address wrote:

> [To reply replace "Aaron.Sloman.XX" with "A.Sloman"]
>
> Some time ago (1993 I think) a decision was taken to make ved treat an
> argument with spaces as a request to read in multiple files.
>
> So,
>
>    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.
>
> Has anyone found a way to disable this?
>
> Does anyone ever use the ability to give Ved an argument with spaces?
> (I have known about it for a long time, but have never found it
> of any use.)
>
> I am inclined to find and comment out the code that breaks up
> vedargument if it contains spaces, or control it with a new
> global variable, e.g.
>
>     ved_multi_edit
>
> with default value false.
>
> Comments? Suggestions?
>
> There may be other utilities in pop-11 that will not work if file or
> directory names contain spaces. I have not checked sys_file_match
> for instance.
>
> Aaron
> ====
> Aaron Sloman, ( http://www.cs.bham.ac.uk/~axs/ )
> School of Computer Science, The University of Birmingham, B15 2TT, UK
> EMAIL A.Sloman AT cs.bham.ac.uk   (ReadATas@please !)
> PAPERS: http://www.cs.bham.ac.uk/research/cogaff/
> FREE TOOLS: http://www.cs.bham.ac.uk/research/poplog/freepoplog.html

--------------12A04B55EAED5774523FF7CE
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
<tt>Two</tt> comments on Aaron's suggestion:
<p>1) I don't use &lt;enter> ved file1 file2, but I do find multiple files
on the shell command line useful , such as
<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; % ved *.pl
<br>I don't know whether this uses the same mechanism, but if it does,
any change should take account.
<p>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.&nbsp; 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 (Ok so I appear
to be the *only* windows user on this list, since no-one responded to my
earlier message :-) ). It&nbsp; makes it awkward to install poplog in the
'standard' windows place for applications (C:\Program Files\), because
it means you can't edit files in the poplog tree (such as $popsys/init.p,
or the whole of poplocal if you want to put it in the same area).&nbsp;
Argh!
<p>Roger
<br>&nbsp;
<p>Aaron Sloman See text for reply address wrote:
<blockquote TYPE=CITE>[To reply replace "Aaron.Sloman.XX" with "A.Sloman"]
<p>Some time ago (1993 I think) a decision was taken to make ved treat
an
<br>argument with spaces as a request to read in multiple files.
<p>So,
<p>&nbsp;&nbsp; ENTER ved my report
<p>makes Ved attempt to read in a file called "my" and a file called
<br>"report".
<p>However since then it has become increasingly common for file stores
for
<br>use on unix and on windows/NT to be integrated. E.g. in this school
<br>all users get the same login directory whether they are using PCs
<br>running NT or using machines running solaris, linux, etc. Thus files
<br>created on any of the systems are accessible on the others.
<p>This makes the current behaviour of Ved intolerable, and as far
<br>as I can tell there is no facility for turning it off.
<p>Has anyone found a way to disable this?
<p>Does anyone ever use the ability to give Ved an argument with spaces?
<br>(I have known about it for a long time, but have never found it
<br>of any use.)
<p>I am inclined to find and comment out the code that breaks up
<br>vedargument if it contains spaces, or control it with a new
<br>global variable, e.g.
<p>&nbsp;&nbsp;&nbsp; ved_multi_edit
<p>with default value false.
<p>Comments? Suggestions?
<p>There may be other utilities in pop-11 that will not work if file or
<br>directory names contain spaces. I have not checked sys_file_match
<br>for instance.
<p>Aaron
<br>====
<br>Aaron Sloman, ( <a href="http://www.cs.bham.ac.uk/~axs/";>http://www.cs.bham.ac.uk/~axs/</a>
)
<br>School of Computer Science, The University of Birmingham, B15 2TT,
UK
<br>EMAIL A.Sloman AT cs.bham.ac.uk&nbsp;&nbsp; (ReadATas@please !)
<br>PAPERS: <a href="http://www.cs.bham.ac.uk/research/cogaff/";>http://www.cs.bham.ac.uk/research/cogaff/</a>
<br>FREE TOOLS: <a href="http://www.cs.bham.ac.uk/research/poplog/freepoplog.html";>http://www.cs.bham.ac.uk/research/poplog/freepoplog.html</a></blockquote>
</html>

--------------12A04B55EAED5774523FF7CE--