From: "Pascal J. Bourguignon" <pjb@informatimago.com>
To: cygwin@cygwin.com
Subject: Re: Username and Computer Name
References: <20120514210137.66526dtb5pmnlatd@www.kalani.com>
Reply-to: pjb@informatimago.com
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Date: Tue, 15 May 2012 05:19:14 +0200
In-Reply-To: <20120514210137.66526dtb5pmnlatd@www.kalani.com>	(max@kalani.com's message of "Mon, 14 May 2012 21:01:37 -0500")
Message-ID: <87d366872l.fsf@kuiper.lan.informatimago.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux)
MIME-Version: 1.0
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

max@kalani.com writes:

> Could you please explain more into detail on how to obtain a PS1?

What else can we tell you?  You've been explained how to learn about it,
and you haven't.  What can we do?

> Run 'man bash' and look for PS1. Remove the '\u@\h' part. To make
> the change permanent, set your own PS1 in '~/.bash_profile'. This
> isn't cygwin specific, so you can google for more details.


If you don't know how to look for a string in a text by reading that
text, you could try to use a computer command:


   man bash | grep -C 3  PS1


But since you couldn't type the man bash command, I don't expect you to
be able to type the more complex man bash | grep -C 3  PS1 command.  And
since you've not been able to read the bash manual, how could I expect
you to be able to read the extracts?

-- 
__Pascal Bourguignon__                     http://www.informatimago.com/
A bad day in () is better than a good day in {}.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple