10
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 06 Jul 2023
10 points (100.0% liked)
Linux
48143 readers
747 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
You could source an
aliases.shfile on your .bashrc where you define your aliases, so that they don't fill up your bashrc.For example, in your bashrc:
source ~/.aliases.shThis way you could also create a file with aliases per program.
That's a good idea, but it only makes the problem a little better. I still wouldn't want one large aliases.sh file with environment variables for every application I customized. Would rather have them separate somehow without gobbling up a file
You can source other files inside
aliases.shor as @treadful noted.bash_aliases.bash_aliases:source .aliases/program_x.shsource .aliases/program_y.shThis way you can have a file with aliases for each application or group of applications.
But it would be helpful if you provided more information on what you really want to do. Read https://xyproblem.info/