From: Peter Humphrey <peter@prh.myzen.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] New bashrc
Date: Sun, 07 Jul 2024 00:10:27 +0100 [thread overview]
Message-ID: <2756479.mvXUDI8C0e@cube> (raw)
In-Reply-To: <a46df2a4-4b64-685a-ff7a-5c23217a227e@gmail.com>
On Saturday, 6 July 2024 17:31:08 BST Dale wrote:
> Hope those files help.
Thank you Dale. In fact my problem turned out to be an invisible typo in a
bash script. You know, the sort that isn't there until the umpteenth time you
look, and there it is after all. :)
--
Regards,
Peter.
next prev parent reply other threads:[~2024-07-06 23:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-06 14:34 [gentoo-user] New bashrc Peter Humphrey
2024-07-06 16:31 ` Dale
2024-07-06 23:10 ` Peter Humphrey [this message]
2024-07-07 1:29 ` Dale
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=2756479.mvXUDI8C0e@cube \
--to=peter@prh.myzen.co.uk \
--cc=gentoo-user@lists.gentoo.org \
/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