Re: I've forgotten again how to do this --> 0-100

Re: I've forgotten again how to do this --> 0-100

[Wessel Dankers]

On Wed, 14 Jan 1998, Timothy J Luoma wrote:

> I know this is dumb, and I know I've asked before, and I know I should be  
> able to figure it out.
> 
> Ignorance, expressed, I'll still ask:
> 
> if I want to make a loop to go from 0 to 100, how do I do that?
> 
> for i in 0-100; do
> 	echo $i
> done
> 
> but the "0-100" part is the part I can never remember....

I suggest that you, as a punishment, write it out in full. :-)

--
Wessel Dankers

NOTE: change to PATCH archive

[Timothy J Luoma]

I was thinking of this myself, and someone else mentioned it as well, so I  
went ahead and made the change.

The problem with the previous setup is the the file was in HTML.  It was  
hard to download and even if you did you'd have to convert it back to ASCII.

So I changed it.

1) zsh@peak.org is now subscribed to zsh-workers
	a) you don't have to CC zsh@peak.org.

	b) any post you send to the list which begins with "PATCH:"
		will be archived
		
2) patches will be stored at: http://www.peak.org/zsh/patches
	(note the lowercase of the URL)

3) patches are in ASCII

4) patches are named:
	PostNumber-Subject.txt
	
	The Subject has the spaces removed.  As long as people don't use
	really funky characters (ie !#&^(*@!&$^_ etc) in the Subject:
	we ought to be ok.


I think that's it.

		TjL
		

Re: NOTE: change to PATCH archive

[Timothy J Luoma]

	Author:        Mark Borges <mdb@cdc.noaa.gov>
	Original-Date: 15 Jan 1998 12:00:24 -0700
	Message-ID:    <vk90sh4l6f.fsf@cdc.noaa.gov>

> >> On Thu, 15 Jan 98 12:13:55 -0500,
> >> Timothy J Luoma(TJL) wrote:
>
> TJL> I think that's it.
>
> Not quite. When I click on it I see the dreaded,
>
> ----------------------------------------
> Forbidden
>
> You don't have permission to access
> /zsh/patches/3655-zsh-3.1.2-zefram3:_libzsh_install.txt on this
> server.


DOOH!

See what happens when you only test something out of your own account?!?!?!

Fixed now.

NOTE: that message number (3655) is not correct, I just made one up for  
testing purposes.  Future ones will be right.

TjL