We always use trfs in the 9fs script.
It's so convenient that we forgot it's there.
I think it's in contrib. Otherwise let me know.
El 16/06/2009, a las 17:58, j...@csplan9.rit.edu escribió:
On Tue, 16 Jun 2009 08:00:44 -0400
erik quanstrom <quans...@quanstro.net> wrote:
note that this won't work if the filenames contain white space.
(i still regret the fact that white space became allowable in
file names)
using ws in filenames is a fossil-only problem;
kfs, cwfs and ken's fs won't allow it.
fortunately, fossil is easy to fix
/n/dump/2009/0616/sys/src/cmd/fossil/9p.c:102,108 - 9p.c:102,108
}
for(p = name; *p != '\0'; p++){
- if((*p & 0xFF) < 040){
+ if((*p & 0xFF) <= 040){
vtSetError("bad character in file name");
return 0;
}
- erik
So what happens when you drawterm from a un*x box or access a VFAT
partition? Perhaps 9fat could dynamically translate spaces in
filenames to some character illegal in Windows file names and not
special to rc, if there is such a character. I don't recall what
characters are illegal in Windows filenames but for the purposes of
example assume ~ is illegal:
I believe it was Nemo et al. who wrote trfs, which does essentially
what you want--it stands between you and your badly-named files,
presenting spaces as underscores or something to that effect.
John
[/mail/box/nemo/msgs/200906/42195]
