Just tried it on a TTY and... had to do some fixes... who would have thought that some shells return -bash as their $0 instead of just bash.
After that, it worked!
Though, figued I need to get rid of the underline for the title, as that becomes a 'cyan'ish background - which kinda makes it hard to read that blue text...
And sure as hell is not inteded, I mean, even adding the underline was just a little fun - and I wasnt sure wether I wanted to keep it or not.. this helps
Just thought I'd share the first image of the TTY test.
But this 'experience' is always kind of a milestone - just to know that it -as it is- works in its basic form for/in both, X and TTY/environments.
Well, once I got rid of that cyan/underline that is...
this is the output i am getting here..
cp: cannot create /wls_domains/eoigw/eoigwsA/deliv/cron/MailingScript/eoigwsA_Health_Status_Report.html: Permission denied
/wls_domains/eoigw/eoigwsA/deliv/cron/MailingScript/
/wls_domains/eoigw/eoigwsA/deliv/cron/MailingScript/GenerateReport.sh:... (6 Replies)
Hi Guys, I am trying write a wrapper script but I don't have any idea. I have 4 different korn shell scripts and all of them needs some parameters from command line (positional parameter). My script cant be interactive because its supposed to be automated. I am confused how can I write a wrapper... (6 Replies)
Hello!
I would like to create a blog website on a web domain of mine. The blog will be used for publishing economics-lated articles.
I tried to use a few open source packages for blog creation (WorldPress, b2evolution, Movable type) which I wanted to test on a local computer before arranging... (5 Replies)
Hi all,
Can I create multiple threads using single thread_id
like
pthread_t thread_id;
pthread_create(&thread_id, NULL, &print_xs, NULL);
pthread_create(&thread_id, NULL, &print_ys, NULL);
pthread_create(&thread_id, NULL, &print_zs, NULL);
pthread_join(thread_id, NULL);
what... (2 Replies)
Hi,
I am trying to capture runtime stats of a shell script (c shell). Are there system variables to call? Or should I create a date variable at the start of the script and at the end of the script? I am trying to capture the time if the script stops or ends with error.
Please help.
... (4 Replies)
Hello,
My requirement is based on Oracle where we run a perl script and it asked some questions.I want to write a wrapper which will answer all these questions.
How is it possible.
Thanks (16 Replies)
Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted!
1. The problem statement, all variables and given/known data:
Make a bash script that calculates average runtime for the first two scripts you made. The average should be... (17 Replies)
Hi,
I have shell script that I am running under Ubuntu as root.
Is it possible to hide the command window and show the user some sort of progress /random progress bar / or other form of GUI interaction?
On MAC, I have been using Platypus but on Ubuntu I am not sure what to do. (4 Replies)
Discussion started by: naveedanwar4u
4 Replies
LEARN ABOUT DEBIAN
ddtcrc.5
DDTCRC.5(5) User Contributed Perl Documentation DDTCRC.5(5)NAME
.ddtcrc - ddtc script configuration file.
DESCRIPTION
This is the configuration file for ddtc. If it exists, it must be at the top of your home directory ($HOME). This file is optional unless
you don't want to use default values.
Lines beginning with a number sign (`#') and empty lines will be ignored. Spaces at the beginning and the end of a line will also be
ignored as well as tabulators. If you need spaces at the end or the beginning of a value you can use apostrophes (`"'). An option line
starts with it's name followed by a value. An equal sign is optional. A comment starts with the number sign, there can be any number of
spaces and/or tab stops in front of the #. Some possible examples:
# this line is ignored
option value
option = value # this is a comment
option "value ending with space "
You have to escape number signs with a backslash (`') to use it in a value.
Default values are provided into square brackets, they should be suitable for most installations.
You can use the configuration menu from interactive mode to edit it.
GENERAL
base_dir
base directory, sub-directory of your $HOME unless an absolute path (i.e. beginning with `/') is provided [ddts]
comment
comment string for review, a space character will be added to this string [>>]
clean_regex
regular expression to remove file with clean command [~$|.old$|.bak$]
language
language extension to use when asking for new documents to translate or to review [none]
editor
text editor [sensible-editor]
ddtc_bug
whether reviews are sent in a special way to prevent updating ddts parts databases or not. [no]
Caution: if set to `yes', the `reply to accept modification' ddts feature doesn't work anymore and the whole language team should use
ddtc. Ask your language team coordinator before setting this option.
EMAIL
mail_out
your email address [first found in $ENV{EMAIL}, $ENV{DEBEMAIL} or none]
mail_in
the mail address you want the ddts to answer to. This is the address the ddts uses for your identification so you must use this if you
need to set mail_out to another value [mail_out]
mail_server
email address of the server [desc@ddtp.debian.org]
mail_encoding
mail encoding for mime [8bit]
mail_charset
mail charset for mime [ISO-8859-1 for lack of charset used by ddts]
mail_self
set to `yes' if you want to be sent a copy of outgoing mail [yes]
MENU COLORS
Set text colors for clear presentation.
The recognized colors (all of which should be fairly intuitive) are: clear, reset, dark, bold, underline, underscore, blink, reverse, con-
cealed, black, red, green, yellow, blue, magenta, cyan, white, on_black, on_red, on_green, on_yellow, on_blue, on_magenta, on_cyan, and
on_white. Case is not significant. Underline and underscore are equivalent, as are clear and reset, so use whichever is the most intu-
itive to you. The color alone sets the foreground color, and on_color sets the background color.
Note that not all colors are supported by all terminal types, and some terminals may not support any of these sequences. Dark, blink, and
concealed in particular are frequently not implemented.
menu_title_color
color used for menu title [bold cyan]
menu_letter_color
color used for the letter to be entered [bold cyan]
menu_text_color
color used for the menu item description [cyan]
EXAMPLE
A ddtc configuration example file can be found at /usr/share/doc/ddtc/ddtcrc.
SEE ALSO ddtc(1).
AUTHOR
Nicolas Bertolissio <bertol@debian.org>
perl v5.8.4 2003-10-25 DDTCRC.5(5)