this post was submitted on 30 Jul 2023
125 points (96.3% liked)
linuxmemes
21410 readers
809 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack members of the community for any reason.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudoin Windows. - No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Wait.. what? I didn't even consider this could be an option. Is anyone willing to point me at some accurate information about how to get started? Like.. where do I put a bash file, and how is it structured? How can I automate it? So many questions. I'm only sort of familiar with bash, as in I've seen the term and watched my coworker do some wizardry once.
I think this is an easier way to do it:
add this to a file called .bash_aliases instead (it should be a file right next to .bashrc, if not just create it)
You can add aliases to .bashrc with this, but I personally perfer to have aliases in their own file
Another thing, if you have a console window open while adding it, restart it so that the console is aware of the aliases. Alternatively, google something like "sourcing bashrc" or "sourcing aliases" and apply the commands you find
If you wish to add aliases to a bash script (for later automation), you add these two lines
shopt -s expand_aliases
source ~/.bash_aliases
but of course add this to the top of your bash scripts, so that your script knows to use the bash shell:
#!/bin/bash
This is so great. Thank you.