9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
* Re: [9fans] acme question + diffs for kfs, fs and plumbing
@ 2002-07-09  8:42 Fco.J.Ballesteros
  2002-07-09  9:28 ` Lucio De Re
  0 siblings, 1 reply; 81+ messages in thread
From: Fco.J.Ballesteros @ 2002-07-09  8:42 UTC (permalink / raw)
  To: 9fans

: Wrong!  What if files 'a b' and 'a_b' both exist on the foreign
: system?  Back to the drawing board, everyone, the problem needs
: another, slightly more focussed iteration.

I'm renaming ' ' with ␣ in u9fs
There's no problem doing that since there's no ␣
in outside file names.


^ permalink raw reply	[flat|nested] 81+ messages in thread
* Re: [9fans] blanks in file names
@ 2002-07-10 18:27 David Gordon Hogan
  2002-07-10 20:56 ` arisawa
  0 siblings, 1 reply; 81+ messages in thread
From: David Gordon Hogan @ 2002-07-10 18:27 UTC (permalink / raw)
  To: 9fans

Isn't this thread dead yet?



^ permalink raw reply	[flat|nested] 81+ messages in thread
* Re: [9fans] blanks in file names
@ 2002-07-10  8:00 Fco.J.Ballesteros
  0 siblings, 0 replies; 81+ messages in thread
From: Fco.J.Ballesteros @ 2002-07-10  8:00 UTC (permalink / raw)
  To: 9fans

