These are the first 8 lines of a script.

#! /bin/sh
# Test Script
#

function disp {
echo "$1"
read -rsn1
}

This is what happens when I try to execute it:

$ sudo ./test.sh
[sudo] password for xxxx:
../test.sh: 5: function: not found

../test.sh: 7: read: Illegal option -s
../test.sh: 8: Syntax error: "}" unexpected

I cannot understand the first "function not found" error message, Why?

--
Linux Mint 21.1 kernel version 5.15.0-78-generic Cinnamon 5.6.8

On 8/14/23 16:16, this is what pinnerite wrote:
> These are the first 8 lines of a script.
>
> #! /bin/sh
> # Test Script
> #
>
> function disp {
> echo "$1"
> read -rsn1
> }
>
> This is what happens when I try to execute it:
>
> $ sudo ./test.sh
> [sudo] password for xxxx:
> ./test.sh: 5: function: not found
>
> ./test.sh: 7: read: Illegal option -s
> ./test.sh: 8: Syntax error: "}" unexpected
>
> I cannot understand the first "function not found" error message, Why?
>
>
>
>
Is that a proper way to declare a function? Never seen one in bash shell script, not that it's no possible, just
haven't done it.
--
Linux Mint 21.1 Cinnamon 5.6.8
Al

On 8/14/23 2:16 PM, pinnerite wrote:
> function disp {

Try "function disp() {"

On 8/14/23 2:44 PM, jeorge wrote:
> On 8/14/23 2:16 PM, pinnerite wrote:
>> function disp {
>
> Try "function disp() {"

Heh, meant "disp() {"

Been writing awk scripts and so the "function" part looked right...

On Mon, 14 Aug 2023 14:56:21 -0600
jeorge <someone@invalid.invalid> wrote:

> On 8/14/23 2:44 PM, jeorge wrote:
> > On 8/14/23 2:16 PM, pinnerite wrote:
> >> function disp {
> >
> > Try "function disp() {"
>
> Heh, meant "disp() {"
>
> Been writing awk scripts and so the "function" part looked right...

Correct!

Take a house mark.

Thanks, Alan

--
Linux Mint 21.1 kernel version 5.15.0-78-generic Cinnamon 5.6.8
AMD Phenom II x4 955 CPU 16Gb Dram 2TB Barracuda

On Mon, 14 Aug 2023 16:24:55 -0400
Big Al <Bears@invalid.com> wrote:

> On 8/14/23 16:16, this is what pinnerite wrote:
> > These are the first 8 lines of a script.
> >
> > #! /bin/sh
> > # Test Script
> > #
> >
> > function disp {
> > echo "$1"
> > read -rsn1
> > }
> >
> > This is what happens when I try to execute it:
> >
> > $ sudo ./test.sh
> > [sudo] password for xxxx:
> > ./test.sh: 5: function: not found
> >
> > ./test.sh: 7: read: Illegal option -s
> > ./test.sh: 8: Syntax error: "}" unexpected
> >
> > I cannot understand the first "function not found" error message, Why?
> >
> >
> >
> >
> Is that a proper way to declare a function? Never seen one in bash shell script, not that it's no possible, just
> haven't done it.
> --
> Linux Mint 21.1 Cinnamon 5.6.8
> Al
>

I picked that up from:

https://linuxize.com/post/bash-functions/

and chose the reserved word "function" approach.
After changing to: disp() { ...} as suggested, i quickly got the whole script to run smoothly.

Thanks again to everyone.
Alan

--
Linux Mint 21.1 kernel version 5.15.0-79-generic Cinnamon 5.6.8
AMD Phenom II x4 955 CPU 16Gb Dram 2TB Barracuda

On 8/16/23 4:30 AM, pinnerite wrote:
> I picked that up from:
>
> https://linuxize.com/post/bash-functions/
>
> and chose the reserved word "function" approach.
> After changing to: disp() { ...} as suggested, i quickly got the whole script to run smoothly.

FYI - you could have used the 'function fname {...}' form but you'd need
to change the "shabang" line to be '#!/bin/bash' ; using '#!/bin/sh'
calls dash(1), the bash(1) version of the traditional Bourne shell which
doesn't support the 'function' reserve word, aka a "bashism". Other
shells such as mksh(1) also support the 'function' reserve word form
(with optional '()' after the 'fname') but generally call it out as an
"ignored bashism".

If you find yourself writing more shell scripts you might add
"comp.unix.shell" to your newgroup subscriptions; I've learned quite a
bit following it.

Cheers,
jeorge

On Wed, 16 Aug 2023 07:22:16 -0600
jeorge <someone@invalid.invalid> wrote:

> On 8/16/23 4:30 AM, pinnerite wrote:
> > I picked that up from:
> >
> > https://linuxize.com/post/bash-functions/
> >
> > and chose the reserved word "function" approach.
> > After changing to: disp() { ...} as suggested, i quickly got the whole script to run smoothly.
>
> FYI - you could have used the 'function fname {...}' form but you'd need
> to change the "shabang" line to be '#!/bin/bash' ; using '#!/bin/sh'
> calls dash(1), the bash(1) version of the traditional Bourne shell which
> doesn't support the 'function' reserve word, aka a "bashism". Other
> shells such as mksh(1) also support the 'function' reserve word form
> (with optional '()' after the 'fname') but generally call it out as an
> "ignored bashism".
>
> If you find yourself writing more shell scripts you might add
> "comp.unix.shell" to your newgroup subscriptions; I've learned quite a
> bit following it.
>
> Cheers,
> jeorge

I have taken your advice and saved this message.

Thank you,

Alan

--
Linux Mint 21.1 kernel version 5.15.0-79-generic Cinnamon 5.6.8
AMD Phenom II x4 955 CPU 16Gb Dram 2TB Barracuda