[9fans] simple question: multiple rename

[9fans] simple question: multiple rename

[Rudolf Sykora]

Hello,

I realized I cannot come up with a simple solution for the following.
I want to rename all the files whose names end with _g_b to just _g,
e.g. hello_g_b should be renamed to hello_g.
I simply don't know an easy way.
[the opposite way is simple: for(i in *_g) mv $i $i^_b ]
I only think about so complicated ways like

for(i in *_g_b) {
    s = `{sam -d <<EOF <{echo $i} >[2] /dev/null
        1s/(.+)_g/\1
        p
        EOF
        }
    mv $i $s
}

which describes my idea, but doesn't work, actually. (btw. how can one
correct it?)

Thanks
Ruda

Re: [9fans] simple question: multiple rename

[Martin Harriss]

Rudolf Sykora wrote:
> Hello,
>
> I realized I cannot come up with a simple solution for the following.
> I want to rename all the files whose names end with _g_b to just _g,
> e.g. hello_g_b should be renamed to hello_g.
> I simply don't know an easy way.
> [the opposite way is simple: for(i in *_g) mv $i $i^_b ]
> I only think about so complicated ways like
>
> for(i in *_g_b) {
>     s = `{sam -d <<EOF <{echo $i} >[2] /dev/null
>         1s/(.+)_g/\1
>         p
>         EOF
>         }
>     mv $i $s
> }
>
> which describes my idea, but doesn't work, actually. (btw. how can one
> correct it?)
>
> Thanks
> Ruda
>

sed is your friend:

s=`{ echo $i | sed -e 's/_g_b/_g/' }


Martin

Re: [9fans] simple question: multiple rename

[Rudolf Sykora]

> sed is your friend:
>
> s=`{ echo $i | sed -e 's/_g_b/_g/' }
>
>
> Martin

Oh yes, that's it.
Thanks
Ruda

Re: [9fans] simple question: multiple rename

[Rudolf Sykora]

Hello,
Still wonder, what's the right way to make the following work:

This is ok:

sam -d <<EOF <{echo $i} >[2] /dev/null
        1s/(.+)_g/\1
        p
        EOF

but now I want it all be inside `{}, like

s = `{sam -d <<EOF <{echo $i} >[2] /dev/null
        1s/(.+)_g/\1
        p
        EOF
       }

which doesn't work. I tried several ways, but unsuccessfully. Anyway,
I guess it should be easy...

Thanks
Ruda

Re: [9fans] simple question: multiple rename

[Russ Cox]

On Mon, Jun 8, 2009 at 12:50 AM, Rudolf Sykora<rudolf.sykora@gmail.com> wrote:
> Hello,
> Still wonder, what's the right way to make the following work:

The right way is

s=`{echo $i | sed 's/(.+)_g/\1/'}.

> s = `{sam -d <<EOF <{echo $i} >[2] /dev/null
>        1s/(.+)_g/\1
>        p
>        EOF
>       }

If you must use sam, the right way is

s=`{echo '1s/(.+)_g/
p' | sam -d <{echo $i} >[2]/dev/null }

If you must use here docs, the way that works is

s=`{sam -d <<EOF <{echo $i} >[2]/dev/null}
1s/(.+)_g/\1
p
EOF

Russ

Re: [9fans] simple question: multiple rename

[Martin Neubauer]

Hello Ruda,

Due to the peculiarities of here documents in rc the following:
> s = `{sam -d <<EOF <{echo $i} >[2] /dev/null
>         1s/(.+)_g/\1
>         p
>         EOF
>        }
should be written as:
s = `{sam -d <<EOF <{echo $i} >[2] /dev/null}
	...
	EOF

Hope that helps,
	Martin

Re: [9fans] simple question: multiple rename

[Rudolf Sykora]

> should be written as:
> s = `{sam -d <<EOF <{echo $i} >[2] /dev/null}
>        ...
>        EOF
>
> Hope that helps,
>        Martin

OK, now I see. The } was at the wrong place...
Thanks Martin
thanks Russ, too.

Ruda

Re: [9fans] simple question: multiple rename

[roger peppe]

2009/6/8 Russ Cox <rsc@swtch.com>
> On Mon, Jun 8, 2009 at 12:50 AM, Rudolf Sykora<rudolf.sykora@gmail.com> wrote:
> > Hello,
> > Still wonder, what's the right way to make the following work:
>
> The right way is
>
> s=`{echo $i | sed 's/(.+)_g/\1/'}.

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)

Re: [9fans] simple question: multiple rename

[erik quanstrom]

> 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

Re: [9fans] simple question: multiple rename

[Ethan Grammatikidis]

On Tue, 16 Jun 2009 08:00:44 -0400
erik quanstrom <quanstro@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:

On-disk filename:
	Program Files
9fat represents this to plan 9 processes as:
	Program~Files

To pick an extreme (and fictional) example:
on-disk:
The Evolution of Conciousness in the Breakdown of the Bicameral Mind.doc
translated:
The~Evolution~of~Conciousness~in~the~Breakdown~of~the~Bicameral~Mind.doc
or
The]Evolution]of]Conciousness]in]the]Breakdown]of]the]Bicameral]Mind.doc
etc.

It would be great if the substitute character could be one not special to regexps.


Un*x seems a harder issue since no character is actually illegal, but I notice many ASCII control characters are not at all special to plan 9 or drawterm and are extremely unlikely to be present in a un*x filename. Vertical tab, perhaps; control-K. For that matter this trick could be used for Windows filesystems too, I'm quite sure control-chars are unacceptable there.


--
Ethan Grammatikidis
The lyf so short, the craft so long to lerne. -- Chaucer

Re: [9fans] simple question: multiple rename

[erik quanstrom]

> So what happens when you drawterm from a un*x box or access a VFAT partition?

nothing.  i'm running ken's fs, so from drawterm i have

	; echo > 'silly file'
	; lc silly*
	'silly file'
	; cd /tmp
	; echo > 'silly file'
	silly file: rc: can't open: 'silly file' create/wstat -- bad character in file name

> Un*x seems a harder issue since no character is actually illegal,

\0 is illegal.  well, not so much illegal as impossible to specify.
(wide characters notwithstanding.)

- erik

Re: [9fans] simple question: multiple rename

[Russ Cox]

the easiest thing to do is not use spaces in
your file names, even if others do in theirs.
most people take that approach, even on unix,
and it works fine.

if you are worried about names with spaces
and want to make a script more robust, then
the simplest option is to set ifs='
'
while you are manipulating the file names
with `{} commands.  spaces may be allowed
but newlines most certainly are not.  i keep
nl='
'
in my profile specifically so i can say ifs=$nl.

> using ws in filenames is a fossil-only problem;
> kfs, cwfs and ken's fs won't allow it.

gee, i'm pretty sure i read somewhere that
plan 9 lets any program be a file server ...

>> So what happens when you drawterm from a un*x box or access a VFAT partition?
>
> nothing.  i'm running ken's fs, so from drawterm ...

the question (quoted) was about talking to non-plan 9
file systems, i.e. a linux or windows /mnt/term or
a dossrv disk.

if you are trying to disallow space you'd have
to fiddle with every file server you could possibly
talk to, or you'd have to edit the kernel.
the barn door has been open for a decade.
it's very late to be talking about closing it.
http://swtch.com/cgi-bin/plan9history.cgi?f=1999/0323/port/chan.c;v=diff;e=1

russ

Re: [9fans] simple question: multiple rename

[erik quanstrom]

> if you are trying to disallow space you'd have
> to fiddle with every file server you could possibly
> talk to, or you'd have to edit the kernel.
> the barn door has been open for a decade.

my point was only that i agree with roger; spaces in
filenames are a pain and it would be best not
to let them on the fileserver.  (we're allowed to
talk about "the fileserver", aren't we?  even if
there are technically many of them?)

> it's very late to be talking about closing it.
> http://swtch.com/cgi-bin/plan9history.cgi?f=1999/0323/port/chan.c;v=diff;e=1

is your point that old mistakes should never
be fixed?

- erik

Re: [9fans] simple question: multiple rename

[erik quanstrom]

> >The Evolution of Conciousness in the Breakdown of the Bicameral Mind.doc
>
> it's not worth worrying about for that book (i think it's `Origin' not `Evolution')
> i am astounded it keeps resurfacing.

those crazy nebraskans.

- erik

Re: [9fans] simple question: multiple rename

[Charles Forsyth]

>The Evolution of Conciousness in the Breakdown of the Bicameral Mind.doc

it's not worth worrying about for that book (i think it's `Origin' not `Evolution')
i am astounded it keeps resurfacing.

Re: [9fans] simple question: multiple rename

[john]

> On Tue, 16 Jun 2009 08:00:44 -0400
> erik quanstrom <quanstro@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

Re: [9fans] simple question: multiple rename

[Tim Newsham]

> 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.

In inferno (at least in acme-sac) the spaces coming from
my native (windows) filesystem are translated into some unicode
underscore type character.  Definitely makes for easier plumbing.
   http://www.thenewsh.com/~newsham/x/machine/inferno-acme-space.jpg

> John

Tim Newsham
http://www.thenewsh.com/~newsham/

Re: [9fans] simple question: multiple rename

[Ethan Grammatikidis]

> > >The Evolution of Conciousness in the Breakdown of the Bicameral Mind.doc
> >
> > it's not worth worrying about for that book (i think it's `Origin' not `Evolution')
> > i am astounded it keeps resurfacing.
>
> those crazy nebraskans.

Don't mind me I'm just quoting Hitchhiker's Guide to the Galaxy. ^.^; I think you're right, it's Origin not Evolution.

--
Ethan Grammatikidis
The lyf so short, the craft so long to lerne. -- Chaucer

Re: [9fans] simple question: multiple rename

