From: Ulf Jasper <ulf.jasper@web.de>
To: Mark Oteiza <mvoteiza@udel.edu>
Cc: 19401@debbugs.gnu.org
Subject: bug#19401: 25.0.50; metar.el (metar-convert-temperature) wrong type argument stringp nil
Date: Thu, 18 Dec 2014 18:00:15 +0100 [thread overview]
Message-ID: <87a92k28rk.fsf@web.de> (raw)
In-Reply-To: <87egrxqaeb.fsf@udel.edu> (Mark Oteiza's message of "Thu, 18 Dec 2014 09:51:08 -0500")
Mark Oteiza <mvoteiza@udel.edu> writes:
> The same; emacs from master and metar 0.1 from ELPA. It works at this
> time when CODES in (metar-decode) is:
>
> "KPHL 181354Z 29012KT 10SM BKN041 03/M07 A3010 RMK AO2 SLP190 T00281067"
>
> but for some reason the following from yesterday was bad input for metar.el:
>
> "KPHL 172054Z 28015G23KT 10SM BKN046 10/M01 A2993 RMK AO2 PK WND 28029/2044 SLP135 T01001006 53013"
It appears that the temperature value -1 °C ("M01") is causing the error
(metar-convert-temperature "M07") => (-7 . degC)
(metar-convert-temperature "M01") => error (wrong-type-argument stringp nil)
I suspect that this is the result of `math-mul-symb-fancy' (which
metar.el calls via calc-units) treating "-1" in a special way
(math-mul-symb-fancy -7 '(var degC var-degC)) => (* -7 (var degC var-degC))
(math-mul-symb-fancy -1 '(var degC var-degC)) => (neg (var degC var-degC))
I have never looked at the calc library before and feel unable to cope
with it. Hopefully someone else can stand in.
ulf
next prev parent reply other threads:[~2014-12-18 17:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-17 21:15 bug#19401: 25.0.50; metar.el (metar-convert-temperature) wrong type argument stringp nil Mark Oteiza
2014-12-18 14:29 ` Ulf Jasper
2014-12-18 14:51 ` Mark Oteiza
2014-12-18 17:00 ` Ulf Jasper [this message]
2015-01-13 14:34 ` Wolfgang Jenkner
2015-01-13 17:57 ` Ulf Jasper
2015-01-13 20:11 ` Wolfgang Jenkner
2016-02-19 18:04 ` Wolfgang Jenkner
2016-02-26 15:50 ` Wolfgang Jenkner
2016-02-29 19:28 ` Wolfgang Jenkner
2015-01-14 1:47 ` Wolfgang Jenkner
2015-12-29 20:26 ` Mark Oteiza
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a92k28rk.fsf@web.de \
--to=ulf.jasper@web.de \
--cc=19401@debbugs.gnu.org \
--cc=mvoteiza@udel.edu \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.