[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: decoding error message
From: |
asha g |
Subject: |
Re: decoding error message |
Date: |
Wed, 18 Feb 2009 05:40:59 +0530 (IST) |
This is the message i get after running it on Octave 3.0
gnuplot: unable to open display ':0.0'
gnuplot: X11 aborted.
octave:3> Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
Asha
Goals too clearly defined can become blinkers. Mary Catherine
Bateson
--- On Mon, 16/2/09, Søren Hauberg <address@hidden> wrote:
> From: Søren Hauberg <address@hidden>
> Subject: Re: decoding error message
> To: address@hidden
> Cc: address@hidden
> Date: Monday, 16 February, 2009, 12:25 PM
> man, 16 02 2009 kl. 12:18 +0530, skrev asha g:
> > I tried that and get the following message:
> > warning: 3.0.0: no such file or directory
> >
> > So does it mean that octave 2.1.57 cannot read the
> legend command? It was working earlier.
>
> Octave 2.1.57 does not have the 'legend' command.
> As long as you're
> using this (very old) version you will not be able to use
> that command.
> You should figure out why you're starting version
> 2.1.57 instead of
> version 3.0. I'm not sure why this is happening,
> though. What OS are you
> using?
>
> Søren
Connect with friends all over the world. Get Yahoo! India Messenger at
http://in.messenger.yahoo.com/?wm=n/
- decoding error message, asha g, 2009/02/16
- Re: decoding error message, Søren Hauberg, 2009/02/16
- Re: decoding error message, asha g, 2009/02/16
- Re: decoding error message, Søren Hauberg, 2009/02/16
- Re: decoding error message, asha g, 2009/02/16
- Re: decoding error message, Søren Hauberg, 2009/02/16
- Re: decoding error message, asha g, 2009/02/16
- Re: decoding error message,
asha g <=
- Re: decoding error message, Ben Abbott, 2009/02/17
- Re: decoding error message, asha g, 2009/02/17
- Re: decoding error message, Ben Abbott, 2009/02/17
- Re: decoding error message, Jordi Gutiérrez Hermoso, 2009/02/17
- Re: decoding error message, asha g, 2009/02/17
- Re: decoding error message, Rob Mahurin, 2009/02/18