Sponsored Content
Full Discussion: Bash prompt is over lapping
Top Forums UNIX for Dummies Questions & Answers Bash prompt is over lapping Post 302923454 by kapil514 on Monday 3rd of November 2014 03:47:17 AM
Old 11-03-2014
Code:
:~$ ot@Servername
:~$ PS1='[\u@\h \W]$ '
 ~]$ ot@Servername

Tried above one but still its not working the whole command is clubbing with Prompt text not sure what is wrong.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

customize my prompt in bash

in csh I was using: set prompt=""$HOSTNAME".tk.\!> " to customize the look of my prompt. I have seen the light after reading the perils of csh scripting and wish to switch to bash. How do I customize my bash prompt??? I've tried many variation of the above w/no success, and searching this... (2 Replies)
Discussion started by: yankee428
2 Replies

2. Shell Programming and Scripting

Works from bash prompt, but not from script!

I'm trying to use unison from bash on windows with cygwin. I don't know if this is a cygwin question, bash question or unison question. Since I always get reprimanded by the cygwin mailing list for assuming it is a cygwin problem, I'll assume it is a bash question. The following commands work... (7 Replies)
Discussion started by: siegfried
7 Replies

3. Shell Programming and Scripting

How can i change my bash prompt ?

It looks like, user@hostname:/auto/home3/user$ Desired, user@hostname$ I added following line in .bashrc, but still its same. export PS1=" $ " Please help me :confused: (13 Replies)
Discussion started by: admax
13 Replies

4. UNIX for Advanced & Expert Users

Bash conditional prompt?

Hi, Does anyone know any way of making bash prompt extended with conditional content? Example: export PS1="] && echo '#' || echo '\$'" # This won't work - prompt is not executed # export PS1="\$" # This is an existing but also working equivalent I would like to use more complex... (8 Replies)
Discussion started by: adderek
8 Replies

5. OS X (Apple)

Bash prompt wraparound

I'm using a custom prompt with PS1 in my .profile. It is PS1="\\u@\e\:\W\ \\$\ \" and it works well, as you can see, http://content.screencast.com/users/killer54291/folders/Jing/media/2b3db52a-ebf7-43e2-95cc-f45dadbc2b98/00000023.png but, when i type more than the width of the window, it... (0 Replies)
Discussion started by: killer54291
0 Replies

6. Shell Programming and Scripting

BASH: Getting titlebar and prompt to 'sync up'

This is an instance of "if it's not one thing, it's another." I recently fell victim to my own stupidity in trashing, by accident, my long-running and very highly-customized .bash_profile and .bashrc files for Cygwin & Cygwin/X. I had backups from a previous "go" with this, and decided to use... (0 Replies)
Discussion started by: SilversleevesX
0 Replies

7. Emergency UNIX and Linux Support

Bash answer prompt

I am working with a script to simplyfy some operations where I work, but one of the programs needs me to enter a password. It will as me "Please enter the administrator password:" Is there a way to make a bash script to automatically answer the question with the needed password? I am looking... (3 Replies)
Discussion started by: noratx
3 Replies

8. Shell Programming and Scripting

How to (GUI) prompt for password from bash?

I remember there was a gnome only command that we could insert in a bash script to mount a Linux disk that would pop up a little window to grab a password. I know there are bash commands to read a string but they are not GUIs and they echo the characters typed. This gnome command popped up a... (1 Reply)
Discussion started by: siegfried
1 Replies

9. Shell Programming and Scripting

Running an executable from bash prompt

Hi, I'm trying to run a program from the bash prompt and I don't understand why it is returning with an error. Dig is my C program, and it takes in parameters J4, detect, 3 and 0182F98E var1="cygdrive/c/2i/test fixture/software/mccdaqtest/debug/Dig J4 detect 3 0182F98E" when I do ... (6 Replies)
Discussion started by: oahmad
6 Replies

10. Shell Programming and Scripting

Autojump with modified bash prompt

I use the .bashrc file from this thread. Direct link to the archive containing the ultimate bashrc I am trying to use autojump, but it will not autoload the directories to the autojump list as the custom prompt is not compatible. Here is the thread on the issue from other users. apt -... (2 Replies)
Discussion started by: genehunter
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 04:10 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy