From: Alex Riesen <raa.lkml@gmail.com>
To: glen@erskinedesign.com
Cc: Steven Noonan <steven@uplinklabs.net>, git@vger.kernel.org
Subject: Re: Git/Terminal issue
Date: Wed, 15 Jul 2009 14:51:47 +0200 [thread overview]
Message-ID: <81b0412b0907150551x718bd46eq6d5bc8f332a9db1f@mail.gmail.com> (raw)
In-Reply-To: <4A5DC56E.8050607@erskinedesign.com>
On Wed, Jul 15, 2009 at 14:02, Glen Swinfield<glen@erskinedesign.com> wrote:
> I cleared my .profile file but it didn't seem to have an effect. I also
> removed any aliases.
>
> If that's what it sounds like I'll have another dig around.
Just do
echo $PS1
and look at the commands it uses. If you just want to get rid
of the prompt set it to something trivial (i.e. "PS1=\w$ ")
prev parent reply other threads:[~2009-07-15 12:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-15 11:27 Git/Terminal issue GleMarS
2009-07-15 11:51 ` Michael J Gruber
2009-07-15 11:51 ` Steven Noonan
2009-07-15 12:02 ` Glen Swinfield
2009-07-15 12:51 ` Alex Riesen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=81b0412b0907150551x718bd46eq6d5bc8f332a9db1f@mail.gmail.com \
--to=raa.lkml@gmail.com \
--cc=git@vger.kernel.org \
--cc=glen@erskinedesign.com \
--cc=steven@uplinklabs.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).