how to make graphical lines in a tui noscript?

​

https://preview.redd.it/rbwtz17ad23b1.png?width=81&format=png&auto=webp&v=enabled&s=178e21ff6f99409f03953b86634d2d329c2319be

I'm trying to make a tui program and I want straight lines like these, (for example ncmpcpp and bottom have them) But I have no idea how to make them using shell noscript. Are they just underscores or are they actually a line? and how are they positioned?

https://redd.it/13w06cc
@r_bash

Question about "ls" error messages, when/why are they suppressed if redirecting the output?

Some background for context only: I am creating a simple bash noscript that will check for stale file handles (most likely Samba mounts that became invalid because the remote system was rebooted, or similar), that I will run from /etc/crontab. The noscript will then umount/mount to fix it, and this is not the part that I have a problem with.

​

The problem is that I wanted to find stale file handles by running ls -1 and looking for an error message such as ls: cannot access 'BAD_MOUNTPOINT': Stale file handle. However, when I try to redirect the output to a mktemp file or pipe it to grep or similar, this error message does not seem to be displayed. Neither on stdout or stderr. It seems to me that ls prints different things if it detects that a console (or not) will receive stdout.

​

In this case, my workaround could be to list all files in the directory, pipe the output into a while IFS= read -r loop and use stat on each filename, which still works from a noscript. But I'd like to know why the ls error output is suppressed. Any ideas?

(It's a bit annoying have a solution that works at the bash command line, but does not work in a noscript.)

https://redd.it/13wg9ol
@r_bash

Problem with * in bash

Hello everyone,
I currently having a problem where the "*" is not replaced by anything in my bash file.

To add context, I'm trying to organize a game collection where I put every game that starts with a "t" in a "t" folder.
To avoid repeating the same two line in my she'll again and again, I wrote a bash noscript to do it for me.
I give it an argument (the letter "t" for example) and it create a folder and move every file beginning with t in it.

I wrote :

#!/bin/bash
mkdir $1
mv ${1}*.a26 $1/

But when I try to execute it, the mv command fail saying that it's impossible to evaluate 't*.a26' because there's no file or folder with this name.
(Just to be clear, I have several files beginning with t).

I can see that the problem comes because of the "*" that is not replaced with anything but I searched and didn't find a solution, neither by myself neither by researching.

So if someone can help me, I will be very thankful

https://redd.it/13wn10e
@r_bash

Sshto fix

Hi, I've just fixed some dumb error in sshto it didn't work if \~/.ssh/config file was missing O_o
Fixed that, enjoy)

https://redd.it/13wqfjs
@r_bash

declaring array using a variable

Given that I can declare an array like this and it creates a three element array perfectly ...

$ declare -a myarray=( 0=apple 1=pear 2=banana )
$ echo ${myarray1}
pear

...then why does this not behave in exactly the same way?

$ arraystring="0=apple 1=pear 2=banana"
$ declare -a myarray=( $arraystring )
$ echo ${myarray1}
1=pear

It still creates a three element array, but includes the key "1=" as part of the element contents. Why is this? I'm sure it has something to do with quoting but can't work it out. Quoting all the elements or quoting $arraystring doesn't seem to make a difference here.

https://redd.it/13wspgg
@r_bash

Tmux plug-in for pianobar.
https://redd.it/13wuyh6
@r_bash

I made a simple noscript for splitting a physical monitor into virtual ones
https://redd.it/13wvk4a
@r_bash

How to compress FileB with respect to, but not compressing, FileA?

Lets say I have FileA and FileB. They are nearly identical files. I am looking to compress the redundant data in FileB with respect to the original data in FileA, then go on to embed the compressed FileB within a metadata field of FileA for export. Eventually would need a process to reverse this as well.

I am not looking for any code but if this is possible and hopefully a point in the right direction. Thanks!

https://redd.it/13wwxtq
@r_bash

Is this regex correct for what I'm trying to do?

