Visit Our UNIX and Linux User Community

Full Discussion: GNU screen
Top Forums UNIX for Advanced & Expert Users GNU screen Post 302240491 by sentinel on Friday 26th of September 2008 12:30:45 AM
Old 09-26-2008
How can I change the prompt that GNU screen displays in .screenrc.

I've tried setenv PS1='\w: ' and
export PS1='\w: '
but it does not show up when the screen open.

man screen does give some options of set prompt and PROMPT_COMMAND but these give errors from the screenrc file. (I use bash)
 
Test Your Knowledge in Computers #39
Difficulty: Easy
IC chips for computer systems are usually made of silicone.
True or False?

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

GNU Screen: Send to Multiple Screens at Once?

There is a feature that I used in KDE's Konsole that I really miss when I'm on a non-GUI server. The ability to "broadcast" what I type to all open windows. That led me to wonder if this could be done with GNU screen (since it can do a whole lot of other cool stuff)? Basically, it would be... (3 Replies)
Discussion started by: deckard
3 Replies

2. HP-UX

Compiling GNU 'screen' on HP-UX 11i

I finally gave up and installed the prepackaged version of 'screen', but I really want to get a better understanding of why my compilation of 'screen' failed on HP-UX 11i using GNU gcc (also from a prepackaged version). Whenever I would try to run './configure' to prep for building screen, it... (4 Replies)
Discussion started by: deckard
4 Replies

3. UNIX for Dummies Questions & Answers

Redirection to GNU screen attached serial port

I'm using GNU screen as a terminal to connect with a usb serial port. eg. screen /dev/tty.usbserial . This works well enough for manual processes. Is there a way to redirect the output of a script running in another session to the stdin of this virtual terminal? ie. I want to repeatedly send some... (1 Reply)
Discussion started by: geoffjMontreal
1 Replies

4. UNIX for Advanced & Expert Users

Help with GNU screen: Backtick and Caption.

I'm trying to get GNU screen to show the output of "uptime" for the host being accessed in the current window, but unfortunately, no matter what window I go in, it shows the uptime for the host I originally launched screen in ("adminhost"). Does anyone know how to get this to update from the... (0 Replies)
Discussion started by: akbar
0 Replies

5. UNIX for Dummies Questions & Answers

GNU Screen - viewing hardcopy (binary)

I generate a hardcopy (C-a h) of an ncurses screen which has some formatting on it (boxes, highlights). If I "cat" the file, i get only text. If I do a cat hardcopy.n | less , then i see a lot of control characters where the boxes are. most hardcopy.n shows me a hexdump of the file. less... (0 Replies)
Discussion started by: sentinel
0 Replies

6. HP-UX

GNU screen on HP-UX 11.23

I compiled GNU screen on HP-UX 11.23 and following the compile, I get the following error when I try to run screen Cannot find terminfo entry for 'vt100' By default the TERMINFO is not set, I found a reference that setting it might help. I tried the following but I still receive the same... (2 Replies)
Discussion started by: scotbuff
2 Replies

7. UNIX for Advanced & Expert Users

GNU screen: shortcut to go to tab 10,11 etc

Using GNU-Screen for a long time. C-a 1 2 n p to navigate to other tabs. This works till 9. I often have 10, 11 etc. Is there any way to go to them quickly ? Currently, i have to do C-a 9, C-a n which is quite a pain. Thanks. (0 Replies)
Discussion started by: sentinel
0 Replies

8. Red Hat

command line tool to disable screen lock and/or screen saver

Hi, I have a simple question : how to disable screen lock and/or sreen saver with command line with RHEL5.4 ? (1 Reply)
Discussion started by: albator1932
1 Replies

9. Shell Programming and Scripting

GNU-Screen Stuff problems

OPTIONS="java -Xms1024M -Xmx1024M -jar craftbukkit.jar" PROCESS=server01 screen -dmS $PROCESS $OPTIONS nogui # Starting the application screen -x $PROCESS -X stuff `printf "stop\r"` # Closing the application screen -x $PROCESS # Attaching to the... (3 Replies)
Discussion started by: Zanax
3 Replies

10. Linux

GNU Screen key bindings....

After I do CTRL-" to show all of my screen sessions, I typically use the up and down arrows to navigate up and down. Suddenly this has changed, and instead only "j" and "k" seem to work for up and down. This has changed in the middle of my screen session. First one changed, and then the... (1 Reply)
Discussion started by: akbar
1 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)

Featured Tech Videos

All times are GMT -4. The time now is 11:12 AM.
Unix & Linux Forums Content Copyright 1993-2021. All Rights Reserved.
Privacy Policy