Sponsored Content
Top Forums Shell Programming and Scripting Is it possible to combine these two PS1 examples? Post 302637981 by MIBPreacher on Wednesday 9th of May 2012 04:11:01 PM
Old 05-09-2012
Is it possible to combine these two PS1 examples?

I need to have the following joined if possible. Any help would be appreciated.

1st PS1 is for current working directory and color in ksh88.
Code:
PS1=$(printf "\033[46;31m%s@\033[1;33m%s:\033[1;34m\$PWD \033[0m \033[1;33m\$date\033[0m \$" $(logname) $(hostname))

2nd PS1 is for the time in ksh88.
Code:
date '+%H %M %S' | read H M S
SECONDS=$((S + 60*(60*H+M)))

Code:
PS1='${DUMMY[((S=(100+$SECONDS%60))+(M=(100+($SECONDS/60)%60))+(H=(100+($SECONDS/3600)%24)))*0]:-} ${H#1}:${M#1}:${S#1} $ '


Last edited by Scrutinizer; 05-10-2012 at 05:41 PM.. Reason: code tags
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

looking for .profile examples

I'm looking for some 'well documented' .profile examples (8 Replies)
Discussion started by: JimC
8 Replies

2. Shell Programming and Scripting

need examples?

Can someone give me an example of two shells? (1 Reply)
Discussion started by: wmosley2
1 Replies

3. Red Hat

redhat-release examples

I have a script that checks the redhat-release file to determine what security patch needs to be applied. Since there's a Red Hat 5 now, I need a redhat-release file from the various platforms (Desktop, Enteprise Workstation, and Enterprise Server) so I can build a proper search string. Also, it... (5 Replies)
Discussion started by: BOFH
5 Replies

4. UNIX for Advanced & Expert Users

Most useful Unix commands and Examples

These commands are placed in the MS Word Doc. with command options and the their respective examples. hope this will help for the beginners. Thanks. Varun Gupta:D (2 Replies)
Discussion started by: varungupta
2 Replies

5. UNIX for Dummies Questions & Answers

SimpleAWK Examples

Can Anyone please give me some simple AWK Examples to clearly understand the usage and syntax of the command. Thanks (2 Replies)
Discussion started by: unxusr123
2 Replies

6. Emergency UNIX and Linux Support

Awk and Sed examples

Hi all, I tried to understand what this awk and sed does but cudnt understand. Can any body explain what awk and sed means with one simple example each and complex examples each with explanation. Thanks in advance. (7 Replies)
Discussion started by: j_panky
7 Replies

7. UNIX for Advanced & Expert Users

Hard Link Examples

Hello, Please move this if I chose the wrong forum category. This question pertains to Unix and Linux I believe. I google the difference between hard and symbolic/soft links and I understand the difference. What I am trying to find is a real example of a hard link being used in a Operating... (11 Replies)
Discussion started by: jaysunn
11 Replies

8. Shell Programming and Scripting

lwp-request examples

Hi; Can i have ne sample examples of of using " lwp-request" in shell script. Is it necessary to have perl installed already in linux box for using this; Thnks; (2 Replies)
Discussion started by: ajaypadvi
2 Replies

9. Programming

Examples, usage, help in C++ program

I have written a C++ program to perform raytracing and would want to write some functions to help the user: examples, usage, help I am wondering how this is done. Would I just put some functions in the main program? (4 Replies)
Discussion started by: kristinu
4 Replies

10. Shell Programming and Scripting

Need lot of examples

Hi, I need a word doc or pdf which contains lots of Shell Programming samples... This is for my open book examination, thanks in advance.. (2 Replies)
Discussion started by: karthikeayan
2 Replies
Env::PS1(3pm)						User Contributed Perl Documentation					     Env::PS1(3pm)

