shell scripting topic

lilbud

This post is more of a forewarning

Don't use climate on the raspberry pi. This program is made to simplify several terminal commands to one or two words, sounds good in theory. But it auto runs and takes up resources. My Pi was sitting idle with climate running and it was at 80 Celsius (176 fahrenheit)

cyperghost

@meleu You can interrupt loops with that.
But I have to test if this is working with keypads also. If yes you can trigger events by keypad press and don't need enter key

In BASIC (afaik) you wrote it like this.... ucase is a function for uppercase characters so you dont use check for "q" and "Q".

Retro: Do loop was introduced in QBasic in 1991, former there were just if-then clauses and the goto/gosub command - really spooky

REM inkey function for basic
REM in anicient basic $ for charstrings is obligatory 
PRINT "Press Q to quit"
DO : LOOP UNTIL UCASE$(INKEY$)="Q"

!/bin/bash
# Demo do show function inkey
inkey() { char="" ; stty -icanon min 0 time 1 ; char=`dd count=1 2>/dev/null` ; }

# ---- main -----
echo "Press some keys and I will show you keybuffer after 3 seconds"
sleep 3 && inkey
echo "You wrote \"$char\""

meleu

@cyperghost be careful using this. It keeps your terminal busy and then you will be unable to input something to a simple read.

Check this script (I just added one single line at the end of your demo):

#!/bin/bash -
inkey() { char="" ; stty -icanon min 0 time 1 ; char=`dd count=1 2>/dev/null` ;}

# ---- main -----
echo "Press some keys and I will show you keybuffer after 3 seconds"
sleep 3 && inkey
echo "You wrote \"$char\""

read -p "Type something: " var

And here is the error I've found:

$ bash inkey.sh
Press some keys and I will show you keybuffer after 3 seconds
asdfgYou wrote "asdfg"
Type something: inkey.sh: linha 10: read: erro de leitura: 0: Resource temporarily unavailable

$ # and it messed my terminal even outside the script, look...

$ read -p "Type something: " var
Type something: -bash: read: erro de leitura: 0: Resource temporarily unavailable

"erro de leitura" (pt_BR) == "reading error" (en)

After this tests I used git to push some commits to one of my repos and when git asked my github username I've got that same error "Resource temporarily unavailable".

The good thing is that you can "fix" your terminal using the reset command (yes, just type reset and then <ENTER>).

I don't know the details of that stty command, but I think it's the responsible for the mess.

Summing up: use that inkey trick very carefully. Maybe performming a reset command after using inkey function is a good idea. :-)

Cheers!

cyperghost

@meleu Wow you are really master meleu

#!/bin/bash
# RESET is mandotary for releasing terminal from being busy
# inkey function demo
inkey() { char="" ; stty -icanon min 0 time 1 ; char=`dd count=1 2>/dev/null` ; }

# ---- main -----

echo "Press some keys and I will show you keybuffer after 3 seconds"
sleep 3
inkey && reset # <-- this is mandotary
echo "You wrote \"$char\""

read -p "Type something: " var
echo $var

I think this function is just a dirty trick. Thanks for looking deeper in. Just did a few simple tests with that.

meleu

@cyperghost talking about indentations in this thread to not messing that other.

@meleu ;) How about the indentations?

it really improved, I just would like to make one little note.

This snippet here

until [[ "${console[idx]}" == "$1" ]]
    do
       idx=$(( $idx + 1 ))
    done

Could be better indented this way:

until [[ "${console[idx]}" == "$1" ]]
do
    idx=$(( $idx + 1 ))
done

It's a more common practice.

I'm glad to see you improving your coding style! :-)

Cheers!

cyperghost

@meleu About your newest ES-termination code.
Is tty is setting the trigger to start the service? Don't get me wrong I thought tty is just the terminal like ssh ;) Can you please explain?

cyperghost

@meleu
Is there no annother approach?
systemd is very complicated?
Can we export a function call to shell that would end ES?
Can we use an alias ... as it can't be used from scripts - is there annother way?

meleu

