emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Niels Giesen <nielsgiesen@ibbu.nl>
To: emacs-orgmode@gnu.org
Subject: Re: Re: extremely weird "bad sexp" errors with org-google-weather [was: extremely weird "bad sexp" errors]
Date: Wed, 03 Nov 2010 12:35:37 +0100	[thread overview]
Message-ID: <4CD14909.6040802@ibbu.nl> (raw)
In-Reply-To: <20100916084207.GB9795@taupan.ath.cx>

Friedrich Delgado wrote:
> Oh... and I just tried to set the language back to "DE" and the
> problem disappeared.
>
> It can only guess that there might have been some problem going on
> behind the curtain (e.g. on the google servers?), which has now been
> resolved.
>
> I'd appreciate if Org/org-google-weather could handle such conditions
> more gracefully, and/or some instructions how to provide debug
> information for those cases.
>
> Friedrich Delgado Friedrichs schrieb:
>   
>> It just occured to me, that I could have include org-google-weather in
>> the subject.
>>
>> *bump*
>>
>> Friedrich Delgado Friedrichs schrieb:
>>     
>>> For some strange reason, as of today, the combination
>>>
>>> %%(org-google-weather "Hamburg" "DE")
>>>
>>> seems to be deeply offending, as I get a "bad sexp" error for it.
>>>       
>> [...]
>>
>>     
> ---Zitatende---
>
>   
Hi Friedrich,

I ran into the same problem when I had no network. My work-around was to
put something like this in my org-file:

%%(condition-case nil (org-google-weather "Tokyo" "jp") (error
"connection failed"))

Of course, having this error intercepted in org-google-weather or in the
general handling by org-mode would be preferable.

  reply	other threads:[~2010-11-03 11:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-15 11:30 extremely weird "bad sexp" errors Friedrich Delgado
2010-09-16  8:39 ` extremely weird "bad sexp" errors with org-google-weather [was: extremely weird "bad sexp" errors] Friedrich Delgado
2010-09-16  8:42   ` Friedrich Delgado
2010-11-03 11:35     ` Niels Giesen [this message]
2010-11-04 10:42       ` Julien Danjou

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4CD14909.6040802@ibbu.nl \
    --to=nielsgiesen@ibbu.nl \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).