What I learned was that the spaces are important!.
Thanks to all who contributed.
Ralph Pass
Scott Haneda wrote:
Very cool. I had a few functions, but this is a handy one. I did not
know I could just set the CLIFORCE_COLOR for the one session. I also
like how I believe you pass in the $@,
On Oct 7, 2009, at 14:38, Scott Haneda wrote:
Was your use of CLICOLOR_FORCE=X meant literally, or should I use
boolean? I have used boolean in the past, and the man page for ls
does not state what 'X" does, though it does work.
Perhaps it doesn't look at what value CLICOLOR_FORCE is set
Very cool. I had a few functions, but this is a handy one. I did not
know I could just set the CLIFORCE_COLOR for the one session. I also
like how I believe you pass in the $@, so I can send in arguments to
my ls alias, which I was not able to do in the past.
Was your use of CLICOLOR_FOR
Hi Scott
If stdout is not a terminal then "ls" disables color information by
default. So if you want to pipe it to anything like grep then you
*must* have CLICOLOR_FORCE in the environment.
But as Brandon points out, that can bite you in general ... perhaps
you want to define an alias wi
On Oct 6, 2009, at 6:22 PM, Brandon Allbery wrote:
So, can I use it and not export it? It seems in all examples I can
find, CLICOLOR_FORCE needs to be exported, but maybe there is a
"set" way to do it, 'SET CLICOLOR_FORCE' in which case it would not
be exported, but just available to me fo
On Oct 4, 2009, at 21:17 , Scott Haneda wrote:
If I do not have my aliases and such in .bashrc, my `sudo -s` env
is pretty stark, and hard to work in. I do not need all my
settings to come over when in this `sudo -s` mode, but I certainly
would like the macports paths and other things to mak
On 2009-10-04 , at 18:17 , Scott Haneda wrote:
I usually set up a line like that on all my remote machines, so when
I ssh in, I am greeted with something that tells me what machine I
am on. Most have the same username, and I try not to add too much
data to the PS1 setting, as long paths ca
Many years ago (when bash2 was being introduced) I tried to work out a
set of startup files that would work in all the environments I might
use. I didn't get there, but found some workable compromises, which I
have used as a basis since.
The main difference, for me, was between interactive
Thanks for all this great info, I think I am getting a handle on it
much better now. I always had it hobbled together, but do believe I
am getting to a point where I understand the repercussions of the
files and settings I am creating. More comments inline below...
On Oct 2, 2009, at 9:19
On Oct 2, 2009, at 14:49 , Harald Hanche-Olsen wrote:
+ Brandon Allbery :
If you run vi and type ":!ls", vi will spawn a noninteractive shell to
run "ls". Noninteractive shells are also used by "make", "port", and
numerous other commands.
Note, however, that these invoke /bin/sh and not bash.
You might want to read the first several chapters of Kernighan and
Pike's _The Unix Programming Environment_; the sections about shell
programming will clarify quite a bit of what's going on with the
environment and various startup files, even though it predates bash.
--
brandon s. allbery
On Oct 2, 2009, at 16:14 , Scott Haneda wrote:
What specifically is an environment setting? This means PATH would
be a bad thing to have in .bashrc? What I do is work in my user
account, I have aliases, and other helper things as well as the PATH
adjustments to MacPorts.
Anything you set
Thank you! comments below...
On Oct 1, 2009, at 5:21 PM, Brandon Allbery wrote:
On Oct 1, 2009, at 17:41 , Scott Haneda wrote:
I need to understand this once and for all, there is varying info
on this, the bash man page is verbose and not entirely clear.
When bash is invoked as an inte
+ Brandon Allbery :
> If you run vi and type ":!ls", vi will spawn a noninteractive shell to
> run "ls". Noninteractive shells are also used by "make", "port", and
> numerous other commands.
Note, however, that these invoke /bin/sh and not bash. Even if /bin/sh
is bash, it will behave more like
On Oct 1, 2009, at 17:41 , Scott Haneda wrote:
I need to understand this once and for all, there is varying info on
this, the bash man page is verbose and not entirely clear.
When bash is invoked as an interactive login shell, or as a
non-inter-
active shell with the --login opt
I need to understand this once and for all, there is varying info on
this, the bash man page is verbose and not entirely clear.
When bash is invoked as an interactive login shell, or as a
non-inter-
active shell with the --login option, it first reads and
executes com-
16 matches
Mail list logo
