Feedback wanted for upcoming script language

View Poll Results: How many letters shall the core commands have?
6-7 letters are ok (example: printh or 'header') 3 75.00%
2 letters of which 1 is capital is prefered (example: sT for 'title') 1 25.00%
Voters: 4. This poll is closed

Thread Tools Search this Thread
Top Forums Shell Programming and Scripting Feedback wanted for upcoming script language
# 1  
Old 01-22-2020
Feedback wanted for upcoming script language


I'm currently rewriting a project from install-required to a pure runtime form.
The former had required the project name and the definition of the command as name, as they all become functions now, this could be shorter.

As you might have figured, the project already exists in another form - the first iteration I had done.
With the new change to make it pure runtime - it was not slow before, but - it will be alot faster.
And as before, cross-platform, arch independant, working at runlevel 1 or higher.

Simplified use of select, yesno (read), themes, or starting of relevant GUI or CLI commands (editor, webbrowser) where available/required.
No worries wether curl or wget is installed by the use of 'download', and lots, lots more!

Question (Poll):
When you write a script, what would you prefer to be a command?
* a 6 -7 letter 'word'
* a 2 letter 'word' of which 1 is capital?

Be aware, this would replace your current 'echo' or 'printf' commands that are supposed to be seen by the end user.
(I trust your intellect to extrapolate the approriate values at the poll)

This only refers to the 2-4 absolute core display functions.
In a simplified prespective, I use:
* echo : for final outputs - starting on a new line afterwards
* printf : for ongoing changes
* I'd like to have a 'header' for a project
* and a 'title' for different section or topics

Mostly because I do not want to 'reuse' echo, allthough SWARM is a Shell Wrapper...
Or should I?
It would be easier, but could you differ print and echo for end user output vs. $PRINTF and $ECHO for internal use (though, the latter is required anyway)?
This is something I cant decide 'for myself' when I want others to 'get along' with it. (the game of numbers)

A 2 letter 'word' would require only 3 keystrokes, while a 6-7 letter 'word' would not require shift.

Addon question (Comment):
Would you prefer the commands 'title' and 'header' to have as such, or be adapted to the result of the poll?

See screenshot - This is how SWARM can look like (note: select is now handled too and root has a different theme):
'Topline' = header
'2nd' line = title
'3rd' line + = 'echo' or 'printf' replacements


Last edited by sea; 01-22-2020 at 10:58 PM..
# 2  
Old 01-23-2020
I voted for the 6/7 letter word option for a couple of reasons. I feel the command(s) would be more self-documenting with longer names. Google, searches, etc for command will avoid false positives for the existing variant of command without capital letters.
# 3  
Old 01-23-2020
Hi sea...

As with Chubler_XL the more verbose the command the better.
The rest is your personal choice except perhaps that echo should be kept in its POSIX simplest form to make it as portable as possible.
# 4  
Old 03-10-2020
Sorry for the long 'break'.
Windows had decided to to format my uefi boot - and I dont check for input if I cant work on it. (priorities / 'free' mind)

This said, I've decided to come up with something in the like of:
  • printe : This is a compromise, I 'cant' use 'echo' and I dont want to use something like 'swarm_echo' (to me, echo is most usable for its 'default new line'. ; I expect this 'comand' (read function) be used the most often)
  • printl : As above for printing on-line.
  • printh : Prints the header (the blue line) ; still thinking to name it just 'header' ?? -> but could be misleading with 'head'...
  • printt : Prints the title (the white line, centred text), might name it just 'title' ?

Now this is all just the 'core display' functions.
But, it's getting more difficult for actual (kind of 'visual') wrapper's such as (but not limited to) dd or select (NOT seen in the screenshots).

And while you read this, please be aware, FOR ALL DEFAULT GNU COREUTILS, swarm checks the system and puts each of them as capital variables for easy access, as in: $ECHO, $DD, $LS, $MKDIR and so forth.

However, doing so still keeps me from 'saving' builtin bash functions such as previously mentioned: select.

By default, one uses select like:
select value in list of words

In comparision, the wrapped select usage would look like:
value=$(select list of words)
tbh, I'd have less an issue with just throwing an echo wrapper with the same name at you guys, rather than just re-using the word select and use for my own function.
Then again, one still can use the builtin function by using \select if needed (same with echo and printf, as those $ECHO and $PRINTF variables are just that).

