mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Alexander Dahl <post@lespocky.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] ptxdist: Don't assume that we have a bashrc
Date: Wed, 21 Mar 2012 09:40:59 +0100	[thread overview]
Message-ID: <4F69941B.7020509@lespocky.de> (raw)
In-Reply-To: <4F697273.3070504@bwalle.de>


[-- Attachment #1.1: Type: text/plain, Size: 996 bytes --]

Hei hei,

Am 21.03.2012 07:17, schrieb Bernhard Walle:
>> I'm using zsh, not bash, but still have ~/.bashrc … what does this code
>> try to do in the first place and how does this affect users of other shells?
> 
> It only avoids two error messages when running "ptxdist bash" when the
> files are not present. You can also use bash and have no ~/.bashrc
> although that might be seldom.

Okay, then let's rephrase this. From `ptxdist help` I got:

  bash                          enter a ptxdist environment bash shell
  bash <cmd> [args...]          execute <cmd> in ptxdist environment

What is this environment useful for or what advantages has `ptxdist
bash` over my own shell?

Greets
Alex

-- 
»With the first link, the chain is forged. The first speech censured,
the first thought forbidden, the first freedom denied, chains us all
irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie)
*** GnuPG-FP: 02C8 A590 7FE5 CA5F 3601  D1D5 8FBA 7744 CC87 10D0 ***


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

[-- Attachment #2: Type: text/plain, Size: 48 bytes --]

-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2012-03-21  8:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-20 19:46 Bernhard Walle
2012-03-20 22:15 ` Alexander Dahl
2012-03-21  6:17   ` Bernhard Walle
2012-03-21  8:40     ` Alexander Dahl [this message]
2012-03-21  8:43       ` Bernhard Walle

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=4F69941B.7020509@lespocky.de \
    --to=post@lespocky.de \
    --cc=ptxdist@pengutronix.de \
    /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