From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] New bashrc
Date: Sat, 6 Jul 2024 20:29:30 -0500 [thread overview]
Message-ID: <8610fc97-0789-f789-e3aa-eea2cb16e715@gmail.com> (raw)
In-Reply-To: <2756479.mvXUDI8C0e@cube>
Peter Humphrey wrote:
> 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. :)
>
Maybe that was my problem as well. My main rig update went fairly
well. The new rig, which had a fresh new set of never altered files,
went sideways. I really hated over writing the files that way but I
didn't know of a better way.
Given that things are moving to a directory now, I wish someone would
write a really good wiki page on how the new way works and have some
examples. One thing I don't know and haven't found a answer too, the
numbers. Does it read from low to high? That makes sense. Does a
setting from a file with a higher number override settings for files
with lower numbers? That's a biggie. When I tried to set my PS1
variable, it clashed with a Gentoo file which set the same variable. It
seems one doesn't override the other but turns into a wreck, with
injuries. My bash kinda got weird. I couldn't login at all.
I suspect someone will write one at some point. I just wish it was
sooner rather than later. I'm not clear on a few things.
Glad to help. :-D
Dale
:-) :-)
P. S. I might add, xorg.conf is doing the same thing and I have the
same questions about it. It seems a lot of things are going the
directory route and it can be a good thing, just confusing at times.
prev parent reply other threads:[~2024-07-07 1:29 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
2024-07-07 1:29 ` Dale [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=8610fc97-0789-f789-e3aa-eea2cb16e715@gmail.com \
--to=rdalek1967@gmail.com \
--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