User:Riviera/Go fish - Revision history

Riviera at 15:03, 22 December 2023

2023-12-22T15:03:04Z

← Older revision		Revision as of 17:03, 22 December 2023
Line 1:		Line 1:
			<includeonly>==Go Fish==</includeonly>
	<blockquote>		<blockquote>

Line 8:		Line 9:
	The shell is a computer programme which launches other programmes. This efficient, textual method of interacting with a computer raises practical and ethical questions. On a practical level the question arises as to which shell to choose from. <tt>bash</tt> is the default login shell on Linux distributions such as Debian and Rasbian. However, it is possible to choose a different shell. This choice leads to a discussion of the ethical issue of accessibility. A feature of this discussion involves unpacking the relationship between norms and defaults. In this wiki page I outline some implications of switching to a shell other than <tt>bash</tt> by way of several examples. I describe why I have chosen to use one shell, rather than another shell and argue in favour of <tt>fish</tt> as a default shell. Overall I argue that shell scripting (with <tt>fish</tt> or bash) could be an effective way in which to activate Radio Worm's sonic archive.		The shell is a computer programme which launches other programmes. This efficient, textual method of interacting with a computer raises practical and ethical questions. On a practical level the question arises as to which shell to choose from. <tt>bash</tt> is the default login shell on Linux distributions such as Debian and Rasbian. However, it is possible to choose a different shell. This choice leads to a discussion of the ethical issue of accessibility. A feature of this discussion involves unpacking the relationship between norms and defaults. In this wiki page I outline some implications of switching to a shell other than <tt>bash</tt> by way of several examples. I describe why I have chosen to use one shell, rather than another shell and argue in favour of <tt>fish</tt> as a default shell. Overall I argue that shell scripting (with <tt>fish</tt> or bash) could be an effective way in which to activate Radio Worm's sonic archive.

	=<tt>fish</tt> in practice =		<noinclude>=<tt>fish</tt> in practice =</noinclude>
			<includeonly>===<tt>fish</tt> in practice ===</includeonly>

	<tt>fish</tt> (https://fishshell.com/) has many features that other shells do not have. This includes enhanced autocompletion, a different way of scripting, improved syntax highlighting and idiosyncratic configuration. Three quarters of these features make it easier to get started with using the command line to interface with the computer. In implementing a different scripting language to <tt>bash</tt>, <tt>fish</tt> scripts pose a hurdle relating to interoperability. One must have access to a working installation of the software to run the script and often this is not the case by default.		<tt>fish</tt> (https://fishshell.com/) has many features that other shells do not have. This includes enhanced autocompletion, a different way of scripting, improved syntax highlighting and idiosyncratic configuration. Three quarters of these features make it easier to get started with using the command line to interface with the computer. In implementing a different scripting language to <tt>bash</tt>, <tt>fish</tt> scripts pose a hurdle relating to interoperability. One must have access to a working installation of the software to run the script and often this is not the case by default.

	<tt>fish</tt> departs from it's normative counterpart <tt>bash</tt> in both helpful and obscure ways. Firstly, there is no file such as <tt>.fishrc</tt>. Instead <tt>fish</tt> keeps configuration data in various user-specific and site-wide configuration files. Extending the functional capabilities of the shell involves adding scripts under <tt>~/.config/fish/functions/</tt>. Command expansion is written differently. For more examples, see [https://fishshell.com/docs/current/fish_for_bash_users.html fish for bash users].		<tt>fish</tt> departs from it's normative counterpart <tt>bash</tt> in both helpful and obscure ways. Firstly, there is no file such as <tt>.fishrc</tt>. Instead <tt>fish</tt> keeps configuration data in various user-specific and site-wide configuration files. Extending the functional capabilities of the shell involves adding scripts under <tt>~/.config/fish/functions/</tt>. Command expansion is written differently. For more examples, see [https://fishshell.com/docs/current/fish_for_bash_users.html fish for bash users].

	== Going Fishing: A Syntax Highlighter ==		<noinclude>==Going Fishing: A Syntax Highlighter ==</noinclude>
			<includeonly>====Going Fishing: A Syntax Highlighter====</includeonly>
	Below are two fish scripts, the second works in tandem with the first. The first function, <tt>highlight</tt>, utilises the <tt>sed</tt> command to edit HTML snippets generated by Emacs' Org Mode's HTML export backend. The second script works by calling the <tt>highlight</tt> function several times on the same file. Really this should be a single script, but I cannot figure out how to execute <tt>sed</tt> this many times in a row...		Below are two fish scripts, the second works in tandem with the first. The first function, <tt>highlight</tt>, utilises the <tt>sed</tt> command to edit HTML snippets generated by Emacs' Org Mode's HTML export backend. The second script works by calling the <tt>highlight</tt> function several times on the same file. Really this should be a single script, but I cannot figure out how to execute <tt>sed</tt> this many times in a row...

	=== <tt>higlight.fish</tt> ===		<noinclude>===<tt>higlight.fish</tt>===</noinclude>
			<includeonly>=====<tt>higlight.fish</tt>=====</includeonly>
	<div style="font-family: Monospace; background-color: #dbe6f0;"><span style="color:teal">#</span><span style="color:teal">! /usr/bin/fish</span>		<div style="font-family: Monospace; background-color: #dbe6f0;"><span style="color:teal">#</span><span style="color:teal">! /usr/bin/fish</span>
	<span style="color:green">function</span> <span style="color:yellow">highlight</span> <span style="org-negation-char">-d</span> <span style="color:olive">"Highlight HTML code"</span> <span style="org-negation-char">-a</span> file		<span style="color:green">function</span> <span style="color:yellow">highlight</span> <span style="org-negation-char">-d</span> <span style="color:olive">"Highlight HTML code"</span> <span style="org-negation-char">-a</span> file
Line 98:		Line 103:


	===<tt>higlight_all.fish</tt> ===		<noinclude>===<tt>higlight_all.fish</tt>===</noinclude>
			<includeonly>=====<tt>higlight_all.fish</tt>=====</includeonly>
	<div style="font-family: Monospace; background-color: #dbe6f0;"><span style="color:teal">#</span><span style="color:teal">! /usr/bin/fish</span>		<div style="font-family: Monospace; background-color: #dbe6f0;"><span style="color:teal">#</span><span style="color:teal">! /usr/bin/fish</span>
	<span style="color:green">function</span> <span style="color:yellow">highlight_all</span> <span style="org-negation-char">-d</span> <span style="color:olive">"Call the highlight command several times"</span> <span style="org-negation-char">-a</span> file		<span style="color:green">function</span> <span style="color:yellow">highlight_all</span> <span style="org-negation-char">-d</span> <span style="color:olive">"Call the highlight command several times"</span> <span style="org-negation-char">-a</span> file

Riviera: /* Advantages of fish */

2023-10-01T19:01:24Z

Advantages of fish

← Older revision		Revision as of 21:01, 1 October 2023
Line 8:		Line 8:
	The shell is a computer programme which launches other programmes. This efficient, textual method of interacting with a computer raises practical and ethical questions. On a practical level the question arises as to which shell to choose from. <tt>bash</tt> is the default login shell on Linux distributions such as Debian and Rasbian. However, it is possible to choose a different shell. This choice leads to a discussion of the ethical issue of accessibility. A feature of this discussion involves unpacking the relationship between norms and defaults. In this wiki page I outline some implications of switching to a shell other than <tt>bash</tt> by way of several examples. I describe why I have chosen to use one shell, rather than another shell and argue in favour of <tt>fish</tt> as a default shell. Overall I argue that shell scripting (with <tt>fish</tt> or bash) could be an effective way in which to activate Radio Worm's sonic archive.		The shell is a computer programme which launches other programmes. This efficient, textual method of interacting with a computer raises practical and ethical questions. On a practical level the question arises as to which shell to choose from. <tt>bash</tt> is the default login shell on Linux distributions such as Debian and Rasbian. However, it is possible to choose a different shell. This choice leads to a discussion of the ethical issue of accessibility. A feature of this discussion involves unpacking the relationship between norms and defaults. In this wiki page I outline some implications of switching to a shell other than <tt>bash</tt> by way of several examples. I describe why I have chosen to use one shell, rather than another shell and argue in favour of <tt>fish</tt> as a default shell. Overall I argue that shell scripting (with <tt>fish</tt> or bash) could be an effective way in which to activate Radio Worm's sonic archive.

	= ~~Advantages of~~ <tt>fish</tt> =		=<tt>fish</tt> in practice =
	<tt>fish</tt> (https://fishshell.com/) has many features that other shells do not have. This includes enhanced autocompletion, a different way of scripting, improved syntax highlighting and idiosyncratic configuration. Three quarters of these features make it easier to get started with using the command line to interface with the computer. In implementing a different scripting language to <tt>bash</tt>, <tt>fish</tt> ~~takes some getting used~~ to. ~~Firstly there~~ is ~~no file such as <tt>.fishrc</tt>. Instead <tt>fish</tt> keeps configuration data in various user-specific and site-wide configuration files. Extending the functional capabilities of~~ the ~~shell involves adding scripts under <tt>~/.config/fish/functions/</tt>~~.		<tt>fish</tt> (https://fishshell.com/) has many features that other shells do not have. This includes enhanced autocompletion, a different way of scripting, improved syntax highlighting and idiosyncratic configuration. Three quarters of these features make it easier to get started with using the command line to interface with the computer. In implementing a different scripting language to <tt>bash</tt>, <tt>fish</tt> scripts pose a hurdle relating to interoperability. One must have access to a working installation of the software to run the script and often this is not the case by default.

	== ~~Example One~~: A Syntax Highlighter ==		<tt>fish</tt> departs from it's normative counterpart <tt>bash</tt> in both helpful and obscure ways. Firstly, there is no file such as <tt>.fishrc</tt>. Instead <tt>fish</tt> keeps configuration data in various user-specific and site-wide configuration files. Extending the functional capabilities of the shell involves adding scripts under <tt>~/.config/fish/functions/</tt>. Command expansion is written differently. For more examples, see [https://fishshell.com/docs/current/fish_for_bash_users.html fish for bash users].

			== Going Fishing: A Syntax Highlighter ==
	Below are two fish scripts, the second works in tandem with the first. The first function, <tt>highlight</tt>, utilises the <tt>sed</tt> command to edit HTML snippets generated by Emacs' Org Mode's HTML export backend. The second script works by calling the <tt>highlight</tt> function several times on the same file. Really this should be a single script, but I cannot figure out how to execute <tt>sed</tt> this many times in a row...		Below are two fish scripts, the second works in tandem with the first. The first function, <tt>highlight</tt>, utilises the <tt>sed</tt> command to edit HTML snippets generated by Emacs' Org Mode's HTML export backend. The second script works by calling the <tt>highlight</tt> function several times on the same file. Really this should be a single script, but I cannot figure out how to execute <tt>sed</tt> this many times in a row...

Riviera: /* higlight.fish */

2023-10-01T18:27:32Z

higlight.fish

@@ Line 6: / Line 6: @@
 </blockquote>
-The shell is a computer programme which launches other programmes. This efficient, textual method of interacting with a computer raises practical and ethical questions. On a practical level the question arises as to which shell to choose from. <tt>bash</tt> is the default login shell on linux distributions such as Debian and Rasbian. However, it is possible to choose a different shell. This choice leads to a discussion of the ethical issue of accessibility. A feature of this discussion involves unpacking the relationship between norms and defaults. In this wiki page I outline  some implications of switching to a shell other than <tt>bash</tt> by way of several examples. I describe why I have chosen to use one shell, rather than another shell and argue in favour of <tt>fish</tt> as a default shell. Overall I argue that shell scripting (with <tt>fish</tt> or bash) could be an effective way in which to activate Radio Worm's sonic archive.
+The shell is a computer programme which launches other programmes. This efficient, textual method of interacting with a computer raises practical and ethical questions. On a practical level the question arises as to which shell to choose from. <tt>bash</tt> is the default login shell on Linux distributions such as Debian and Rasbian. However, it is possible to choose a different shell. This choice leads to a discussion of the ethical issue of accessibility. A feature of this discussion involves unpacking the relationship between norms and defaults. In this wiki page I outline  some implications of switching to a shell other than <tt>bash</tt> by way of several examples. I describe why I have chosen to use one shell, rather than another shell and argue in favour of <tt>fish</tt> as a default shell. Overall I argue that shell scripting (with <tt>fish</tt> or bash) could be an effective way in which to activate Radio Worm's sonic archive.
 = Advantages of <tt>fish</tt> =
-<tt>fish</tt> (https://fishshell.com/) has many features that other shells do not have. This includes enhanced autocompletion, a different way of scripting, improved syntax highlighting and idiosyncratic configuration. Three quarters of these features make it easier to get started with using the command line to interface with the computer. In implementing a different scripting language to <tt>bash</tt>, <tt>fish</tt> takes some getting used to. Firstly there is no file such as <tt>.fishrc</tt>. Instead <tt>fish</tt> keeps configuration data in various user-specific and site-wide configuration files. It's easy to extend the functional capabilities of the shell by adding scripts under <tt>~/.config/fish/functions/</tt>.
+<tt>fish</tt> (https://fishshell.com/) has many features that other shells do not have. This includes enhanced autocompletion, a different way of scripting, improved syntax highlighting and idiosyncratic configuration. Three quarters of these features make it easier to get started with using the command line to interface with the computer. In implementing a different scripting language to <tt>bash</tt>, <tt>fish</tt> takes some getting used to. Firstly there is no file such as <tt>.fishrc</tt>. Instead <tt>fish</tt> keeps configuration data in various user-specific and site-wide configuration files. Extending the functional capabilities of the shell involves adding scripts under <tt>~/.config/fish/functions/</tt>.
 == Example One: A Syntax Highlighter ==
@@ Line 20: / Line 20: @@
      <span style="color:purple">sed</span> -i <span style="color:olive">'s/&lt;pre/&lt;div/'</span> <span style="color:olive">$</span><span style="color:orange">argv</span>;
      <span style="color:purple">sed</span> -i <span style="color:olive">'s/&lt;\/pre&gt;/&lt;\/div&gt;/'</span> <span style="color:olive">$</span><span style="color:orange">argv</span>;
-     <span style="color:purple">sed</span> -i <span style="color:olive">'s/style=/style=/'</span> <span style="color:olive">$</span><span style="color:orange">argv</span>;
+     <span style="color:purple">sed</span> -i <span style="color:olive">'s/class=/style=/'</span> <span style="color:olive">$</span><span style="color:orange">argv</span>;
      <span style="color:purple">sed</span> -i -E <span style="color:olive">'s/"src src-<nowiki>[[:alpha:]]</nowiki>*"/"font-family: Monospace; background-color: #dbe6f0;"/'</span> <span style="color:olive">$</span><span style="color:orange">argv</span>;
      <span style="color:purple">sed</span> -i <span style="color:olive">'s/"color:teal"/"color:teal"/'</span> <span style="color:olive">$</span><span style="color:orange">argv</span>;
@@ Line 32: / Line 32: @@
 <span style="color:green">end</span>
 </div>
 The <tt>s</tt> command in <tt>sed</tt> language is a shorthand for '''substitute'''. <tt>s</tt> commands are of the form
 <pre>
@@ Line 38: / Line 37: @@
 </pre>
-With the <tt>s</tt> command, <tt>sed</tt> queries a text file for the presence of a particular string, or regular expression, and replaces what is found with user defined text. In the above example, classes of HTML elements are restyled with colour to highlight different parts of the script.
+With the <tt>s</tt> command, <tt>sed</tt> queries a text file for the presence of a particular string, or regular expression, and replaces what is found with user defined text. In the above example, classes of HTML elements are restyled with colour to highlight different parts of the script. Represented as a table, the changes are:
-=== <tt>higlight_all.fish</tt> ===
+===<tt>higlight_all.fish</tt> ===
 <div style="font-family: Monospace; background-color: #dbe6f0;"><span style="color:teal">#</span><span style="color:teal">! /usr/bin/fish</span>
 <span style="color:green">function</span> <span style="color:yellow">highlight_all</span> <span style="org-negation-char">-d</span> <span style="color:olive">"Call the highlight command several times"</span> <span style="org-negation-char">-a</span> file
@@ Line 51: / Line 107: @@
 </div>
-This command calls <tt>highlight</tt> multiple times to ensure the script runs to completion. I could improve this such that only one script is required. I'm curious as to whether shell scripts can accept user input.
+This command calls <tt>highlight</tt> multiple times to ensure the script runs to completion. I could improve this such that only one script is required.

Riviera at 17:08, 1 October 2023

2023-10-01T17:08:29Z

← Older revision		Revision as of 19:08, 1 October 2023
Line 6:		Line 6:
	</blockquote>		</blockquote>

	The shell is a computer programme which launches other programmes. This efficient, textual method of interacting with a computer raises practical and ethical questions. On a practical level the question arises as to which shell to choose from. <tt>bash</tt> is the default login shell on linux distributions such as Debian and Rasbian. However, it is possible to choose a different shell. This choice leads to a discussion of the ethical issue of accessibility. A feature of this discussion involves unpacking the relationship between norms and defaults. In this wiki page I outline some implications of switching to a shell other than <tt>bash</tt> by way of several examples. I describe why I have chosen to use one shell, rather than another shell and argue in favour of <tt>fish</tt> as a default shell.		The shell is a computer programme which launches other programmes. This efficient, textual method of interacting with a computer raises practical and ethical questions. On a practical level the question arises as to which shell to choose from. <tt>bash</tt> is the default login shell on linux distributions such as Debian and Rasbian. However, it is possible to choose a different shell. This choice leads to a discussion of the ethical issue of accessibility. A feature of this discussion involves unpacking the relationship between norms and defaults. In this wiki page I outline some implications of switching to a shell other than <tt>bash</tt> by way of several examples. I describe why I have chosen to use one shell, rather than another shell and argue in favour of <tt>fish</tt> as a default shell. Overall I argue that shell scripting (with <tt>fish</tt> or bash) could be an effective way in which to activate Radio Worm's sonic archive.

	=A ~~Two-Part~~ Syntax Highlighter =		= Advantages of <tt>fish</tt> =
			<tt>fish</tt> (https://fishshell.com/) has many features that other shells do not have. This includes enhanced autocompletion, a different way of scripting, improved syntax highlighting and idiosyncratic configuration. Three quarters of these features make it easier to get started with using the command line to interface with the computer. In implementing a different scripting language to <tt>bash</tt>, <tt>fish</tt> takes some getting used to. Firstly there is no file such as <tt>.fishrc</tt>. Instead <tt>fish</tt> keeps configuration data in various user-specific and site-wide configuration files. It's easy to extend the functional capabilities of the shell by adding scripts under <tt>~/.config/fish/functions/</tt>.

			== Example One: A Syntax Highlighter ==
	Below are two fish scripts, the second works in tandem with the first. The first function, <tt>highlight</tt>, utilises the <tt>sed</tt> command to edit HTML snippets generated by Emacs' Org Mode's HTML export backend. The second script works by calling the <tt>highlight</tt> function several times on the same file. Really this should be a single script, but I cannot figure out how to execute <tt>sed</tt> this many times in a row...		Below are two fish scripts, the second works in tandem with the first. The first function, <tt>highlight</tt>, utilises the <tt>sed</tt> command to edit HTML snippets generated by Emacs' Org Mode's HTML export backend. The second script works by calling the <tt>highlight</tt> function several times on the same file. Really this should be a single script, but I cannot figure out how to execute <tt>sed</tt> this many times in a row...

	== <tt>higlight.fish</tt> ==		=== <tt>higlight.fish</tt> ===
	<div style="font-family: Monospace; background-color: #dbe6f0;"><span style="color:teal">#</span><span style="color:teal">! /usr/bin/fish</span>		<div style="font-family: Monospace; background-color: #dbe6f0;"><span style="color:teal">#</span><span style="color:teal">! /usr/bin/fish</span>
	<span style="color:green">function</span> <span style="color:yellow">highlight</span> <span style="org-negation-char">-d</span> <span style="color:olive">"Highlight HTML code"</span> <span style="org-negation-char">-a</span> file		<span style="color:green">function</span> <span style="color:yellow">highlight</span> <span style="org-negation-char">-d</span> <span style="color:olive">"Highlight HTML code"</span> <span style="org-negation-char">-a</span> file
Line 37:		Line 40:
	With the <tt>s</tt> command, <tt>sed</tt> queries a text file for the presence of a particular string, or regular expression, and replaces what is found with user defined text. In the above example, classes of HTML elements are restyled with colour to highlight different parts of the script.		With the <tt>s</tt> command, <tt>sed</tt> queries a text file for the presence of a particular string, or regular expression, and replaces what is found with user defined text. In the above example, classes of HTML elements are restyled with colour to highlight different parts of the script.

	== <tt>higlight_all.fish</tt> ==		=== <tt>higlight_all.fish</tt> ===
	<div style="font-family: Monospace; background-color: #dbe6f0;"><span style="color:teal">#</span><span style="color:teal">! /usr/bin/fish</span>		<div style="font-family: Monospace; background-color: #dbe6f0;"><span style="color:teal">#</span><span style="color:teal">! /usr/bin/fish</span>
	<span style="color:green">function</span> <span style="color:yellow">highlight_all</span> <span style="org-negation-char">-d</span> <span style="color:olive">"Call the highlight command several times"</span> <span style="org-negation-char">-a</span> file		<span style="color:green">function</span> <span style="color:yellow">highlight_all</span> <span style="org-negation-char">-d</span> <span style="color:olive">"Call the highlight command several times"</span> <span style="org-negation-char">-a</span> file

Riviera: /* A Two-Part Syntax Highlighter */

2023-10-01T16:45:18Z

A Two-Part Syntax Highlighter

← Older revision		Revision as of 18:45, 1 October 2023
Line 6:		Line 6:
	</blockquote>		</blockquote>

			The shell is a computer programme which launches other programmes. This efficient, textual method of interacting with a computer raises practical and ethical questions. On a practical level the question arises as to which shell to choose from. <tt>bash</tt> is the default login shell on linux distributions such as Debian and Rasbian. However, it is possible to choose a different shell. This choice leads to a discussion of the ethical issue of accessibility. A feature of this discussion involves unpacking the relationship between norms and defaults. In this wiki page I outline some implications of switching to a shell other than <tt>bash</tt> by way of several examples. I describe why I have chosen to use one shell, rather than another shell and argue in favour of <tt>fish</tt> as a default shell.
	=A Two-Part Syntax Highlighter=
	Below are two fish scripts. The first function, <tt>highlight</tt>, utilises the <tt>sed</tt> command to edit HTML snippets generated by Emacs' Org Mode's HTML export backend. The second script works by calling the <tt>highlight</tt> function several times on the same file.		=A Two-Part Syntax Highlighter =
			Below are two fish scripts, the second works in tandem with the first. The first function, <tt>highlight</tt>, utilises the <tt>sed</tt> command to edit HTML snippets generated by Emacs' Org Mode's HTML export backend. The second script works by calling the <tt>highlight</tt> function several times on the same file. Really this should be a single script, but I cannot figure out how to execute <tt>sed</tt> this many times in a row...

	== <tt>higlight.fish</tt> ==		== <tt>higlight.fish</tt> ==
Line 46:		Line 47:
	<span style="color:green">end</span>		<span style="color:green">end</span>
	</div>		</div>

			This command calls <tt>highlight</tt> multiple times to ensure the script runs to completion. I could improve this such that only one script is required. I'm curious as to whether shell scripts can accept user input.

Riviera: Created page with "
In the shell I find a marvelous mess of constellations, nebulae, interstellar gaps, awesome gullies, that provokes in me an indescribable sense of vertigo, as if I am hanging from earth upside down on the brink of infinite space, with terrestrial gravity still holding me by the heels but about to release me any moment. ---- Nancy Mauro-Flude, 2008
=A Two-Part Syntax Highlighter= Below are two fish scripts. The first function, highlight 2023-10-01T15:41:36Z Created page with "<blockquote> In the shell I find a marvelous mess of constellations, nebulae, interstellar gaps, awesome gullies, that provokes in me an indescribable sense of vertigo, as if I am hanging from earth upside down on the brink of infinite space, with terrestrial gravity still holding me by the heels but about to release me any moment. ---- Nancy Mauro-Flude, 2008 </blockquote> =A Two-Part Syntax Highlighter= Below are two fish scripts. The first function, <tt>highlight</..." New page <blockquote> In the shell I find a marvelous mess of constellations, nebulae, interstellar gaps, awesome gullies, that provokes in me an indescribable sense of vertigo, as if I am hanging from earth upside down on the brink of infinite space, with terrestrial gravity still holding me by the heels but about to release me any moment. ---- Nancy Mauro-Flude, 2008 </blockquote> =A Two-Part Syntax Highlighter= Below are two fish scripts. The first function, <tt>highlight</tt>, utilises the <tt>sed</tt> command to edit HTML snippets generated by Emacs' Org Mode's HTML export backend. The second script works by calling the <tt>highlight</tt> function several times on the same file. == <tt>higlight.fish</tt> == <div style="font-family: Monospace; background-color: #dbe6f0;">#! /usr/bin/fish function highlight -d "Highlight HTML code" -a file argparse --name='highlight' 'h/help' -- $argv; sed -i 's/<pre/<div/' $argv; sed -i 's/<\/pre>/<\/div>/' $argv; sed -i 's/style=/style=/' $argv; sed -i -E 's/"src src-<nowiki>[[:alpha:]]</nowiki>*"/"font-family: Monospace; background-color: #dbe6f0;"/' $argv; sed -i 's/"color:teal"/"color:teal"/' $argv; sed -i 's/"color:teal"/"color:teal"/' $argv; sed -i 's/"color:green"/"color:green"/' $argv; sed -i 's/"color:yellow"/"color:yellow"/' $argv; sed -i 's/"color:orange"/"color:orange"/' $argv; sed -i 's/"color:olive"/"color:olive"/' $argv; sed -i 's/"color:gray"/"color:gray"/' $argv; sed -i 's/"color:purple"/"color:purple"/' $argv; end </div> The <tt>s</tt> command in <tt>sed</tt> language is a shorthand for '''substitute'''. <tt>s</tt> commands are of the form <pre> 's/find/replace/' </pre> With the <tt>s</tt> command, <tt>sed</tt> queries a text file for the presence of a particular string, or regular expression, and replaces what is found with user defined text. In the above example, classes of HTML elements are restyled with colour to highlight different parts of the script. == <tt>higlight_all.fish</tt> == <div style="font-family: Monospace; background-color: #dbe6f0;">#! /usr/bin/fish function highlight_all -d "Call the highlight command several times" -a file set -l options (fish_opt -s h -l help) argparse --name='highlight_all' 'h/help' -- $argv; for n in (seq 1 5); highlight $argv; end end </div>