is that an intention that acme does not recognize (or , not so sure
about '''chk' ) to be a name of a valid file? At least and seems to me
to be a valid file name, but clicking on it with button 3 in acme doesn't
work --- file is not opened. Only explicit use of Get opens it.
They are
Hello,
is that an intention that acme does not recognize (or , not so sure
about '''chk' ) to be a name of a valid file? At least and seems to me
to be a valid file name, but clicking on it with button 3 in acme doesn't
work --- file is not opened. Only explicit use of Get opens it.
Thanks
It's the plumber that decides. If you want those characters to be understood as
file name characters in general - and you really don't, whatever you think now;
consider what happens when you click on includefile.h - then change the
plumbing rules.
-rob
On Wed, Oct 8, 2008 at 9:35 AM, Rudolf
2008/10/8 Rob Pike [EMAIL PROTECTED]
It's the plumber that decides. If you want those characters to be
understood as
file name characters in general - and you really don't, whatever you think
now;
consider what happens when you click on includefile.h - then change the
plumbing rules.
-rob
Insert a plumbing rule before the usual one that considers those
characters part of filenames. Now you can plumb those scripts. When
it fails to find the file named includefile.h (with the quotes as
part of the filename), the plumber will move on to the next rule to
check for includefile.h (no
2008/10/8 grai [EMAIL PROTECTED]
Insert a plumbing rule before the usual one that considers those
characters part of filenames. Now you can plumb those scripts. When
it fails to find the file named includefile.h (with the quotes as
part of the filename), the plumber will move on to the next
