Re: Access environment variables in screenrc

2015-03-07 Thread Jürgen Weigert
When I put this line in my ~/.screenrc screen 7 env shelltitle="window 7 at $HOSTNAME" bash then screen will create a shell in window 7, that has the machine's hostname as part of its shelltitle env variable. cheers, JW- On Sat, Mar 7, 2015 at 1:02 PM, John Blakeman wrote: > I'd like to be ab

Access environment variables in screenrc

2015-03-07 Thread John Blakeman
I'd like to be able to put something like: shelltitle "$HOSTNAME" in my screenrc, and have it work. Furthermore, I'd like to access any environment variable in my screenrc that isn't a screen specific environment variable. Is this possible? Thanks, John ___

Re: environment variables

2013-12-18 Thread David T. Pierson
On Wed, Dec 11, 2013 at 12:06:36PM +0100, Nico Schlömer wrote: > I would like to execute a program in a shell that needs a custom path > added to LD_LIBRARY_PATH. This happens in my .bashrc by default, so > on the regular non-screen shell I'm getting no problems. > On a detached screen however, th

Re: environment variables

2013-12-11 Thread Aaron Davies
On Dec 11, 2013, at 6:06 AM, Nico Schlömer wrote: > David T. Pierson wrote: > >> If you want different behavior, please be more specific about what you are >> really trying to accomplish. > > I would like to execute a program in a shell that needs a custom path added > to LD_LIBRARY_PATH. T

Re: environment variables

2013-12-11 Thread Nico Schlömer
> If you want different behavior, please be more specific > about what you are really trying to accomplish. I would like to execute a program in a shell that needs a custom path added to LD_LIBRARY_PATH. This happens in my .bashrc by default, so on the regular non-screen shell I'm getting no prob

Re: environment variables

2013-12-06 Thread David T. Pierson
On Thu, Dec 05, 2013 at 10:08:36PM +0100, Nico Schlömer wrote: > I get > > $ screen > --> screen > $ echo $FOO > bar > > but a detached shell yields nothing: > > $ screen -s /bin/bash -L -d -m echo $FOO > $ There are a couple of things to say here. The lack of output has nothing to do with the

environment variables

2013-12-05 Thread Nico Schlömer
Hi all, I'm not quite sure what environment variables are set when executing an interactive screen vs. a detached screen. For example, when filling in this $ cat ~/.bashrc | grep FOO export FOO="bar" I get $ screen --> screen $ echo $FOO bar but a detached shell yields not

Re: passing environment variables through to screen

2012-07-04 Thread Mark Diekhans
Thanks for the response. In case this hits anyone else, the problem is this is a Linux security measure due to screen being setgid. This seems Linux-specifc in the system and specific to TMPDIR and certain other environments variables. See below. It's mentioned here: https://bugzilla

Re: passing environment variables through to screen

2012-07-03 Thread Kevin Van Workum
o pass through environment > variables when invoked? > > My particular problem is TMPDIR, which varies on different > systems we have. > > Thanks! > > ___ > screen-users mailing list > screen-users@gnu.org > https://list

passing environment variables through to screen

2012-07-02 Thread Mark Diekhans
Is there a way to cause screen to pass through environment variables when invoked? My particular problem is TMPDIR, which varies on different systems we have. Thanks! ___ screen-users mailing list screen-users@gnu.org https://lists.gnu.org/mailman

Updating DISPLAY, SSH and other environment variables

2011-09-02 Thread Surinder Singh
Hi All, After reattaching to a screen session, some of the environment variables need to be updated. I have seen some solution where the variables need to be explicitly updated (sourcing files). I haven't found any automated solution to this. My implementation below can do this automaticall

Re: Propagating environment variables ($STY and $WINDOW)

2008-05-29 Thread Ethan Mallove
On Sun, May/25/2008 10:41:42AM, Trent W. Buck wrote: > On Sat, May 24, 2008 at 05:23:25PM -0400, Ethan Mallove wrote: > > Is there a way to get the $STY and $WINDOW environment variables to > > propagate in an RSH/SSH session? E.g., if I start a Screen session, > > $STY and $

Re: Propagating environment variables ($STY and $WINDOW)

2008-05-24 Thread Trent W. Buck
On Sat, May 24, 2008 at 05:23:25PM -0400, Ethan Mallove wrote: > Is there a way to get the $STY and $WINDOW environment variables to > propagate in an RSH/SSH session? E.g., if I start a Screen session, > $STY and $WINDOW go away once I have RSH/SSH'd to another machine. The SendEn

Propagating environment variables ($STY and $WINDOW)

2008-05-24 Thread Ethan Mallove
Hello, Is there a way to get the $STY and $WINDOW environment variables to propagate in an RSH/SSH session? E.g., if I start a Screen session, $STY and $WINDOW go away once I have RSH/SSH'd to another machine. Thanks, Ethan ___ screen-users ma

Re: Passing Environment Variables In A Config File

2006-08-21 Thread Tom Purl
Thanks a *ton* Michael. I swear that I checked the man page numerous times before posting this question, but I just missed that option. Also, sorry for asking something that was solved a few days ago. I actually composed my question weeks ago and just joined the list. It's a long story, but I s

Passing Environment Variables In A Config File

2006-08-20 Thread Tom Purl
I looked around for a while to find a solution to this and could not. Any help at all would be greatly appreciated. I use screen on Linux to access a large number of Unix servers. Some of the terminal applications that I use on these Unix servers don't recognize a TERM value of 'screen', so I usu

Re: Passing Environment Variables In A Config File

2006-08-18 Thread Michael Parson
On Fri, Aug 18, 2006 at 04:15:41PM -0500, Tom Purl wrote: > I looked around for a while to find a solution to this and could > not. Any help at all would be greatly appreciated. > > I use screen on Linux to access a large number of Unix servers. Some > of the terminal applications that I use on th

Passing Environment Variables In A Config File

2006-08-18 Thread Tom Purl
I looked around for a while to find a solution to this and could not. Any help at all would be greatly appreciated. I use screen on Linux to access a large number of Unix servers. Some of the terminal applications that I use on these Unix servers don't recognize a TERM value of 'screen', so I usu