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.
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 DEBIAN
acheck
ACHECK.1(1) User Contributed Perl Documentation ACHECK.1(1)
NAME
acheck - Check common localization mistakes
SYNOPSIS
acheck [OPTIONS] [INPUT_FILE]
DESCRIPTION
This program parses a file checking for syntax rules and optionally asking Aspell for checking word spelling. It makes fix suggestions and
outputs a corrected file accordingly adding review comments if requested.
It tries to find the file type according to the extension or the first lines and loads rules accordingly.
It displays lines when they are parse.
When an error is found, a menu is displayed. Just press Enter if you don't want to change anything. If a choice suits you, enter the corre-
sponding number. If you want to fix it but no choice is correct, enter a space, then you will be asked for a string to replace the high-
lighted text. The script will replace the highlighted text with your choice and parse it again for new errors.
Here are all the available commands:
Enter, ignore.
Ignore.
Ctrl+L, redraw.
Rewrite the last line, suggestions and hints.
Space, edit.
Edit the highlighted text.
E, edit line.
Edit the whole line.
H, add hint.
Add the displayed hint as review comment. Use this if you want the translator to see the corresponding warning or error but you have no
correction.
N, next line.
Skip the rest of this line.
X, exit and discard all changes.
Quit without saving modifications, the script ask you for confirmation, you have to enter `yes' to exit otherwise parsing starts again
at the current mistake.
a, add in dictionary.
Add the highlighted word to you personal dictionary, capitalized as it is.
l, add lowercase in dictionary.
Lowercase the highlighted word to add it to your personal dictionary.
i, ignore word.
Ignore the highlighted word, same as Enter.
I, ignore all.
Ignore the highlighted word and add it to your session dictionary.
OPTIONS
Verbosity level:
-q, --quiet
quiet mode.
-v verbose, start at level $Debug + 1, add more for more verbosity (see below).
--verbose n
set verbosity level to n (see below).
Files:
-i, --input
input filename, can be '-' to read data from standard input.
-o, --output
output filename, can be '-' to write data to standard ouput. If no output filename is provided, input file is backed up with `bak_ext'
extension and input filename is used.
Spell check:
-s, --spell
check spelling with Aspell.
-d language, --dict language
use language dictionary for Aspell.
-n, --nospell
don't check spelling.
Mode:
-r, --review
review mode, add comments on lines beginning with $Comment after parsed line.
-t, --trans
translator mode, don't add comments, just fix errors.
others:
--rules ruleset
use ruleset rules set.
--type filetype
use filetype whatever the file type is.
--dump
Dump the rules to check and exit, use this for debugging purposes.
-V, --version
print version and exit.
-h, --help
print a short usage message and exit.
Verbosity Level
0 quiet, normal
only warnings and errors
1 debug
names of subroutines
2 debug verbose
names and arguments of subroutines
3 .. 5 debug very verbose
output parsing and checking details
SEE ALSO
acheck(5), acheck-rules(5)
AUTHOR
Nicolas Bertolissio <bertol@debian.org>
perl v5.8.4 2003-10-05 ACHECK.1(1)