You are not logged in.
I put ${weather http://xoap.weather.com/weather/local/ 02645 temperature} in my .conkyrc, but all it does is display '${weather}' on the screen. I have the Partner ID and License Key in ~/.xaoprc. Can anyone tell me what's wrong?
Offline
Without actually listing your .xaoprc, it would be difficult for anyone to help you. Try starting conky from CLI and see if you get any errors.
There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !
Offline
The .xaoprc only has the two numbers in it, as instructed on the conky objects page.
The... second requires you to register and obtain your partner ID and license key. These two must be written, separated by a space, into a file called .xoaprc which needs to be placed into your home directory.
conky starts with no errors.
Offline
Did you compile conky with the weather options enabled?
FYI, currently I know of no packages that have the weather features turned on by default, so that means that you will have to compile it yourself.
[edit]the command conky -v will tell you what was turned on when it was compiled.[/edit]
Last edited by Knute (2011-01-25 21:07:42)
Knute
Offline
Did you compile conky with the weather options enabled?
FYI, currently I know of no packages that have the weather features turned on by default, so that means that you will have to compile it yourself.
[edit]the command conky -v will tell you what was turned on when it was compiled.[/edit]
No, I used the arch package.
You mean $weather and $weather_forecast are standard options in conky, and arch builds conky without that capability? :?: Seems a little retarded - does it really take that many more resources to have that enabled?
Offline
Learn how to use abs and build it yourself done!
Mr Green
Offline
why not just LFS then? i mean really.
Offline
why not just LFS then? i mean really.
please do !
There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !
Offline
why not just LFS then? i mean really.
I can clearly see the correlation between building, patching, and maintaining your own toolchain and rebuilding one teeny package that would never ever break your system beyond - hold for it - some text or images displaying on your desktop.
Thank you for letting me see the light.
Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy
Offline
There's just no intelligent reason to cripple a main feature of a program arbitrarily like that. Doesn't really 'keep it simple' for the end user at all. Just adds more work, when it would be just as easy to compile it into the program to begin with, to use or not as the user chooses.
Offline
There's just no intelligent reason to cripple a main feature of a program arbitrarily like that. Doesn't really 'keep it simple' for the end user at all. Just adds more work, when it would be just as easy to compile it into the program to begin with, to use or not as the user chooses.
There IS actually a reason. There is another program out there that is quite popular with conky users called conkyforecast that provides the same information. Since that is so popular, IMHO that the option just was never turned on in conky.
Another option is to setup customizepkg to automatically turn that on, but then you would need to use one of the compiled versions rather than prebuilt.
Knute
Offline
There's just no intelligent reason to cripple a main feature of a program arbitrarily like that. Doesn't really 'keep it simple' for the end user at all. Just adds more work, when it would be just as easy to compile it into the program to begin with, to use or not as the user chooses.
Then file a feature request?
Got Leenucks? :: Arch: Power in simplicity :: Get Counted! Registered Linux User #392717 :: Blog thingy
Offline