Shell scripts (Wordhole) - Revision history

Riviera at 15:50, 1 November 2023

2023-11-01T15:50:57Z

← Older revision		Revision as of 17:50, 1 November 2023
Line 6:		Line 6:
	end		end
	</syntaxhighlight>		</syntaxhighlight>
			[[Category:Wordhole]]

Riviera at 13:50, 1 November 2023

2023-11-01T13:50:31Z

← Older revision		Revision as of 15:50, 1 November 2023
Line 1:		Line 1:
	Throughout SI #22: Radio Worm - Protocols for an Active Archive, several shell scripts have been made. These are small computer programmes which enhance productivity and make tasks less repetitive. On several occasions we have implemented shell scripts to get things done and probably we will use shell scripts again in the near future. In 'Tools to Fight Boredom: FLOSS and GNU/Linux for artists working in the field of generative music and software art' Marloes de Valk likens shell scripts to a sort of 'glue' capable of binding things together. Throughout SI #22 shell scripts have been used to diverse ends. This ranges from making a podcast generator to downloading files from the internet. From compiling pdf documents with pandoc and weasyprint to manipulating texts with grep, awk and sed. These scripts can be found on the internet via Gitea, on the Wiki and in etherpads. Overall, shell scripting has been more of a distributive practice than a collaborative practice. We have shared algorithms with each other without necessarily writing those algorithms together (i.e. in an Etherpad). Depending on how the shell script is written, a specific shell may or may not be required to execute the code. Primarily we have been using bash, the Bourne Again Shell, and fish, the Friendly Interactive Shell. These shells have subtle differences in syntax; bash often cannot execute fish scripts and vice-versa.		Throughout SI #22: Radio Worm - Protocols for an Active Archive, several shell scripts have been made. These are small computer programmes which enhance productivity and make tasks less repetitive. On several occasions we have implemented shell scripts to get things done and probably we will use shell scripts again in the near future. In 'Tools to Fight Boredom: FLOSS and GNU/Linux for artists working in the field of generative music and software art' Marloes de Valk likens shell scripts to a sort of 'glue' capable of binding things together. Throughout SI #22 shell scripts have been used to diverse ends. This ranges from making a podcast generator to downloading files from the internet. From compiling pdf documents with pandoc and weasyprint to manipulating texts with grep, awk and sed. These scripts can be found on the internet via Gitea, on the Wiki and in etherpads. Overall, shell scripting has been more of a distributive practice than a collaborative practice. We have shared algorithms with each other without necessarily writing those algorithms together (i.e. in an Etherpad). Depending on how the shell script is written, a specific shell may or may not be required to execute the code. Primarily we have been using bash, the Bourne Again Shell, and fish, the Friendly Interactive Shell. These shells have subtle differences in syntax; bash often cannot execute fish scripts and vice-versa. Below is an example of a fish script which, when executed, downloads all episodes of the Laurence Rassel Show.
	~~[[Category~~:~~Wordhole]]~~
			<syntaxhighlight lang="fish">#! /usr/bin/fish
			for n in 01 02 03 04 05 06 07 08 09 (seq 10 17);
			wget (printf 'http://www.publicrec.org/archive/2-01/2-01-014/2-01-014-%s.mp3' $n);
			end
			</syntaxhighlight>

Riviera at 13:38, 1 November 2023

2023-11-01T13:38:05Z

← Older revision		Revision as of 15:38, 1 November 2023
Line 1:		Line 1:
	Throughout SI #22: Radio Worm - Protocols for an Active Archive, several shell scripts have been made. These are small computer programmes which enhance productivity and make tasks less repetitive. On several occasions we have implemented shell scripts to get things done and probably we will use shell scripts again in the near future. In 'Tools to Fight Boredom: FLOSS and GNU/Linux for artists working in the field of generative music and software art' Marloes de Valk likens shell scripts to a sort of 'glue' capable of binding things together. Throughout SI #22 shell scripts have been used to diverse ends. This ranges from making a podcast generator to downloading files from the internet. From compiling pdf documents with pandoc and weasyprint to ~~and~~ manipulating texts with grep, awk and sed. These scripts can be found on the internet via Gitea, on the Wiki and in etherpads. Overall, shell scripting has been more of a distributive practice than a collaborative practice. We have shared algorithms with each other without necessarily writing those algorithms together (i.e. in an Etherpad). Depending on how the shell script is written, a specific shell may or may not be required to execute the code. Primarily we have been using bash, the Bourne Again Shell, and fish, the Friendly Interactive Shell. These shells have subtle differences in syntax; bash often cannot execute fish scripts and vice-versa.		Throughout SI #22: Radio Worm - Protocols for an Active Archive, several shell scripts have been made. These are small computer programmes which enhance productivity and make tasks less repetitive. On several occasions we have implemented shell scripts to get things done and probably we will use shell scripts again in the near future. In 'Tools to Fight Boredom: FLOSS and GNU/Linux for artists working in the field of generative music and software art' Marloes de Valk likens shell scripts to a sort of 'glue' capable of binding things together. Throughout SI #22 shell scripts have been used to diverse ends. This ranges from making a podcast generator to downloading files from the internet. From compiling pdf documents with pandoc and weasyprint to manipulating texts with grep, awk and sed. These scripts can be found on the internet via Gitea, on the Wiki and in etherpads. Overall, shell scripting has been more of a distributive practice than a collaborative practice. We have shared algorithms with each other without necessarily writing those algorithms together (i.e. in an Etherpad). Depending on how the shell script is written, a specific shell may or may not be required to execute the code. Primarily we have been using bash, the Bourne Again Shell, and fish, the Friendly Interactive Shell. These shells have subtle differences in syntax; bash often cannot execute fish scripts and vice-versa.
	[[Category:Wordhole]]		[[Category:Wordhole]]

