/dev/chat

« first day (1352 days earlier) ← previous day next day → last day (3593 days later) »

Braiam

1:10 AM

and UL has a new worst asked question

I'm sure we have a dupe for this unix.stackexchange.com/q/138504/41104

10 hours later…

Gilles

11:14 AM

@Braiam deleted by Community now! I flagged for undeletion

@Braiam unix.stackexchange.com/questions/110540/…, which hasn't been correctly answered

and unix.stackexchange.com/questions/26047/…, where it's buried in other considerations

Opinions? We have this question with a comprehensive answer (which happens to be mine):

Q: How to correctly add a path to PATH?

I'm wondering where a new path has to be added to PATH environment variable. I know this is accomplished editing .bash_rc (for example), but it's not clear how to do this. This way: export PATH=~/opt/bin:$PATH or this? export PATH=$PATH:~/opt/bin Question 2 (related). What's a workable way...

and these two questions which are more focused and have both had answers that don't actually answer the question:

Q: Adding Postgres bins to PATH: should I `export`?

I'm on a Mac, but this seems like a UNIX/Linux question. I just installed Postgres.app, and the documentation says to add the /bin directory that ships with Postgres.app to your PATH by adding the following line to .bashrc, it'll get set for every terminal session: PATH="/Applications/Postgres.a...

path postgresql

-1

Q: Setting PATH vs. exporting PATH in ~/.bash_profile

What's the difference and which is better to use when customizing my bash profile? Documentation on the export command is scarce, as it's a builtin cmd. Excerpt from version 1 of my ~/.bash-profile: #PATH export PATH=/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:$HOME/bin #add Homebrew’s sbin t...

bash terminal osx environment-variables path

should we close #2 and #3 as a duplicte of #1, or only #3 as a duplicate of #2?

and why was #3 downvoted?

Braiam

11:31 AM

@Gilles huh? the diamond Community?

@Gilles that seems more like "setting VAR vs. exporting VAR in ~/.bash_profile"

if we forget about "PATH" and treat them as variables we can get something canonical

Gilles

@Braiam Why forget about PATH? The general effect of export is best answered by looking it up in the shell manual. The specific circumstance of setting PATH, which is already in the environment, warrants a specific answer.

Braiam

@Gilles is my impression, going by the first lines, that he's more interested in the different ways to set variables (customizing his shell) than the special case of PATH

Braiam

11:53 AM

what's up with all those kernel/userspace questions?

polym

12:37 PM

@Braiam I agree with you, he's more interested in the meaning of export.

@Gilles It's nice that you commented that once its exported, it stays exported. But your first sentence can be understood that TEST4=TEST4=/usr/local/sbin:$TEST4 is equal to exporting the variable TEST4

also you added an additional PATH= infront of the cmd, which I think is a typo, or?

9 hours later…

Gilles

9:28 PM

@MichaelMrozek please merge module into kernel-modules then delete module

A: What's the diference between kernel-modules, kernel-drivers, drivers and modules?

My first impression is that kernel-drivers should be merged into drivers, and module was created by someone who typed kernel module as separate words and grew from there. This is to be confirmed by browsing through the questions list which I haven't done yet. Only 16 questions are tagged module ...

2 hours later…

Faheem Mitha

11:14 PM

Any Python users around?

Q: When does argparse not complain about this missing argument?

There is probably an obvious answer to this question, but I've looked at it for a bit without figuring it out. This is some old Python code using argparse. I haven't used argparse recently, so I may have forgotten some nuance. #test.py def load_crossval_dataset(args): schema, samplenum, per...