So, first-off, I will admit, I know little about regex patterns. I'm trying to get a noscript to identify a \[music\] track filename with a track number, and only if the track number is a single digit, add a leading zero. I'm gonna get some cringes from the audience here, but please be gentle; I'm still very much a beginner, this is how the code for that looks at the moment, and spoiler alert, though no surprise to some, it doesn't work:


[if..then block begins]
elif [[ $filename =~ ^[0-9]+\ .+\.mp3$ ]]; then
local track_number=$(echo "$filename" | cut -d' ' -f1)
local noscript=$(echo "$filename" | cut -d' ' -f2-)

# Add leading zero if track number is a single character
if [[ ${#track_number} -eq 1 ]]; then
track_number="0$track_number"
fi

local new_filename="${track_number} ${noscript}"
if [[ "$filename" != "$new_filename" ]]; then
mv "$mp3_file" "$sub_dir/$new_filename"
log "Renamed: $filename --> $new_filename"
((files_renamed++))
else
log "No changes needed for: $filename"
fi
[if..then block continues]

I have plenty of tracks that are named like "1 Kryptonite.mp3" which I want renamed to "01 Kryptonite.mp3". I have close to 10,000 tracks in my library, so I'm not doing this by hand for the first 9 tracks of 677 albums.

Where am I going wrong, style aside? (I'm literally just trying to get this to work before I make it pretty)

And yes, everything is correctly declared and everything; this is the only part of the noscript I'm having issue with; the rest of the renaming conditions work fine.

https://redd.it/13wviwz
@r_bash

Is Recursion Stateful or Stateless?

Is recursion a stateful or stateless process?

On one hand, all previous iterations affect the next ones.

On the other hand, the function has no idea that it has ever been called before.

https://redd.it/13x4sbu
@r_bash

How to use scale in bc (for division) within a bash noscript and set it as a variable?

Hi, I am modifying a brightness volume bash noscript for my i3wm setup. The original noscript requires xbacklight which doesnt work on my system, so I need to tweak it a little. Anyway, this part of the noscript:

function show_brightness_notif {
brightness=${get_brightness}
# some more codes below for dunstify
}

The idea is that I need to divide this brightness by the max brightness, so I can get a percentage. I found out that you can do float arithmetic using bc, so:

function show_brightness_notif {
brightness=${get_brightness}
bc -l <<< $brightness/$max_brightness
}

This `max_brightness` is set outside the function as global, it is a fixed number. If I do this, calling the function from the command line will indeed show the decimal result. Problem is: it has a lot of decimal places. A quick search shows that you can limit decimal place using scale: [https://askubuntu.com/questions/217570/bc-set-number-of-digits-after-decimal-point](https://askubuntu.com/questions/217570/bc-set-number-of-digits-after-decimal-point)

But where do I write this `scale` variable? More specifically, how do I put everything (the division using bc, the scale) into 1 variable? Ideally, I would use dunst to output this variable.

https://redd.it/13xip20
@r_bash

Ksh etc. in 2023?

What do you guys think about still using a shell like the C shell or the Ksh shell? Are they still worth using?

https://redd.it/13xjds0
@r_bash

Adding the value of an array to a variable

Im just learning bash so this question mighta bit stupid. What im trying to do, is to add the values of every colum of an array, that contain 100 letters at maximum, to an Variable and give out the sum. For this i have created the following noscript:

#!/bin/bash
read save[1000]
i=0
sum=0
while (($i < 1000)); do
sum=$(($sum + ${save[$i]}))
((i++))
done
echo $sum

When executing i get the following error message:

line 5: 0 + : syntax error: operand expected (error token is "+ ")

How can i fix this?

https://redd.it/13xry3j
@r_bash

? - The only cheat sheet you need
https://gist.github.com/thingsiplay/69aada6a57f829d9580d7b54f8a207a0

https://redd.it/13xz1kc
@r_bash

Installer noscript for CMake, Ninja, and Meson

I thought I would share my custom installer noscript for the latest GitHub versions of CMake, Ninja, and Meson.

It uses GitHub's API to grab the latest tag version of each repo and will install the static binaries to /usr/local/bin

bash <(curl -sSL https://build-tools.optimizethis.net)

This is my GitHub repo in case anyone wants to check it out before using: GitHub Script Repo

I hope someone finds this useful. (I know apt works but it doesn't install the latest versions usually).

And please let me know if something is wrong so I can make changes. =)

https://redd.it/13xy52n
@r_bash

Maximize Productivity Of The Bash Shell
https://bluz71.github.io/2023/06/02/maximize-productivity-of-the-bash-shell.html

https://redd.it/13y4pg6
@r_bash

I don't understand how this lines with arrays works

Hello guys, we talked about bash arrays in our shell noscripting course and the professor gave us this demonstration of a cool use of bash arrays but I am not able to understand why this works.

declare -A SELECTOR
declare -A SOMEDATA
declare -A OTHERDATA
SELECTORsome='SOMEDATA$KEY'
SELECTORother='OTHERDATA$KEY'
SOMEDATAfirstkey=somefirstvalue
SOMEDATAsecondkey=somesecondvalue
OTHERDATAfirstkey=otherfirstvalue
OTHERDATAsecondkey=othersecondvalue

KEY=firstkey
DATASET=some
echo ${!SELECTOR$DATASET}
#somefirstvalue

As I know, from bash manual:

>It is possible to obtain the keys (indices) of an array as well as the values. ${!name[@\]} and ${!name[*\]} expand to the indices assigned in array variable name. The treatment when in double quotes is similar to the expansion of the special parameters ‘@’ and ‘*’ within double quotes.

How this syntax of getting the assigned keys of an array let you create this dynamic dataset selection? I am not understanding the step-by-step expansions and operations performed by the shell. Also, I would like to know if any known shell noscripts have used this approach to see a more consistent-real use.

Thanks.

https://redd.it/13yabi7
@r_bash

How do I open a dir/filename with cat command?

For simplicity: I have a directory that contains two things: a setup noscript file, and another directory containing a text file with VS Code extensions, one per line. The paths to the two files would be:

~/Downloads/noscripts/setupnoscript

~/Downloads/noscripts/VSCode/extensions.txt

I have this line in the setup noscript from this superuser topic:

cat VSCode/extensions.txt | xargs -n 1 code --install-extension

I get No such file or directory errors when I run this line; despite trying a number of ways to get it to recognize the file like different path prefixes (/, ./, ../) and even putting extensions.txt in the same directory as setupnoscript. Where am I going wrong?

https://redd.it/13ym85l
@r_bash

Script to simply read value give a not found error ?

Hi

I have a quite simple noscript and somehow i can't figure how to fix it.. It give me a not found all the time. If some do see the point...

nano /sbin/tempcpunotif.sh

#!/bin/bash

while true; do

val=$(sensors | awk '/temp1/ {print $2}')

max="+75.0"

if [[ "$val" > "$max" ]]; then

systemctl suspend

fi

sleep 10

clear

sensors

done

exit 0

&#x200B;

Or i try with a simpler one, but not sure as i told me the temp is not found..:

&#x200B;

#!/bin/sh

# Threshold for when to send alert

threshold=75000

&#x200B;

#sensors | grep -e "Package id 0" | while read line; do

cat /sys/devices/platform/coretemp.0/hwmon/hwmon1/temp1_input | while read line; do

temp=$(echo $line | awk -F "+" '{ print $2 }' | awk -F "." '{ print $1 }');

if (( temp > $threshold )); then sh /sbin/tempnotif.sh

fi;

done

&#x200B;

Thanks in advance

https://redd.it/13yswnh
@r_bash

woman - Preview list for man documents
https://gist.github.com/thingsiplay/f71383569c10da17f772b9967f5a5767

https://redd.it/13z41ji
@r_bash

What is this command?

I have a noscript that should run only when certain directory exists. It begins like that:

-d /home/path/to/directory &&

I found that example somewhere and it works, but I don't understand what these brackets really do. Is it correct way?

https://redd.it/13z8dfl
@r_bash