Riviera at 13:36, 1 November 2023

2023-11-01T13:36:59Z

← Older revision		Revision as of 15:36, 1 November 2023
Line 1:		Line 1:
	Throughout SI #22: Radio Worm - Protocols for an Active Archive, several shell scripts have been made. These are small computer programmes which enhance productivity and make tasks less repetitive. On several occasions we have implemented shell scripts to get things done and probably we will use shell scripts again in the near future. In 'Tools to Fight Boredom: FLOSS and GNU/Linux for artists working in the field of generative music and software art' Marloes de Valk likens shell scripts to a sort of 'glue' capable of binding things together. Throughout SI #22 shell scripts have been used to diverse ends. This ranges from making a podcast generator to downloading files from the internet. From compiling pdf documents with pandoc and weasyprint to and manipulating texts with grep, awk and sed. These scripts can be found on the internet via Gitea, on the Wiki and in etherpads. Overall, shell scripting has been more of a distributive practice than a collaborative practice. We have shared algorithms with each other without necessarily writing those algorithms together (i.e. in an Etherpad). Depending on how the shell script is written, a specific shell may or may not be required to execute the code. Primarily we have been using bash, the Bourne Again Shell, and fish, the Friendly Interactive Shell. These shells have subtle differences in syntax; bash often cannot execute fish scripts and vice-versa.		Throughout SI #22: Radio Worm - Protocols for an Active Archive, several shell scripts have been made. These are small computer programmes which enhance productivity and make tasks less repetitive. On several occasions we have implemented shell scripts to get things done and probably we will use shell scripts again in the near future. In 'Tools to Fight Boredom: FLOSS and GNU/Linux for artists working in the field of generative music and software art' Marloes de Valk likens shell scripts to a sort of 'glue' capable of binding things together. Throughout SI #22 shell scripts have been used to diverse ends. This ranges from making a podcast generator to downloading files from the internet. From compiling pdf documents with pandoc and weasyprint to and manipulating texts with grep, awk and sed. These scripts can be found on the internet via Gitea, on the Wiki and in etherpads. Overall, shell scripting has been more of a distributive practice than a collaborative practice. We have shared algorithms with each other without necessarily writing those algorithms together (i.e. in an Etherpad). Depending on how the shell script is written, a specific shell may or may not be required to execute the code. Primarily we have been using bash, the Bourne Again Shell, and fish, the Friendly Interactive Shell. These shells have subtle differences in syntax; bash often cannot execute fish scripts and vice-versa.
			[[Category:Wordhole]]

Riviera: Created page with "Throughout SI #22: Radio Worm - Protocols for an Active Archive, several shell scripts have been made. These are small computer programmes which enhance productivity and make tasks less repetitive. On several occasions we have implemented shell scripts to get things done and probably we will use shell scripts again in the near future. In 'Tools to Fight Boredom: FLOSS and GNU/Linux for artists working in the field of generative music and software art' Marloes de Valk lik..."

2023-11-01T13:35:59Z

Created page with "Throughout SI #22: Radio Worm - Protocols for an Active Archive, several shell scripts have been made. These are small computer programmes which enhance productivity and make tasks less repetitive. On several occasions we have implemented shell scripts to get things done and probably we will use shell scripts again in the near future. In 'Tools to Fight Boredom: FLOSS and GNU/Linux for artists working in the field of generative music and software art' Marloes de Valk lik..."

New page

Throughout SI #22: Radio Worm - Protocols for an Active Archive, several shell scripts have been made. These are small computer programmes which enhance productivity and make tasks less repetitive. On several occasions we have implemented shell scripts to get things done and probably we will use shell scripts again in the near future. In 'Tools to Fight Boredom: FLOSS and GNU/Linux for artists working in the field of generative music and software art' Marloes de Valk likens shell scripts to a sort of 'glue' capable of binding things together. Throughout SI #22 shell scripts have been used to diverse ends. This ranges from making a podcast generator to downloading files from the internet. From compiling pdf documents with pandoc and weasyprint to and manipulating texts with grep, awk and sed. These scripts can be found on the internet via Gitea, on the Wiki and in etherpads. Overall, shell scripting has been more of a distributive practice than a collaborative practice. We have shared algorithms with each other without necessarily writing those algorithms together (i.e. in an Etherpad). Depending on how the shell script is written, a specific shell may or may not be required to execute the code. Primarily we have been using bash, the Bourne Again Shell, and fish, the Friendly Interactive Shell. These shells have subtle differences in syntax; bash often cannot execute fish scripts and vice-versa.