On Tue, Jan 4, 2022 at 3:38 PM Greg Wooledge wrote:
> On Tue, Jan 04, 2022 at 03:34:05PM -0500, Matthew Persico wrote:
> > On Fri, Dec 31, 2021 at 10:33 AM Greg Wooledge
> wrote:
> > > You can edit the file yourself and make it work however you like. You
> > > have the right idea, but I'd write
On Tue, Jan 04, 2022 at 03:34:05PM -0500, Matthew Persico wrote:
> On Fri, Dec 31, 2021 at 10:33 AM Greg Wooledge wrote:
> > You can edit the file yourself and make it work however you like. You
> > have the right idea, but I'd write it like this:
> >
> > if [[ -d ~/.bash_aliases.d ]]; then
> >
On Fri, Dec 31, 2021 at 10:33 AM Greg Wooledge wrote:
> On Thu, Dec 30, 2021 at 08:46:16PM -0800, Kevin O'Gorman wrote:
> > So I propose extending the stanza near the end of .bashrc:
> > if [ -f ~/.bash_aliases ]; then
> > . ~/.bash_aliases
> > fi
>
> That code was written by your operating
On Thu, Dec 30, 2021 at 08:46:16PM -0800, Kevin O'Gorman wrote:
> So I propose extending the stanza near the end of .bashrc:
> if [ -f ~/.bash_aliases ]; then
> . ~/.bash_aliases
> fi
That code was written by your operating system vendor, or by your
system administrator, or by you. It's not
i have a sys that produces bash code out of tree's, so i can have aliases
and stuff in separate files, .. just my suggestion
On Fri, Dec 31, 2021, 09:19 Kevin O'Gorman wrote:
> I see the bash web page on Xubuntu gives this email address for requests
> and such. Nice. It also gives a usenet gro
I see the bash web page on Xubuntu gives this email address for requests
and such. Nice. It also gives a usenet group as an alternative. I did
not know usenet was still around.
Anyway, my problem is thatI have so many things added to my .bashrc (well
to .bash_aliases really), and they've become