This explained, one would be 'forced' to use $AWK instead of g/awk (there it begins, but doesnt stop), same for sed, grep and all other 'default' commands in one's scripts.
As this is required to have cross-platform compatiblity with system such as - but not limited to - Solaris and some BSD variants...

Note, I was thinking of adding an 'option' in the config file, to 'enable' a 'builtin overwrite', which would rename (load functions named: echo, printf, select) as a true wrapper. (read: just a function that refers to the other function).
One could still use default commands by using \echo or $ECHO -> but it would help to 'instantly see' a change with one's script - without the need to rewrite (much).
Mind you, this would be optional.

Geez, became much more text than intended, so to make my questions short:
* What do you think of the suggested names? (specialy header/title !?)
* What is your thought on 'select' and 'dd', maybe name suggestions please? -> do you think swarm_XXX would suffice?

Thank you for your feedback and thoughts.

PS @wisecracker:
In it's TUI form, SWARM could do all Pipes and whistles one expects from GNU/Linux and POSIX usages (that I'm aware of).
I intend to keep it that way.
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. What is on Your Mind?

Wanted: Feedback on TUI (2)

Hello everyone It just so happend that TUI was rejected from GNU for the moment, with one of the reasons beeing that additional user feedback was required. So, if you like scripting, bash in specific, please have a try and report your feedback, to help me find all issues to fix, and as i... (0 Replies)
Discussion started by: sea
0 Replies

2. What is on Your Mind?

Wanted: Feedback on TUI

Hello Couldnt think of a better place than "What is on your Mind". So me have that project :b: Eventhough i tried to describe it well in its thread and its on github, i've... (15 Replies)
Discussion started by: sea
15 Replies

3. Shell Programming and Scripting

I just wanted to share this bash script for linux

If your Unix box doesn't support bash scripts then do not do the following. Create a file named version. type chmod 755 version and then copy and paste the code below into the file. Then type "mv version /bin" and presto, type version. A cool full hearty command. If you know more about you're Os... (3 Replies)
Discussion started by: Errigour
3 Replies

4. Shell Programming and Scripting

First public beta of upcoming gawk 4.0 release

Hi (g)awk lovers, just spreading the news: the first beta is available and there are many new features. This is the original announce. (3 Replies)
Discussion started by: radoulov
3 Replies

5. Shell Programming and Scripting

lvm/tar/rsync backup script feedback/criticism

I have written a shell script to perform backups using tar, rsync and optionally utilise lvm snapshots. The script is not finished but is in a working state and comments/descriptions are poor. I would greatly appreciate any criticism and suggestions of the script to help improve my own learning... (0 Replies)
Discussion started by: jelloir
0 Replies

6. Shell Programming and Scripting

help wanted to understand MQ script

hi , i am writing a script to copy the MQ messages from onw queue to another. The following i got from one site, but i di not understand , can anyone explain. /root/scripts/sap/q -m$Q_MANAGER -i$Q_NAME_SRC_1 -F/logs/mq/MQ_COPYdump_$Q_NAME_SRC_1.$$ /root/scripts/sap/q -m$Q_MANAGER... (0 Replies)
Discussion started by: Satyak
0 Replies

7. Shell Programming and Scripting

I wanted to update a script, more dynamic (just say no to hard coding)...

currently it has the following: bdumpN=`ll /home/apps/oracle/admin/DBprod/bdump/DBprod_j* | grep "$Cdate" | wc -l` If I pass the DBname, I would not have to hardcode it in the script... I can capture the database name by adding the following: DBname=$1 The problem is, I have been unable... (2 Replies)
Discussion started by: mr_manny
2 Replies

8. UNIX for Dummies Questions & Answers

New User needing Help for upcoming job

Hello All, I'm applying for a new job in telecommunications and have been asked to learn unix and pearl scripting. I've got a copy of knoppix Linux 03. I at this point only know how to list files, create directories, change permissions. I was instructed to learn how to create files, basic... (3 Replies)
Discussion started by: cyberjax21
3 Replies

9. Shell Programming and Scripting

Feedback on Script.

Hi all, Would like to get some feedback on a scrip that I've finished writing at home for work. Any constructive feedback from operations used to legibility, etc. would be appreciated - anything at all. It's my first real script that will be running on a clients server. The script is... (2 Replies)
Discussion started by: Cameron
2 Replies
Login or Register to Ask a Question