Hi,
On Monday 25 of April 2011 05:36:17 erik quanstrom wrote:
> ; hg diff rfork.c
>
> > hmm. is that right? it's wait3/wait4 that's failing. it shouldn't
> > be necesary to catch SIGCHLD for wait to work. but maybe
> > it is
>
> i take it back. i'd forgotten how quirky unix is these days.
> > i take it back. i'd forgotten how quirky unix is these days.
> > here's the solution. not rc's fault. recompile lib9 and listen1:
> >
> > diff -r 5caa04977471 src/lib9/rfork.c
> > (...)
>
>
> back in 13/05/2009 00:57 i've submitted a different patch for that
> (mail with subject ``[p9p] B
Hi,
>From time to time, the issue of having spaces in file names seems to
come up on this list, mostly in the context of discussions on find, du,
Acme, and trfs(4). All the discussions I've found suggest that file
names with whitespace in them are *legal* on fossil. I'm running a
9atom 9pcf kern
Sometime around, maybe, 2000, I flipped the bit in the frogs table so
spaces were legal in file names, for two reasons: we were seeing
spaces in file names from remote systems and seemed simpler to accept
them than to remap them, and I wanted to know how it would affect
things.
Not all software ha
>
> Not all software has caught up, I suspect. It's only been a decade.
>
my software hasn't. i'm just a philistine.
- erik
> From time to time, the issue of having spaces in file names seems to
> come up on this list, mostly in the context of discussions on find,
> du, Acme, and trfs(4). All the discussions I've found suggest that
> file names with whitespace in them are *legal* on fossil. I'm running
> a 9atom 9pcf
On Tuesday 26 of April 2011 20:42:49 Rob Pike wrote:
> Sometime around, maybe, 2000, I flipped the bit in the frogs table so
> spaces were legal in file names, for two reasons: we were seeing
> spaces in file names from remote systems and seemed simpler to accept
> them than to remap them, and I wa
I still use acme. My solution for spaces in file names is to avoid
them. That might not work for everyone.
-rob
I mostly run acme from inferno (acme-SAC), and live with trfs to take care
of my windows and mac paths. My linux paths are much better behaved, and so
I run from p9p there.
Paul
On Tue, Apr 26, 2011 at 12:31 PM, Rob Pike wrote:
> I still use acme. My solution for spaces in file names is to av
erik quanstrom writes:
> the sources version of fossil does allow spaces in filenames.
I'm hypothesizing that my version of fossil isn't allowing spaces in
file names because the version compiled into the '#//boot/boot/fossil'
in the 9atom 9pcf kernel from the 9atom .iso doesn't allow spaces.
Wo
On Tue Apr 26 22:34:26 EDT 2011, smi...@zenzebra.mv.com wrote:
> erik quanstrom writes:
>
> > the sources version of fossil does allow spaces in filenames.
>
> I'm hypothesizing that my version of fossil isn't allowing spaces in
> file names because the version compiled into the '#//boot/boot/fo
11 matches
Mail list logo
