|
|
Sponsored Content
Top Forums
Shell Programming and Scripting
Feedback wanted for upcoming script language
Post 303043262 by sea on Wednesday 22nd of January 2020 06:41:40 PM
01-22-2020
Feedback wanted for upcoming script language
Hi
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)
Summarization:
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
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)
Summarization:
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 09:58 PM..
|
|
9 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
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
2. UNIX for Dummies Questions & Answers
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
3. Shell Programming and Scripting
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
4. Shell Programming and Scripting
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
5. Shell Programming and Scripting
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
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
7. Shell Programming and Scripting
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
8. What is on Your Mind?
Hello
Couldnt think of a better place than "What is on your Mind".
So me have that project https://www.unix.com/shell-programming-and-scripting/253496-tui-text-user-interface-framework-scripts.html. :b:
Eventhough i tried to describe it well in its thread and its README.md on github, i've... (15 Replies)
Discussion started by: sea
15 Replies
9. What is on Your Mind?
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
LEARN ABOUT LINUX
shtool-echo
SHTOOL-ECHO.TMP(1) GNU Portable Shell Tool SHTOOL-ECHO.TMP(1) NAME
shtool-echo - GNU shtool echo(1) extensional command SYNOPSIS
shtool echo [-n|--newline] [-e|--expand] string DESCRIPTION
shtool echo is an echo(1) style command which prints string to stdout and optionally provides special expansion constructs (terminal bold mode, environment details, date, etc) and newline control. The trick of this command is that it provides a portable -n option and hides the gory details needed to find out the environment details under option -e. OPTIONS
The following command line options are available. -n, --newline By default, output is written to stdout followed by a "newline" (ASCII character 0x0a). If option -n is used, this newline character is omitted. -e, --expand If option -e is used, string can contain special "%x" constructs which are expanded before the output is written. Currently the following constructs are recognized: %B switch terminal mode to bold display mode. %b switch terminal mode back to normal display mode. %u the current user name. %U the current user id (numerical). %g the current group name. %G the current group id (numerical). %h the current hostname (without any domain extension). %d the current domain name. %D the current day of the month. %M the current month (numerical). %m the current month name. %Y the current year. EXAMPLE
# shell script shtool echo -n -e "Enter your name [%B%u%b]: "; read name shtool echo -e "Your Email address might be %u@%h%d" shtool echo -e "The current date is %D-%m-%Y" HISTORY
The GNU shtool echo command was originally written by Ralf S. Engelschall <rse@engelschall.com> in 1998 for Website META Language (WML) under the name buildinfo. It was later taken over into GNU shtool. SEE ALSO
shtool(1), echo(1). 18-Jul-2008 shtool 2.0.8 SHTOOL-ECHO.TMP(1)