@cyperghost There are as many approaches as creativity allows. I just tried to find a way to encompass as many use cases as possible. The explanation for how it works can be complex, but the steps to make it work is not.

Using an alias has its limitations, but it's an option.

cyperghost

@meleu Hello brother ;)
Yes I know it's maybe easy for me and you but take a look here
https://retropie.org.uk/forum/topic/12930/
I suggested the first solution (yours)
but it didn't work, so I used the "old" way.....

I bought now one of these mausberry devices to test ;)
It's really hard to test without the device.

AFAIK an alias can't be called within a script. So you may export the bash function with export -f func_call. But how this works? Do you have a clue?

meleu

@cyperghost said in shell scripting topic:

@meleu Hello brother ;)
Yes I know it's maybe easy for me and you but take a look here
https://retropie.org.uk/forum/topic/12930/
I suggested the first solution (yours)
but it didn't work, so I used the "old" way.....

I'll try to find what he made wrong. I think it was my fault: I didn't give really clear instructions for inexperienced Linux users.

I bought now one of these mausberry devices to test ;)
It's really hard to test without the device.

Oh yeah! Let's break that infinite loop!!

AFAIK an alias can't be called within a script.

I thought you were talking about creating an alias for shutdown command, making it call the killes.sh script before actually shutdown. But this approach has limitations.

So you may export the bash function with export -f func_call. But how this works? Do you have a clue?

When you export something in a shell (functions or variables) only the child shells will know the respective variable/function.

A good way would be to add this function and the export command to one of these files:

~/.profile
~/.bash_profile
~/.bashrc
/etc/profile
create a file at /etc/profile.d/ directory (btw, did you notice that you have a /etc/profile.d/10-retropie.sh on your RetroPie? :) )

But this approach also has its limitations...

lilbud

I have followed @meleu down the bash rabbit hole and need some help getting out.

I am trying to write a script for the retropie menu that will allow you to select the overlay you want, (kind of like the SNES Mini). That is where I get stuck.

My idea is this: When the script starts, it will list all of the overlays in a directory and allow you to select them. Upon selection, it will modify the overlay.cfg file and replace what is there, and finally start the game with the overlay applied.

Better example of what I am trying to accomplish: https://ghostbin.com/paste/avjcs

meleu

@lilbud it's possible. But you have to specify where do you want to apply the overlay (specific for a game? specific for a system?).

Expand the use case.

cyperghost

@lilbud Yes please - I can't imagine what you exactly want.
I think it can be wrapped up like here

lilbud

@meleu The script would apply the overlay to all systems automatically. Individual systems can be modified when launching a game from the system where the user doesn't want an overlay, like GB/GBC/GBA or other hand held systems were aspect ratio is not 4:3

@cyperghost Something like that would be nice for this, having the script and be able to choose which systems you want the overlay to be applied to.

cyperghost

@lilbud automatically means to invoke runcommand-onstart.sh
I think it's doable but we need more input about usecase...

I think there is a need of 2 parts....

Part let you choose overlay for special system
Invokes seleceted overlay to system on start of emulator run

I think.... you should start coding. And we will help you ;)
You can read the full thread I've posted ... The issue here was solved in an efficient way (imho)

meleu

@lilbud said in shell scripting topic:

@meleu The script would apply the overlay to all systems automatically.

I'm not sure if an overlay for all systems would look good. I think some systems have a different aspect ratio.

As @cyperghost said, we can help you once you start the coding. But maybe the fastest solution is to use rpie-art tool. Learning how to create an info.txt file is faster than learning a programing language.

Here is the info.txt creation doc: https://github.com/meleu/rpie-art/blob/master/INFO.md

cyperghost

@meleu Yes... therefore the runcommand-onstart. $1 shows current used system. So there is a way to set an overlay for a specfic system ... ;)

lilbud

@meleu @cyperghost I had this to start with:
sed -i 's/01.png/08.png/g' overlay.cfg

Something feels missing, not sure what at the moment.

meleu

@lilbud where is placed the script with that line of code? maybe you have to use the full path to the overlay.cfg.

lilbud

@meleu I believe it is placed in the overlay directory.

opt/retropie/configs/all/retroarch/overlay