Print result of `db/ntp-to-time' when called interactively

Otherwise no result is displayed.
This commit is contained in:
Daniel - 2020-06-27 12:27:42 +02:00
parent 5b6dcfe8d2
commit 72768b659f
No known key found for this signature in database
GPG Key ID: 1C7071A75BB72D64
1 changed files with 18 additions and 15 deletions

View File

@ -201,21 +201,24 @@ FORMAT-STRING defaults to some ISO 8601-like format."
'raw)
;; we explicitly call `calcFunc-unixtime'
;; here to set the time zone to UTC
0)))
(format (or format-string
"%04d-%02d-%02dT%02d:%02d:%012.9fZ")
(calcFunc-year unix-time)
(calcFunc-month unix-time)
(calcFunc-day unix-time)
(calcFunc-hour unix-time)
(calcFunc-minute unix-time)
;; `seconds' will be a floating point number, and we need to format
;; it with a precision that is high enough; apparently, we also need
;; to truncate the number of seconds to nine digits, at least that
;; is what has been done in the test example we use in the
;; corresponding regression test …
(string-to-number
(calc-eval "trunc(second($), 9)" 'num unix-time)))))
0))
(time-string (format (or format-string
"%04d-%02d-%02dT%02d:%02d:%012.9fZ")
(calcFunc-year unix-time)
(calcFunc-month unix-time)
(calcFunc-day unix-time)
(calcFunc-hour unix-time)
(calcFunc-minute unix-time)
;; `seconds' will be a floating point number, and we need to format
;; it with a precision that is high enough; apparently, we also need
;; to truncate the number of seconds to nine digits, at least that
;; is what has been done in the test example we use in the
;; corresponding regression test …
(string-to-number
(calc-eval "trunc(second($), 9)" 'num unix-time)))))
(if (called-interactively-p 'interactive)
(message time-string)
time-string)))
(defun conditionally-enable-lispy ()
"Enable lispy-mode when in `eval-expression or in