My .bashrc and the command prompt.

Software:
Distro: Debian 12
My .bashrc
github.com/drewgrif/jag_dots/...
Github:
github.com/drewgrif/
Fosstodon:
fosstodon.org/@justaguylinux
Twitter:
/ justaguylinux
Proton Mail:
pr.tn/ref/CBK96TN0ZDAG

[@TheLinuxCast]

The ssh thing is a great idea!

[@JustAGuyLinux]

Thanks pal. 👍

[@TheChrissutcliffe]

I enjoyed the video as you provided a clear explanation of your bashrc and I like the fact that you have kept things simple.

[@penguin2137]

you inspired me to do some cleaning in my .bashrc file - i've been planning that some time ago but it was just today i was able to move my lazy a** for that purpose

[@backhdlp]

a cool alias I have is s='sudo '. it does the obvious of shortening sudo to s to be quicker, but the space at the end also means that it still understands aliases.

[@cwarehime]

Hey great video, it's very simple I Love it! Easy to understand and use. If I had to explain my environment (28+ yrs inside my .bashrc) it would not be pretty.

[@bokami3445]

Admitted your 'x' command is handy and shorter, ctrl-d does the same thing, Plus if you alias apt='sudo apt' and then include your install, upgrade, uplist.... if you decide to switch to nala, you only need to change the one entry and all your other aliases will switch from apt to nala.

[@jonatdrmarlo]

Thanks!

[@mikel8190]

I've been using most of those same git aliases for years. Enjoyed the video. It helped make my PS1 actually readable.

[@kychemclass5850]

I have conflicting feelings about aliases... reliance on them lowers memory retention of the 'proper' commands/syntax, establishing non-standard stuff within you which carriers future potential problems. The standard syntax carries a logical structure which aliases reduce your exposure to. Personally I still feel time isn't right for me alias everything, I try to stick to original command/syntax especially when a command is short.
But they can save a _lot_ of time and if a reference to the aliases is available (cat ~/.bashrc) then any problems are largely mitigated.
The case for aliases get very strong for more complex the commands need to be and a great way to 'pseudo PATH' to scripts.
I'm probably saying the blindingly obvious but to new users to think of these things is I feel, important.

[@nosotrosloslobosestamosreg4115]

Thank you for sharing your aliases. I'll implement some of them in my bashrc and zshrc.

[@philippef.4590]

Thank you

[@ricardoreinasgiordano3846]

your alias combination is very interesting 👍👍👍

[@JustAGuyLinux]

Thanks 😁

[@PeterBuffon]

Me seeing those aliases and feeling dumb to why i`ve never thought of to use some of them hehehehe.

[@JustAGuyLinux]

Let's get one thing straight. Anyone who watches my channel could never be considered dumb. 😉

[@youtubewzd2196]

I went and put my aliases into ~/.alias and source them from my .bashrc. This way I can reuse them from zsh or fish in the same way.

[@jyvben1520]

why not use the .bash_aliases file, it is called automatically from .bashrc, i have added alias a to edit it ... and added b to edit .bashrc

[@alexstone691]

Install alias is cool but i usually avoid shadowing existing commands

[@user-hc6uo5fp8n]

Have you see hstr - easily view, navigate, sort and use your command history with shell history suggest box.

[@tubeincompetence]

I generally just switched to zsh instead. But this is still a nice video :)

[@ditierferreira2039]

Friend, would it be possible to introduce the JWM graphical environment into the custom script shown in the previous video? Congratulations on the videos and the excellent work

[@nastykerb34]

Wait.. Now sudo make install wont work if u use the install="sudo apt install". Unless you use which in the makefiel