Am 02.08.2013 23:56, schrieb Joe Zeff:
> On 08/02/2013 02:30 PM, Tom Horsley wrote:
>> In fact, I have thwarted that on my system by running a
>> yum "hook" function that re-applies all my hacks every time
>> there is an update, but it is silly that I have to resort
>> to that.
>
> This is why I
Once upon a time, Joe Zeff said:
> Which helps if and only if you have a list of them and take the time
> to translate everything yourself. Putting in comments to make it
> easy to understand would be nice, but at this time, I'll refer you
> to what Rhett Butler said at the end of Gone With The W
On 08/02/2013 02:11 PM, Joe Zeff wrote:
<>
Which helps if and only if you have a list of them and take the time to
translate everything yourself. Putting in comments to make it easy to
understand would be nice, but at this time, I'll refer you to what Rhett
Butler said at the end of Gone With
On 8/2/2013 8:07 PM, Joe Zeff wrote:
> On 08/02/2013 05:00 PM, David wrote:
>> Well good then. You changed your system from the distroution defaults to
>> what you, personally, want. What works for you.
>>
>> Windows users do that. they set the default installed system to what
>> they want. MacOS u
On 08/02/2013 05:00 PM, David wrote:
Well good then. You changed your system from the distroution defaults to
what you, personally, want. What works for you.
Windows users do that. they set the default installed system to what
they want. MacOS users do that too. So all is good then?
I'd probab
On 8/2/2013 7:38 PM, Joe Zeff wrote:
> On 08/02/2013 04:20 PM, David wrote:
>> Then change youe user's config. That is not touched by system changes
>> and will override the system configurations. You should, so I do not
>> repeat, read my comment to Joe Zeff about this in this thread.
>
> And tha
On 08/02/2013 04:20 PM, David wrote:
Then change youe user's config. That is not touched by system changes
and will override the system configurations. You should, so I do not
repeat, read my comment to Joe Zeff about this in this thread.
And that's why I ended up doing exactly that. It gets m
On 8/2/2013 5:30 PM, Tom Horsley wrote:
> On Fri, 02 Aug 2013 16:08:26 -0400
> David wrote:
>
>> You do know that you can change the system default?
>
> Not very easily. Every time the package that owns the file
> gets an update, the original is put back.
>
> In fact, I have thwarted that on my
On 8/2/2013 4:22 PM, Joe Zeff wrote:
> On 08/02/2013 01:08 PM, David wrote:
>> You do know that you can change the system default? As well as changing
>> it in your users .bashrc file? The best of two worlds you and Joe get it
>> your way and the rest of the Fedora world gets it their way.
>
> Yes
On 08/02/2013 02:30 PM, Tom Horsley wrote:
In fact, I have thwarted that on my system by running a
yum "hook" function that re-applies all my hacks every time
there is an update, but it is silly that I have to resort
to that.
This is why I referred to my method as elegant: I don't need to know
On Fri, 02 Aug 2013 16:08:26 -0400
David wrote:
> You do know that you can change the system default?
Not very easily. Every time the package that owns the file
gets an update, the original is put back.
In fact, I have thwarted that on my system by running a
yum "hook" function that re-applies a
On Fri, 2 Aug 2013, Tom Horsley wrote:
On Fri, 02 Aug 2013 15:30:57 -0400
David wrote:
Many others like them since you are the
only user to complain.
No, he's not.
It is especially fun when your default terminal colors are
light foreground and dark background. Most ls output goes
almost inv
On 08/02/2013 01:08 PM, David wrote:
You do know that you can change the system default? As well as changing
it in your users .bashrc file? The best of two worlds you and Joe get it
your way and the rest of the Fedora world gets it their way.
Yes, and that's why instead of wasting time with a p
On 08/02/2013 12:50 PM, Tom Horsley wrote:
On Fri, 02 Aug 2013 15:30:57 -0400
David wrote:
Many others like them since you are the
only user to complain.
No, he's not.
It is especially fun when your default terminal colors are
light foreground and dark background. Most ls output goes
almost
On 8/2/2013 1:08 PM, David wrote:
On 8/2/2013 3:50 PM, Tom Horsley wrote:
[...]
So there is *two* of you? :-)
Seriously I can see your problem here. I seriously doubt there are plans
to change this or make a GUI to change it. And I seriously doubt that
comments here will make any difference.
Hi Joe,
On Fri, Aug 02, 2013 at 12:11:58PM -0700, Joe Zeff wrote:
> On 08/02/2013 12:03 PM, David wrote:
> >Unless something changed when I was not looking the codes you refer to
> >are ANSI color and ANSI control codes.
>
> Which helps if and only if you have a list of them and take the time to
On 08/02/2013 12:30 PM, David wrote:
As for the colors? Linux is about choice. You don't like them? Remove
them and go on your merry way. Many others like them since you are the
only user to complain.
Or, and this is a distinct possibility, I'm the only one who doesn't
like them and is aware
On 8/2/2013 3:50 PM, Tom Horsley wrote:
> On Fri, 02 Aug 2013 15:30:57 -0400
> David wrote:
>
>> Many others like them since you are the
>> only user to complain.
>
> No, he's not.
>
> It is especially fun when your default terminal colors are
> light foreground and dark background. Most ls outp
On Fri, 02 Aug 2013 15:30:57 -0400
David wrote:
> Many others like them since you are the
> only user to complain.
No, he's not.
It is especially fun when your default terminal colors are
light foreground and dark background. Most ls output goes
almost invisible.
--
users mailing list
users@lis
On 8/2/2013 3:11 PM, Joe Zeff wrote:
> On 08/02/2013 12:03 PM, David wrote:
>> Unless something changed when I was not looking the codes you refer to
>> are ANSI color and ANSI control codes.
>
> Which helps if and only if you have a list of them and take the time to
> translate everything yoursel
On 08/02/2013 12:03 PM, David wrote:
Unless something changed when I was not looking the codes you refer to
are ANSI color and ANSI control codes.
Which helps if and only if you have a list of them and take the time to
translate everything yourself. Putting in comments to make it easy to
und
On 8/2/2013 2:21 PM, Joe Zeff wrote:
> On 08/02/2013 05:27 AM, Darryl L. Pierce wrote:
>> The colors are defined in /etc/profile.d/colorls.sh:
>
> Reading that, the alias is set up, but there's no listing of which color
> means what. And, if you do track that down, it's all in hex codes, so
> tha
On 08/02/2013 05:27 AM, Darryl L. Pierce wrote:
The colors are defined in /etc/profile.d/colorls.sh:
Reading that, the alias is set up, but there's no listing of which color
means what. And, if you do track that down, it's all in hex codes, so
that there's no easy way to find out what those
On 08/02/2013 05:27 AM, Darryl L. Pierce issued this missive:
On Thu, Aug 01, 2013 at 11:49:27AM -0700, Joe Zeff wrote:
On 08/01/2013 06:20 AM, Tom Horsley wrote:
On Thu, 01 Aug 2013 09:07:07 -0400
Neal Becker wrote:
I suspect colored prompts are confusing emacs tramp. What's the easiest way
On Thu, Aug 01, 2013 at 11:49:27AM -0700, Joe Zeff wrote:
> On 08/01/2013 06:20 AM, Tom Horsley wrote:
> >On Thu, 01 Aug 2013 09:07:07 -0400
> >Neal Becker wrote:
> >
> >>I suspect colored prompts are confusing emacs tramp. What's the easiest
> >>way to
> >>turn it off for all users (especially r
On 08/01/2013 12:18 PM, Suvayu Ali wrote:
The colours the OP is refering to is not the coloured output of ls.
That is controlled by the environment variable LS_COLORS. The OP has to
make sure his PS1 variable does not have any ANSI colour escapes. If
you are interested, take a look at my respon
On Thu, Aug 01, 2013 at 11:49:27AM -0700, Joe Zeff wrote:
> On 08/01/2013 06:20 AM, Tom Horsley wrote:
> >On Thu, 01 Aug 2013 09:07:07 -0400
> >Neal Becker wrote:
> >
> >>I suspect colored prompts are confusing emacs tramp. What's the easiest
> >>way to
> >>turn it off for all users (especially r
On 08/01/2013 06:20 AM, Tom Horsley wrote:
On Thu, 01 Aug 2013 09:07:07 -0400
Neal Becker wrote:
I suspect colored prompts are confusing emacs tramp. What's the easiest way to
turn it off for all users (especially root)?
There is a whole slew of things in /etc/profile that turn on
annoying e
On Thu, 01 Aug 2013 09:07:07 -0400
Neal Becker wrote:
> I suspect colored prompts are confusing emacs tramp. What's the easiest way
> to
> turn it off for all users (especially root)?
There is a whole slew of things in /etc/profile that turn on
annoying environment variables which enable thing
On Thu, Aug 01, 2013 at 09:07:07AM -0400, Neal Becker wrote:
> I suspect colored prompts are confusing emacs tramp. What's the easiest way
> to
> turn it off for all users (especially root)?
You have to set your PS1 in your ~/.bashrc such that there are no colour
escapes. This is what I do:
I suspect colored prompts are confusing emacs tramp. What's the easiest way to
turn it off for all users (especially root)?
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Co
31 matches
Mail list logo