[-- Attachment #1: Type: text/plain, Size: 277 bytes --]

Really, I make changes now and then; many times after
trying the resulting binaries I change my mind and
use yesterday + cp to restore the source back to its
previous state. Some other times I bind temporary directories
on top of the sources and make the changes there.


[-- Attachment #2: Type: message/rfc822, Size: 2260 bytes --]

From: Dave <dave@dave.tj>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] blanks in file names
Date: Tue, 09 Jul 2002 11:23:25 -0400 (EDT)
Message-ID: <200207091523.g69FNP431828@dave2.dave.tj>

You're not going to do that every time you make a change to the
filesystem.  Besides, that won't undo all the "changes" to all the
new programs that lack complexity because they don't have to reinvent
the wheel.

 - Dave


Fco.J.Ballesteros wrote:
> 
> >> But above all, I will undo the changes made in this respect to my
> >> local system if you guys or the system designers choose a different way.
> ...
> > Undoing kernel-level changes won't be easy, especially when people start
> 
> 9fs dump
> cp blah blah
> 
> Sorry, couldn't resist. I just love this system :-)
> 

^ permalink raw reply	[flat|nested] 81+ messages in thread
* Re: [9fans] acme question + diffs for kfs, fs and plumbing
@ 2002-07-10  7:57 Fco.J.Ballesteros
  0 siblings, 0 replies; 81+ messages in thread
From: Fco.J.Ballesteros @ 2002-07-10  7:57 UTC (permalink / raw)
  To: 9fans

[-- Attachment #1: Type: text/plain, Size: 97 bytes --]

There's no reason.
I though of using ☺, but I think it's more
usual in file names than ␣.

[-- Attachment #2: Type: message/rfc822, Size: 2148 bytes --]

From: Dave <dave@dave.tj>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] acme question + diffs for kfs, fs and plumbing
Date: Tue, 09 Jul 2002 11:29:45 -0400 (EDT)
Message-ID: <200207091529.g69FTj832499@dave2.dave.tj>

AFAIK, VFAT uses Unicode for its long file names, so I see no reason
why ␣ shouldn't be allowed there.

 - Dave


Fco.J.Ballesteros wrote:
> 
> : Wrong!  What if files 'a b' and 'a_b' both exist on the foreign
> : system?  Back to the drawing board, everyone, the problem needs
> : another, slightly more focussed iteration.
> 
> I'm renaming ' ' with ␣ in u9fs
> There's no problem doing that since there's no ␣
> in outside file names.
> 

^ permalink raw reply	[flat|nested] 81+ messages in thread
* Re: [9fans] acme question + diffs for kfs, fs and plumbing
@ 2002-07-09 12:24 Fco.J.Ballesteros
  0 siblings, 0 replies; 81+ messages in thread
From: Fco.J.Ballesteros @ 2002-07-09 12:24 UTC (permalink / raw)
  To: 9fans

[-- Attachment #1: Type: text/plain, Size: 242 bytes --]

The rune I was talking about is "open box, visible space"
(0x2423) I'm sorry, but I thought all of us could accept utf mails. 
If there's ever such a rune being used in outside
systems, you can always pick a different one (still unused).

[-- Attachment #2: Type: message/rfc822, Size: 1823 bytes --]

From: "matt" <matt@proweb.co.uk>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] acme question + diffs for kfs, fs and plumbing
Date: Tue, 9 Jul 2002 13:05:30 +0100
Message-ID: <022201c22740$ecbec270$6501a8c0@xpire>

>I'm renaming ' ' with â^У in u9fs
>There's no problem doing that since there's no â^У
>in outside file names.

can't see them either but "there is no" could possibly become "oops now
there is"?

^ permalink raw reply	[flat|nested] 81+ messages in thread
* Re: [9fans] acme question + diffs for kfs, fs and plumbing
@ 2002-07-09  9:37 Fco.J.Ballesteros
  0 siblings, 0 replies; 81+ messages in thread
From: Fco.J.Ballesteros @ 2002-07-09  9:37 UTC (permalink / raw)
  To: 9fans

[-- Attachment #1: Type: text/plain, Size: 117 bytes --]

It's ok if the name contains '?', it's just inconvenient but
it's ok. It's like that inconvenient "'chk" name I had.

[-- Attachment #2: Type: message/rfc822, Size: 2762 bytes --]

From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] acme question + diffs for kfs, fs and plumbing
Date: Tue, 9 Jul 2002 11:28:57 +0200
Message-ID: <20020709112856.L20312@cackle.proxima.alt.za>

On Tue, Jul 09, 2002 at 10:42:04AM +0200, Fco.J.Ballesteros wrote:
> 
> I'm renaming ' ' with ? in u9fs
> There's no problem doing that since there's no ?
> in outside file names.

There could be:

-rw-r--r--   1 lucio  staff         0 Jul  9 11:22 t?uch

produced by "touch t\?uch" on my NetBSD host.  This is from
"man 2 intro" on NetBSD 1.5.2:

     File Name
             Names consisting of up to 255 (MAXNAMELEN) characters may be used
             to name an ordinary file, special file, or directory.

             These characters may be selected from the set of all ASCII char-
             acter excluding 0 (NUL) and the ASCII code for `/' (slash).  (The
             parity bit, bit 7, must be 0.)

             Note that it is generally unwise to use `*', `?', `[' or `]' as
             part of file names because of the special meaning attached to
             these characters by the shell.

It needn't be up to date, but it's a safe indicator.

++L

^ permalink raw reply	[flat|nested] 81+ messages in thread
* Re: [9fans] acme question + diffs for kfs, fs and plumbing
@ 2002-07-09  8:40 Fco.J.Ballesteros
  0 siblings, 0 replies; 81+ messages in thread
From: Fco.J.Ballesteros @ 2002-07-09  8:40 UTC (permalink / raw)
  To: 9fans

[-- Attachment #1: Type: text/plain, Size: 88 bytes --]

Yes, but did an undo and will never redo it.
Had enough blanks for the rest of my life.

[-- Attachment #2: Type: message/rfc822, Size: 1381 bytes --]

From: arisawa@ar.aichi-u.ac.jp
To: 9fans@cse.psu.edu
Subject: Re: [9fans] acme question + diffs for kfs, fs and plumbing
Date: Tue,  9 Jul 2002 17:22:03 +0900
Message-ID: <20020709082218.AB50B199EE@mail.cse.psu.edu>

I guess that someone (probably nemo) has already fixed acme
so that we can enter into '/n/c/My Document/' using mouse.
Or already fixed in official update?

Kenji Arisawa

^ permalink raw reply	[flat|nested] 81+ messages in thread
* Re: [9fans] blanks in file names
@ 2002-07-09  7:54 Fco.J.Ballesteros
       [not found] ` <Fco.J.Ballesteros@Jul>
  0 siblings, 1 reply; 81+ messages in thread
From: Fco.J.Ballesteros @ 2002-07-09  7:54 UTC (permalink / raw)
  To: 9fans

>> But above all, I will undo the changes made in this respect to my
>> local system if you guys or the system designers choose a different way.
...
> Undoing kernel-level changes won't be easy, especially when people start

9fs dump
cp blah blah

Sorry, couldn't resist. I just love this system :-)



^ permalink raw reply	[flat|nested] 81+ messages in thread
* Re: [9fans] acme question + diffs for kfs, fs and plumbing
@ 2002-07-09  7:50 Fco.J.Ballesteros
  2002-07-09  8:15 ` Lucio De Re
  2002-07-09  8:22 ` [9fans] acme question + diffs for kfs, fs and plumbing arisawa
  0 siblings, 2 replies; 81+ messages in thread
From: Fco.J.Ballesteros @ 2002-07-09  7:50 UTC (permalink / raw)
  To: 9fans

> We need not distinguishing 'a b' from 'a_b' because there are
> no files that contains ' ' in their names.

I'm glad to be at home again ☺
Things are so easy now...



^ permalink raw reply	[flat|nested] 81+ messages in thread
* Re: [9fans] acme question + diffs for kfs, fs and plumbing
@ 2002-07-09  7:46 Fco.J.Ballesteros
  0 siblings, 0 replies; 81+ messages in thread
From: Fco.J.Ballesteros @ 2002-07-09  7:46 UTC (permalink / raw)
  To: 9fans

[-- Attachment #1: Type: text/plain, Size: 205 bytes --]

Just to clarify, I'm no longer pursuing blanks on Plan 9.
As a matter of fact, I never liked them. Now that I'm happy
to see that Rob does not want them on native files I can just
rename them in u9fs.

[-- Attachment #2: Type: message/rfc822, Size: 1485 bytes --]

From: okamoto@granite.cias.osakafu-u.ac.jp
To: 9fans@cse.psu.edu
Subject: Re: [9fans] acme question + diffs for kfs, fs and plumbing
Date: Tue, 9 Jul 2002 09:38:32 +0900
Message-ID: <20020709003915.580A719991@mail.cse.psu.edu>

>I would just like an acme window to be able to hold
>"/a/b x/d/e/f x"

Why, nemo, are you so eager to permit blank as a file name?
Does it come from European language nature?
IMHO:  our language, yes Japanese has no such blank as a delimiter
of words, so I have no such interest to that.  :-)

Kenji

^ permalink raw reply	[flat|nested] 81+ messages in thread
* Re: [9fans] acme question + diffs for kfs, fs and plumbing
@ 2002-07-09  0:38 okamoto
  0 siblings, 0 replies; 81+ messages in thread
From: okamoto @ 2002-07-09  0:38 UTC (permalink / raw)
  To: 9fans

>I would just like an acme window to be able to hold
>"/a/b x/d/e/f x"

Why, nemo, are you so eager to permit blank as a file name?
Does it come from European language nature?
IMHO:  our language, yes Japanese has no such blank as a delimiter
of words, so I have no such interest to that.  :-)

Kenji



^ permalink raw reply	[flat|nested] 81+ messages in thread
* Re: [9fans] acme question + diffs for kfs, fs and plumbing
@ 2002-07-08 16:14 rob pike, esq.
  0 siblings, 0 replies; 81+ messages in thread
From: rob pike, esq. @ 2002-07-08 16:14 UTC (permalink / raw)
  To: 9fans

> 99% only.  You'd still have the problem of names that arrive surreptitiously,
> such as in tar files.

Expanding a bit....

This is why I decided (mea maxima culpa) to admit blanks in file names.
They show up, you don't know where from, and if the basic tools have
ways of coping (as opposed to being graceful and perfect in handling them)
you can get by without mystery error messages caused by the operating
system rejecting them deep down.

I think the setup is sufficient, and sufficient unto the day is the evil thereof.

-rob



^ permalink raw reply	[flat|nested] 81+ messages in thread
* Re: [9fans] acme question + diffs for kfs, fs and plumbing
@ 2002-07-08 16:07 rob pike, esq.
  2002-07-08 20:58 ` Dave
  0 siblings, 1 reply; 81+ messages in thread
From: rob pike, esq. @ 2002-07-08 16:07 UTC (permalink / raw)
  To: 9fans

[-- Attachment #1: Type: text/plain, Size: 110 bytes --]

99% only.  You'd still have the problem of names that arrive surreptitiously,
such as in tar files.

-rob

[-- Attachment #2: Type: message/rfc822, Size: 3446 bytes --]

[-- Attachment #2.1.1: Type: text/plain, Size: 89 bytes --]

Renaming them would get us quickly up to 100%, with no need
to fix anything. Am I wrong?

[-- Attachment #2.1.2: Type: message/rfc822, Size: 1779 bytes --]

From: "rob pike, esq." <rob@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] acme question + diffs for kfs, fs and plumbing
Date: Mon, 8 Jul 2002 12:00:09 -0400
Message-ID: <a5b373bbdc70b762911c083da046ca5f@plan9.bell-labs.com>

> Glub! My first view of all this blank thing was just to forbid
> them and maybe rename them just to avoid them (They make things more
> complex for our programs). 

I encounter a dozen blank-containing names a day, but only from
interacting with foreign systems.  I find the current setup covers about
80% of what I need; fixing a few other simple things would probably
get us to 99%.  But upon reflection I don't think it's wise to push for
blanks to be first-class citizens in file names.  As long as we continue
to use linguistic rather than graphical interfaces to most of our tools,
that would be a mistake.

-rob

^ permalink raw reply	[flat|nested] 81+ messages in thread
* Re: [9fans] acme question + diffs for kfs, fs and plumbing
@ 2002-07-08 16:05 Fco.J.Ballesteros
  0 siblings, 0 replies; 81+ messages in thread
From: Fco.J.Ballesteros @ 2002-07-08 16:05 UTC (permalink / raw)
  To: 9fans

[-- Attachment #1: Type: text/plain, Size: 89 bytes --]

Renaming them would get us quickly up to 100%, with no need
to fix anything. Am I wrong?

[-- Attachment #2: Type: message/rfc822, Size: 1779 bytes --]

From: "rob pike, esq." <rob@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] acme question + diffs for kfs, fs and plumbing
Date: Mon, 8 Jul 2002 12:00:09 -0400
Message-ID: <a5b373bbdc70b762911c083da046ca5f@plan9.bell-labs.com>

> Glub! My first view of all this blank thing was just to forbid
> them and maybe rename them just to avoid them (They make things more
> complex for our programs). 

I encounter a dozen blank-containing names a day, but only from
interacting with foreign systems.  I find the current setup covers about
80% of what I need; fixing a few other simple things would probably
get us to 99%.  But upon reflection I don't think it's wise to push for
blanks to be first-class citizens in file names.  As long as we continue
to use linguistic rather than graphical interfaces to most of our tools,
that would be a mistake.

-rob

^ permalink raw reply	[flat|nested] 81+ messages in thread
* Re: [9fans] acme question + diffs for kfs, fs and plumbing
@ 2002-07-08 16:00 rob pike, esq.
  0 siblings, 0 replies; 81+ messages in thread
From: rob pike, esq. @ 2002-07-08 16:00 UTC (permalink / raw)
  To: 9fans

> Glub! My first view of all this blank thing was just to forbid
> them and maybe rename them just to avoid them (They make things more
> complex for our programs). 

I encounter a dozen blank-containing names a day, but only from
interacting with foreign systems.  I find the current setup covers about
80% of what I need; fixing a few other simple things would probably
get us to 99%.  But upon reflection I don't think it's wise to push for
blanks to be first-class citizens in file names.  As long as we continue
to use linguistic rather than graphical interfaces to most of our tools,
that would be a mistake.

-rob



^ permalink raw reply	[flat|nested] 81+ messages in thread
* Re: [9fans] acme question + diffs for kfs, fs and plumbing
@ 2002-07-08 15:51 Fco.J.Ballesteros
  0 siblings, 0 replies; 81+ messages in thread
From: Fco.J.Ballesteros @ 2002-07-08 15:51 UTC (permalink / raw)
  To: 9fans

[-- Attachment #1: Type: text/plain, Size: 555 bytes --]

Glub! My first view of all this blank thing was just to forbid
them and maybe rename them just to avoid them (They make things more
complex for our programs). 

But then I (mis)understood that the plan for the system was to give
them a chance; thus I tried to find a simple way to get them working.

Now that I finally see that the agreement is on 
`blanks would mess up things', I think I'll just add them to isfrog and
rename them in u9fs (the only place were I get blanks into the system).

Thanks for your answer and sorry about the mess.

[-- Attachment #2: Type: message/rfc822, Size: 1319 bytes --]

From: "rob pike, esq." <rob@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] acme question + diffs for kfs, fs and plumbing
Date: Mon, 8 Jul 2002 11:42:05 -0400
Message-ID: <7b9a9eaaf34e6773065104024b7696c2@plan9.bell-labs.com>

> So all the effort to handle ' ' was just for foreign files?

Yes.  And that is the main reason I don't want to trash the
system to support blanks in file names.

-rob

^ permalink raw reply	[flat|nested] 81+ messages in thread
* Re: [9fans] acme question + diffs for kfs, fs and plumbing
@ 2002-07-08 15:42 rob pike, esq.
  0 siblings, 0 replies; 81+ messages in thread
From: rob pike, esq. @ 2002-07-08 15:42 UTC (permalink / raw)
  To: 9fans

> So all the effort to handle ' ' was just for foreign files?

Yes.  And that is the main reason I don't want to trash the
system to support blanks in file names.

-rob



^ permalink raw reply	[flat|nested] 81+ messages in thread
* Re: [9fans] acme question + diffs for kfs, fs and plumbing
@ 2002-07-08 15:18 Fco.J.Ballesteros
  0 siblings, 0 replies; 81+ messages in thread
From: Fco.J.Ballesteros @ 2002-07-08 15:18 UTC (permalink / raw)
  To: 9fans

[-- Attachment #1: Type: text/plain, Size: 61 bytes --]

So all the effort to handle ' ' was just for foreign files?

[-- Attachment #2: Type: message/rfc822, Size: 1265 bytes --]

From: "rob pike, esq." <rob@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] acme question + diffs for kfs, fs and plumbing
Date: Mon, 8 Jul 2002 11:16:57 -0400
Message-ID: <53a4b2914a2d14090c0f2bc46f48ce8a@plan9.bell-labs.com>

You don't want blanks in native files, I promise you.  The kfs changes
(at least) are ill-advised.

-rob

^ permalink raw reply	[flat|nested] 81+ messages in thread
* Re: [9fans] acme question + diffs for kfs, fs and plumbing
@ 2002-07-08 15:16 rob pike, esq.
  0 siblings, 0 replies; 81+ messages in thread
From: rob pike, esq. @ 2002-07-08 15:16 UTC (permalink / raw)
  To: 9fans

You don't want blanks in native files, I promise you.  The kfs changes
(at least) are ill-advised.

-rob



^ permalink raw reply	[flat|nested] 81+ messages in thread
* Re: [9fans] acme question + diffs for kfs, fs and plumbing
@ 2002-07-08 15:10 Fco.J.Ballesteros
  2002-07-08 15:16 ` Lucio De Re
  0 siblings, 1 reply; 81+ messages in thread
From: Fco.J.Ballesteros @ 2002-07-08 15:10 UTC (permalink / raw)
  To: 9fans

> I'm not familiar with ACME's innards, but wouldn't it be more
> consistent to have ACME understand the "?" wild character in the
> tag?  Of course this has other drawbacks, but it strikes me as a good
> starting point for discussion.

??

I would just like an acme window to be able to hold
"/a/b x/d/e/f x"
in its tag line. Currently, it would stop at the first
blank and eat the rest of the file name. I'm not talking
about metacharacters.

I think that a couple of changes in wind.c could do the effect.



^ permalink raw reply	[flat|nested] 81+ messages in thread
* [9fans] acme question + diffs for kfs, fs and plumbing
@ 2002-07-08 14:54 Fco.J.Ballesteros
  2002-07-08 15:05 ` Lucio De Re
  0 siblings, 1 reply; 81+ messages in thread
From: Fco.J.Ballesteros @ 2002-07-08 14:54 UTC (permalink / raw)
  To: 9fans

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="UTF-8", Size: 1113 bytes --]

Could we change the acme tag so that the file name is terminated by
`|' and not by space?  Otherwise I don't know how to let acme edit
files that have blanks on their names (It would eat part of the name).


Now the diffs. I had to make them to let my system handle
blanks on file names; i.e. to
	- let the plumber config know of blanks
	- permit blanks in kfs
	- permit blanks in fs
	- permit blanks in acme tags (I don't include this one).

/sys/lib/plumb/basic:
	- add space as a valid char for file names.
	  eg. '[ a-zA-Z¡-￿0-9_\-./]+' instead of '[ a-zA-Z¡-￿0-9_\-./]+'


Permit blanks in kfs servers:

diff /n/dump/2002/0708/sys/src/cmd/disk/kfs/sub.c sub.c
382c382
< 		if(c <= 040)
---
> 		if(c < 040)
diff /n/dump/2002/0708/sys/src/cmd/disk/kfs/9p2.c 9p2.c
795c795
< 		if((*p & 0xFF) <= 040)
---
> 		if((*p & 0xFF) < 040)

Permit blanks in real file servers:

diff ./port/9p2.c /sys/src/fs/port/9p2.c
155c155
< 		if((*p & 0xFF) <= 040)
---
> 		if((*p & 0xFF) < 040)
diff ./port/sub.c /sys/src/fs/port/sub.c
496c496
< 		if(c <= 040)
---
> 		if(c < 040)



^ permalink raw reply	[flat|nested] 81+ messages in thread
* Re: [9fans] blanks in file names
@ 2002-07-03  8:00 Fco.J.Ballesteros
  2002-07-03 12:00 ` Lucio De Re
  0 siblings, 1 reply; 81+ messages in thread
From: Fco.J.Ballesteros @ 2002-07-03  8:00 UTC (permalink / raw)
  To: 9fans

rog@vitanuova.com :
:  /sys/src/cmd/dossrv
:  /sys/src/cmd/9660srv
:  /sys/src/cmd/tapefs
:  /sys/src/cmd/unix/u9fs
:  /sys/src/cmd/ftpfs
:  	convert "space char" to/from external actual space on create,
:  	walk, wstat, stat and directory reads.

One crazy idea I had was to do that translation in the mount driver.
That way the server would be happy to think that it uses space, and
the client plan 9 program would be happy to see 00A0 or whatever
without confussion with the space character. 

lucio@proxima.alt.za : 
:  What I'm saying, is that I'd like to target a kernel that is entirely
:  delimiter agnostic and promote each user application in the same
:  direction as a long-term project.  In the interim, constructs that
:  cast delimiters in stone should be removed wherever possible.

IMHO, the problem is mostly the user programs and not the kernel.
AFAIK, the kernel is fine if you don't use / and \0 as delimiters
(which seems reasonable to me, although some guys might want to use it too). 

But the tradition that blanks separate arguments is deeply embedded in
user programs, perhaps most notably the shell.

Assume the kernel has changed to use openv[], what would the shell
do to deal with spaces vs 00A0s ?




^ permalink raw reply	[flat|nested] 81+ messages in thread

end of thread, other threads:[~2002-07-14 23:27 UTC | newest]

Thread overview: 81+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-07-09  8:42 [9fans] acme question + diffs for kfs, fs and plumbing Fco.J.Ballesteros
2002-07-09  9:28 ` Lucio De Re
2002-07-09 11:23   ` andrey mirtchovski
2002-07-09 12:05     ` matt
  -- strict thread matches above, loose matches on Subject: below --
2002-07-10 18:27 [9fans] blanks in file names David Gordon Hogan
2002-07-10 20:56 ` arisawa
2002-07-10  8:00 Fco.J.Ballesteros
2002-07-10  7:57 [9fans] acme question + diffs for kfs, fs and plumbing Fco.J.Ballesteros
2002-07-09 12:24 Fco.J.Ballesteros
2002-07-09  9:37 Fco.J.Ballesteros
2002-07-09  8:40 Fco.J.Ballesteros
2002-07-09  7:54 [9fans] blanks in file names Fco.J.Ballesteros
     [not found] ` <Fco.J.Ballesteros@Jul>
2002-07-09 15:23   ` Dave
2002-07-09 15:29   ` [9fans] acme question + diffs for kfs, fs and plumbing Dave
2002-07-10 15:57   ` Dave
2002-07-10 16:02   ` [9fans] blanks in file names Dave
2002-07-10 20:59     ` FJ Ballesteros
2002-07-10 21:51       ` Dave
2002-07-10 22:22         ` Dan Cross
2002-07-10 23:01           ` Dave
2002-07-11  2:00             ` Dan Cross
2002-07-11  6:14               ` Dave
2002-07-11  6:38                 ` Lucio De Re
2002-07-14 18:00                   ` Dave
2002-07-11 13:14                 ` arisawa
2002-07-12 12:28                   ` arisawa
2002-07-11 16:23                 ` Dan Cross
2002-07-11 10:43             ` Ish Rattan
2002-07-14 18:49               ` Dave
2002-07-09  7:50 [9fans] acme question + diffs for kfs, fs and plumbing Fco.J.Ballesteros
2002-07-09  8:15 ` Lucio De Re
2002-07-09  8:42   ` arisawa
2002-07-09  9:21     ` Lucio De Re
2002-07-09  9:43       ` arisawa
2002-07-09 10:36         ` Lucio De Re
2002-07-09 10:54           ` matt
2002-07-09 11:01             ` Liberating the filename (Was: [9fans] acme question + diffs for kfs, fs and plumbing) Lucio De Re
2002-07-09 11:07               ` arisawa
2002-07-11 14:57                 ` Liberating the filename (Was: [9fans] acme question + diffs forkfs, Douglas A. Gwyn
2002-07-09  8:22 ` [9fans] acme question + diffs for kfs, fs and plumbing arisawa
2002-07-09  7:46 Fco.J.Ballesteros
2002-07-09  0:38 okamoto
2002-07-08 16:14 rob pike, esq.
2002-07-08 16:07 rob pike, esq.
2002-07-08 20:58 ` Dave
2002-07-08 22:18   ` arisawa
2002-07-08 16:05 Fco.J.Ballesteros
2002-07-08 16:00 rob pike, esq.
2002-07-08 15:51 Fco.J.Ballesteros
2002-07-08 15:42 rob pike, esq.
2002-07-08 15:18 Fco.J.Ballesteros
2002-07-08 15:16 rob pike, esq.
2002-07-08 15:10 Fco.J.Ballesteros
2002-07-08 15:16 ` Lucio De Re
2002-07-08 14:54 Fco.J.Ballesteros
2002-07-08 15:05 ` Lucio De Re
2002-07-03  8:00 [9fans] blanks in file names Fco.J.Ballesteros
2002-07-03 12:00 ` Lucio De Re
2002-07-03 19:39   ` rob pike, esq.
2002-07-07  4:02     ` Dave
2002-07-07  5:17       ` arisawa
     [not found]         ` <"arisawa@ar.aichi-u.ac.jp"@Jul>
2002-07-07  5:38           ` Dave
2002-07-07  6:04             ` arisawa
2002-07-07  7:16               ` arisawa
2002-07-07 16:11           ` Dave
2002-07-07 16:12           ` Dave
2002-07-09 15:31           ` [9fans] acme question + diffs for kfs, fs and plumbing Dave
2002-07-09 22:15             ` arisawa
2002-07-10 21:58           ` [9fans] blanks in file names Dave
2002-07-10 22:38             ` arisawa
2002-07-10 22:42             ` [9fans] " Jim Choate
2002-07-11  5:08               ` Dave
2002-07-11  5:10           ` [9fans] " Dave
2002-07-14 18:32           ` Dave
2002-07-14 18:51             ` Jim Choate
2002-07-14 23:27             ` arisawa
2002-07-08  9:48       ` Boyd Roberts
2002-07-08 20:22         ` Dave
2002-07-09  8:24           ` Boyd Roberts
2002-07-09 15:25             ` Dave
2002-07-08 23:05         ` Berry Kercheval

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).