Linux

48255 readers

925 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

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

How to make it such that, when running command, it automatically does SOME_ENV_VAR=value command? (something cleaner than aliases?) (lemmy.ml)

submitted 1 year ago by cyclohexane@lemmy.ml to c/linux@lemmy.ml

21 comments fedilink hide all child comments

hello friends,

I am looking for a way to do what I described in the title. When running command command, I dont want to have to type SOME_ENV_VAR=value command every time, especially if there are multiple.

I am sure youre immediately thinking aliases. My issue with aliases is that if I do this for several programs, my .bashrc will get large and messy quickly. I would prefer a way to separate those by program or application, rather than put them all in one file.

Is there a clean way to do this?

you are viewing a single comment's thread
view the rest of the comments

[–] nicoag328@lemmy.ml 9 points 1 year ago (2 children)

You could source an aliases.sh file on your .bashrc where you define your aliases, so that they don't fill up your bashrc.

For example, in your bashrc:

source ~/.aliases.sh

This way you could also create a file with aliases per program.

[–] treadful@lemmy.zip 7 points 1 year ago (1 children)

FYI: $HOME/.bash_aliases is standard and most distros' .bashrc will source that file by default.

[–] oranki@sopuli.xyz 2 points 1 year ago (1 children)

Most Debian based distros, actually.

[–] treadful@lemmy.zip 1 points 1 year ago

And at least arch. Probably others.

[–] cyclohexane@lemmy.ml 1 points 1 year ago (1 children)

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

[–] nicoag328@lemmy.ml 1 points 1 year ago

You can source other files inside aliases.sh or as @treadful noted .bash_aliases

.bash_aliases:

source .aliases/program_x.sh source .aliases/program_y.sh

This 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/