| Re: how to suppres warning [message #63069 is a reply to message #62976] |
Wed, 22 October 2008 09:59   |
astroboy2k
Messages: 34
Registered: July 2007
|
Member |
|
|
On Oct 22, 10:53 am, Paul van Delst <Paul.vanDe...@noaa.gov> wrote:
> Mark wrote:
>> Well, as long as this topic has come up....
>
>> In alot of my code (running bash on unix) I get this warning printed
>> to the screen:
>
>> bash: defaults: command not found
>
>> along with other occasional warnings that bash isn't happy for some
>> reason I can't comprehend.
>
>> I really have no idea at what point in the code(s) that this warning
>> originates from, but since everything works fine I'd just as soon
>> suppress it. Does anyone know how this might be done easily, either in
>> IDL or unix?
>
> Err...this is also off-topic, but don't you have any curiosity to find out what is causing
> the problem? With google at your fingertips it's easy to get at least an idea if not the
> outright answer. E.g. Have you checked your .profile, .login, .bashrc, .bash_profile, or
> the various /etc forms of those files to see where the "defaults" command is being called,
> why is it being called, and why it isn't in your path?
>
> You know, this topic reminds me of callers to the NPR show "Car Talk". People describe
> these sometimes bizarre things that are happening (noises, shaking, other weird stuff) as
> they drive their cars. The inevitable question "How long has this been going on?" comes up
> and the answers typically range from several weeks to months in some cases. It never
> ceases to amaze me what people will put up with. :o)
>
> cheers,
>
> paulv
Well yes, I am curious, and yes, I have looked into it, and no, I
can't figure out what the problem is for the life of me.
Unfortunately, my employers don't pay me to program in IDL just for
the sake of writing elegant IDL programs; they want answers. If I want
to keep my job an occasional warning which does nothing but clutter my
screen is something I have to write off after having given it the old
college try to fix it.
As long as this topic had come up I thought I might mention it; I
wouldn't have wasted the bandwidth or the time of the people who
kindly have helped me out so many times otherwise. I thought possibly
there was some IDL or unix fix that would suppress this sort of
message that was likely common knowledge.
Having said that, I'm afraid my message did come across like I was
asking someone else to do my thinking for me out of laziness. Sorry
'bout that.
Mark
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
