From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: [9fans] acme question + diffs for kfs, fs and plumbing
Date: Mon, 8 Jul 2002 16:54:24 +0200 [thread overview]
Message-ID: <037f0a35d7e0a3fffada61950c73786d@plan9.escet.urjc.es> (raw)
[-- 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)
next reply other threads:[~2002-07-08 14:54 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-08 14:54 Fco.J.Ballesteros [this message]
2002-07-08 15:05 ` Lucio De Re
2002-07-08 15:10 Fco.J.Ballesteros
2002-07-08 15:16 ` Lucio De Re
2002-07-08 15:16 rob pike, esq.
2002-07-08 15:18 Fco.J.Ballesteros
2002-07-08 15:42 rob pike, esq.
2002-07-08 15:51 Fco.J.Ballesteros
2002-07-08 16:00 rob pike, esq.
2002-07-08 16:05 Fco.J.Ballesteros
2002-07-08 16:07 rob pike, esq.
2002-07-08 20:58 ` Dave
2002-07-08 22:18 ` arisawa
2002-07-08 16:14 rob pike, esq.
2002-07-09 0:38 okamoto
2002-07-09 7:46 Fco.J.Ballesteros
2002-07-09 7:50 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
[not found] ` <"arisawa@ar.aichi-u.ac.jp"@Jul>
2002-07-09 15:31 ` Dave
2002-07-09 22:15 ` arisawa
2002-07-09 8:22 ` arisawa
2002-07-09 8:40 Fco.J.Ballesteros
2002-07-09 8:42 Fco.J.Ballesteros
2002-07-09 9:28 ` Lucio De Re
2002-07-09 11:23 ` andrey mirtchovski
2002-07-09 12:05 ` matt
[not found] ` <Fco.J.Ballesteros@Jul>
2002-07-09 15:29 ` Dave
2002-07-10 15:57 ` Dave
2002-07-09 9:37 Fco.J.Ballesteros
2002-07-09 12:24 Fco.J.Ballesteros
2002-07-10 7:57 Fco.J.Ballesteros
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=037f0a35d7e0a3fffada61950c73786d@plan9.escet.urjc.es \
--to=nemo@plan9.escet.urjc.es \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).