[Ethan Grammatikidis]

On Tue, 16 Jun 2009 08:52:43 -0400
erik quanstrom <quanstro@quanstro.net> wrote:

> > So what happens when you drawterm from a un*x box or access a VFAT partition?
>
> nothing.  i'm running ken's fs, so from drawterm i have
>
> 	; echo > 'silly file'
> 	; lc silly*
> 	'silly file'
> 	; cd /tmp
> 	; echo > 'silly file'
> 	silly file: rc: can't open: 'silly file' create/wstat -- bad character in file name
>
> > Un*x seems a harder issue since no character is actually illegal,
>
> \0 is illegal.  well, not so much illegal as impossible to specify.
> (wide characters notwithstanding.)

I forgot, / is actually illegal. I'm almost (but not quite) certain that \0 is legal, and if I understand my emacs correctly you may be able to type it as ctrl-space. It displays as ^@ in emacs.


--
Ethan Grammatikidis
The lyf so short, the craft so long to lerne. -- Chaucer

Re: [9fans] simple question: multiple rename

[erik quanstrom]

> I forgot, / is actually illegal. I'm almost (but not quite) certain that \0 is legal, and if I understand my emacs correctly you may be able to type it as ctrl-space. It displays as ^@ in emacs.
>

what system call do you use to create a file with \0 in the name?
i'm not really keeping up, but last i checked creat doesn't take
a filename length, and therefore the null will terminate the string.

- erik

Re: [9fans] simple question: multiple rename

[Ethan Grammatikidis]

On Tue, 16 Jun 2009 11:55:42 -0400
john@csplan9.rit.edu wrote:

> > On Tue, 16 Jun 2009 08:00:44 -0400
> > erik quanstrom <quanstro@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.

trfs sounds like the tool for the job alright. Will get it as soon as I can.

--
Ethan Grammatikidis
The lyf so short, the craft so long to lerne. -- Chaucer

Re: [9fans] simple question: multiple rename

[Ethan Grammatikidis]

On Tue, 16 Jun 2009 19:01:43 -0400
erik quanstrom <quanstro@coraid.com> wrote:

> > I forgot, / is actually illegal. I'm almost (but not quite) certain that \0 is legal, and if I understand my emacs correctly you may be able to type it as ctrl-space. It displays as ^@ in emacs.
> >
>
> what system call do you use to create a file with \0 in the name?
> i'm not really keeping up, but last i checked creat doesn't take
> a filename length, and therefore the null will terminate the string.
>
> - erik
>

Ah you're right there.


--
Ethan Grammatikidis
The lyf so short, the craft so long to lerne. -- Chaucer

Re: [9fans] simple question: multiple rename

[John Floren]

On Tue, Jun 16, 2009 at 4:01 PM, erik quanstrom <quanstro@coraid.com> wrote:
>
> > I forgot, / is actually illegal. I'm almost (but not quite) certain that \0 is legal, and if I understand my emacs correctly you may be able to type it as ctrl-space. It displays as ^@ in emacs.
> >
>
> what system call do you use to create a file with \0 in the name?
> i'm not really keeping up, but last i checked creat doesn't take
> a filename length, and therefore the null will terminate the string.
>
> - erik
>

According to intro(5), \0 is illegal in a 9P text string. "The NUL
character is illegal in all text strings in 9P, and is therefore
excluded from file names, user names, and so on." I'm assuming from
this that Thou Shall Not Use NUL In Filenames.


John
--
"I've tried programming Ruby on Rails, following TechCrunch in my RSS
reader, and drinking absinthe. It doesn't work. I'm going back to C,
Hunter S. Thompson, and cheap whiskey." -- Ted Dziuba

Re: [9fans] simple question: multiple rename

[erik quanstrom]

On Thu Jun 18 18:55:30 EDT 2009, slawmaster@gmail.com wrote:
> On Tue, Jun 16, 2009 at 4:01 PM, erik quanstrom <quanstro@coraid.com> wrote:
> >
> > > I forgot, / is actually illegal. I'm almost (but not quite) certain that \0 is legal, and if I understand my emacs correctly you may be able to type it as ctrl-space. It displays as ^@ in emacs.
> > >
> >
> > what system call do you use to create a file with \0 in the name?
> > i'm not really keeping up, but last i checked creat doesn't take
> > a filename length, and therefore the null will terminate the string.
> >
> > - erik
> >
>
> According to intro(5), \0 is illegal in a 9P text string. "The NUL
> character is illegal in all text strings in 9P, and is therefore
> excluded from file names, user names, and so on." I'm assuming from
> this that Thou Shall Not Use NUL In Filenames.

note the spelling of creat.  intro(5) does not apply to unix.

- erik

Re: [9fans] simple question: multiple rename

[Francisco J Ballesteros]

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, john@csplan9.rit.edu escribió:

>> On Tue, 16 Jun 2009 08:00:44 -0400
>> erik quanstrom <quanstro@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]