Re: An Embarrassing Progblem

2017-01-24 Thread S. P. Molnar
On 01/23/2017 04:21 PM, Ben Caradoc-Davies wrote: On 24/01/17 09:09, to...@tuxteam.de wrote: There should be a session file somewhere in ~/.config (sorry I have no more details). Perhaps XFCE honors ~/.xinitrc, ~/.xsessionrc or some of their siblings. I use ~/.config/xfce4/xinitrc to set envi

Re: An Embarrassing Progblem

2017-01-23 Thread Ben Caradoc-Davies
On 24/01/17 09:09, to...@tuxteam.de wrote: There should be a session file somewhere in ~/.config (sorry I have no more details). Perhaps XFCE honors ~/.xinitrc, ~/.xsessionrc or some of their siblings. I use ~/.config/xfce4/xinitrc to set environment variables before XFCE starts: #!/bin/sh #

Re: An Embarrassing Progblem

2017-01-23 Thread Kent West
On Mon, Jan 23, 2017 at 2:09 PM, wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Mon, Jan 23, 2017 at 07:58:01PM +, der.hans wrote: > > Am 23. Jan, 2017 schwätzte S. P. Molnar so: > > > > moin moin Stephen, > > > > > > > >On 01/23/2017 01:38 PM, der.hans wrote: > > >>grep PS1

Re: An Embarrassing Progblem

2017-01-23 Thread tomas
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, Jan 23, 2017 at 07:58:01PM +, der.hans wrote: > Am 23. Jan, 2017 schwätzte S. P. Molnar so: > > moin moin Stephen, > > > > >On 01/23/2017 01:38 PM, der.hans wrote: > >>grep PS1 ~/.bashrc ~/.bash_profile ~/.profile > > > >Thanks for the an

Re: An Embarrassing Progblem

2017-01-23 Thread der.hans
Am 23. Jan, 2017 schwätzte S. P. Molnar so: moin moin Stephen, On 01/23/2017 01:38 PM, der.hans wrote: grep PS1 ~/.bashrc ~/.bash_profile ~/.profile Thanks for the answers. I thought that i had the solution. Grep showed me that ps1 was only in .bashrc. After making a copy of .bashrc I r

Re: An Embarrassing Progblem

2017-01-23 Thread Greg Wooledge
On Mon, Jan 23, 2017 at 02:43:12PM -0500, S. P. Molnar wrote: > I added PS1="\u@\h >" to the end of .bashrc and sourced the file - it > worked, in that terminal. However, if I open a new terminal (I'm using > xfce4-terminal) the prompt is back to the corrupted one! Normally when you open a ter

Re: An Embarrassing Progblem

2017-01-23 Thread S. P. Molnar
On 01/23/2017 01:38 PM, der.hans wrote: grep PS1 ~/.bashrc ~/.bash_profile ~/.profile Thanks for the answers. I thought that i had the solution. Grep showed me that ps1 was only in .bashrc. After making a copy of .bashrc I removed the entire if ... fi section that contained PS1. I added

Re: An Embarrassing Progblem

2017-01-23 Thread der.hans
Am 23. Jan, 2017 schwätzte S. P. Molnar so: moin moin Stephen, check for PS1 in ~/.bashrc, ~/.bash_profile and ~/.profile. grep PS1 ~/.bashrc ~/.bash_profile ~/.profile If you don't find it that way, check to see if any of those include another rc file. You can set PS1 at the bottom of ~/.bas

Re: An Embarrassing Progblem

2017-01-23 Thread Ben Caradoc-Davies
On 24/01/17 07:27, S. P. Molnar wrote: I'm embarrassed to admit it. but I am completely confused. Somehow, I don't know how I managed to reset my bash user prompt. Rather than the default user prompt '\u@h >', it has morphed to (p4env). I have found plenty of Google results about correcting the

Re: An Embarrassing Progblem

2017-01-23 Thread Greg Wooledge
On Mon, Jan 23, 2017 at 01:27:05PM -0500, S. P. Molnar wrote: > I have found plenty of Google results about correcting thei promled, > and, indeed export PS1='\u@\h > ' restores the prompt - that is, until I > close that terminal. The next time I open a terminal the prompt is back > to (p4env).

An Embarrassing Progblem

2017-01-23 Thread S. P. Molnar
I'm embarrassed to admit it. but I am completely confused. Somehow, I don't know how I managed to reset my bash user prompt. Rather than the default user prompt '\u@h >', it has morphed to (p4env). I have found plenty of Google results about correcting thei promled, and, indeed export PS1='\u