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
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.
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.
Your videos are very helpful. Thank you! One thing that irks me (and is my issue) is when people say slash for a back slash and vice versa. See about the 4 min. mark “ ”. I’m sure that I have other issues that others have already mastered, just ask my wife. 😉 Also, I noticed in the comments that you said you now use DWM. Maybe your video where you say that you love/use XFCE, is a newer video? In any case, I would love to try out multiple WM options and I believe that is a huge reason people are drawn to Linux. I remember tinkering with as many Win95/98 colors and border settings as I could. But alas, there is work to do! That’s about the only good thing about Windows, they only let you work. 🤣🤣🤣 Where’s my old Erector set and Lincoln logs? 😉
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.
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
I put separated shell scripts inside ~/.bashrc.d directory instead of override the ~/.bashrc file and I can carry that directory to every distribution.
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.
Ctrl+L , to clear your screen , Ctrl+D to close your session, EZA - can be installed via homebrew - add it to your path, Aliases always nice keeping a separate alias file. Great vids I always rethink how I can be more effiicient in bash likewise your vids always make me seek to learn other ways. Great job as always.
Oops forgot to mention don't use tr - truncate for tree command - this is a conflict. just use tree or I use eza and my alias is lta for tree functionality
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
You help me a lot, thanks. I learn with you
Thank you for sharing your aliases. I'll implement some of them in my bashrc and zshrc.
I've been using most of those same git aliases for years. Enjoyed the video. It helped make my PS1 actually readable.
Thank you
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.
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.
your alias combination is very interesting 👍👍👍
Thanks 😁
Your videos are very helpful. Thank you!
One thing that irks me (and is my issue) is when people say slash for a back slash and vice versa. See about the 4 min. mark “
”.
I’m sure that I have other issues that others have already mastered, just ask my wife. 😉
Also, I noticed in the comments that you said you now use DWM. Maybe your video where you say that you love/use XFCE, is a newer video?
In any case, I would love to try out multiple WM options and I believe that is a huge reason people are drawn to Linux. I remember tinkering with as many Win95/98 colors and border settings as I could.
But alas, there is work to do! That’s about the only good thing about Windows, they only let you work. 🤣🤣🤣
Where’s my old Erector set and Lincoln logs? 😉
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.
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
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.
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
Wait.. Now sudo make install wont work if u use the install="sudo apt install". Unless you use which in the makefiel
The ssh thing is a great idea!
Thanks pal. 👍
Me seeing those aliases and feeling dumb to why i`ve never thought of to use some of them hehehehe.
Let's get one thing straight. Anyone who watches my channel could never be considered dumb. 😉
Have you see hstr - easily view, navigate, sort and use your command history with shell history suggest box.
i Drew, Which window manager do you recommend?
I use dwm but if you are new to window managers I would start with i3 or bspwm. I like bspwm better
@@JustAGuyLinux thanks drew. I will do with your tutorial. Keep going.
Install alias is cool but i usually avoid shadowing existing commands
Thanks!
I put separated shell scripts inside ~/.bashrc.d directory instead of override the ~/.bashrc file and I can carry that directory to every distribution.
I generally just switched to zsh instead. But this is still a nice video :)
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.
Ctrl+L , to clear your screen , Ctrl+D to close your session, EZA - can be installed via homebrew - add it to your path, Aliases always nice keeping a separate alias file. Great vids I always rethink how I can be more effiicient in bash likewise your vids always make me seek to learn other ways. Great job as always.
Oops forgot to mention don't use tr - truncate for tree command - this is a conflict. just use tree or I use eza and my alias is lta for tree functionality
I enjoyed the video as you provided a clear explanation of your bashrc and I like the fact that you have kept things simple.