NAME
Env::PS1 - prompt string formatter SYNOPSIS
# use the import function use Env::PS1 qw/$PS1/; $ENV{PS1} = 'u@h $ '; print $PS1; $readline = <STDIN>; # or tie it yourself tie $prompt, 'Env::PS1', 'PS1'; # you can also tie a scalar ref $format = 'u@h$ '; tie $prompt, 'Env::PS1', $format; DESCRIPTION
This package supplies variables that are "tied" to environment variables like 'PS1' and 'PS2', if read it takes the contents of the variable as a format string like the ones bash(1) uses to format the prompt. It is intended to be used in combination with the various ReadLine packages. EXPORT
You can request for arbitrary variables to be exported, they will be tied to the environment variables of the same name. TIE
When you "tie" a variable you can supply one argument which can either be the name of an environement variable or a SCALAR reference. This argument defaults to 'PS1'. METHODS
"sprintf($format)" Returns the formatted string. Using this method all the time is a lot less efficient then using the tied variable, because the tied variable caches parts of the format that remain the same anyway. FORMAT
The format is copied mostly from bash(1) because that's what it is supposed to be compatible with. We made some private extensions which obviously are not portable. Note that this is not the prompt format as specified by the posix specification, that would only know "!" for the history number and "!!" for a literal "!". Apart from the escape sequences you can also use environment variables in the format string; use $VAR or "${VAR}". The following escape sequences are recognized: a The bell character, identical to "07" d The date in "Weekday Month Date" format D{format} The date in strftime(3) format, uses POSIX e The escape character, identical to "33" Newline Carriage return s The basename of $0 The current time in 24-hour format, identical to "D{%H:%M:%S}" T The current time in 12-hour format, identical to "D{%I:%M:%S}" @ The current time in 12-hour am/pm format, identical to "D{%I:%M %p}" A The current time in short 24-hour format, identical to "D{%H:%M}" u The username of the current user w The current working directory W The basename of the current working directory $ "#" for effective uid is 0 (root), else "$" dd The character corresponding to the octal number 0dd \ Literal backslash H Hostname, uses Sys::Hostname h First part of the hostname l The basename of the (output) terminal device name, uses POSIX, but won't be really portable. [ ] These are used to encapsulate a sequence of non-printing chars. Since we don't need that, they are removed. Extensions The following escapes are extensions not supported by bash, and are not portable: L The (output) terminal device name, uses POSIX, but won't be really portable. C{colour} Insert the ANSI sequence for named colour. Known colours are: black, red, green, yellow, blue, magenta, cyan and white; background colours prefixed with "on_". Also known are reset, bold, dark, underline, blink and reverse, although the effect depends on the terminla you use. Unless you want the whole commandline coloured you should end your prompt with "C{reset}". Of course you can still use the "raw" ansi escape codes for these colours. Note that "bold" is sometimes also known as "bright", so "C{bold,black}" will on some terminals render dark grey. If the environment variable "CLICOLOR" is defined but false colours are switched off automaticly. P{format} Proc information. All of these are unix specific %a Acpi AC status '+' or '-' for connected or not, linux specific %b Acpi battery status in mWh, linux specific %L Load average %l First number of the load average %t Acpi temperature, linux specific %u Uptime %w Number of users logged in Not implemented escapes The following escapes are not implemented, because they are application specific. j The number of jobs currently managed by the application. v The version of the application. V The release number of the application, version + patchelvel ! The history number of the next command. This escape gets replaced by literal '!' while a literal '!' gets replaces by '!!'; this makes the string a posix compatible prompt, thus it will work if your readline module expects a posix prompt. # The command number of the next command (like history number, but minus the lines read from the history file). Customizing If you want to overload escapes or want to supply values for the application specific escapes you can put them in %Env::PS1::map, the key is the escape letter, the value either a string or a CODE ref. If you map a CODE ref it normally is called every time the prompt string is read. When the escape is followed by an argument in the format string (like "D{argument}") the CODE ref is called only once when the string is cached, but in that case it may in turn return a CODE ref. BUGS
Please mail the author if you encounter any bugs. AUTHOR
Jaap Karssenberg || Pardus [Larus] <pardus@cpan.org> This module is currently maintained by Ryan Niebur <rsn@cpan.org> Copyright (c) 2004 Jaap G Karssenberg. All rights reserved. Copyright (c) 2009 Ryan Niebur. This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. SEE ALSO
Env, Term::ReadLine::Zoid perl v5.10.0 2009-06-25 Env::PS1(3pm)
All times are GMT -4. The time now is 10:58 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy