4 thoughts on “Inexplicable error message du jour”

  2. Error messages I have known and loved.

    “kbuildsyscoca running…”
    “not a typewriter.”
    “Keyboard macro terminated by a command ringing the bell”
    “Spork”
    “Keyboard Error. Press <F1> to continue”
    And all modern inane backtraces from elisp or Java, as in:
    Debugger entered–Lisp error: (void-variable abc)

    (duplicate-sequence abc)
    eval((duplicate-sequence abc))
    eval-last-sexp-1(t)
    eval-last-sexp(t)
    eval-print-last-sexp()
    call-interactively(eval-print-last-sexp)
    recursive-edit()
    byte-code(“[binary goo]” [debugger-buffer debugger-args noninteractive debugger-batch-max-lines middlestart buffer-read-only pop-to-buffer debugger-mode debugger-setup-buffer count-lines 2 “…\n” message buffer-string kill-emacs debug backtrace-debug 3 t debugger-reenable “” nil recursive-edit standard-output inhibit-trace] 3)
    debug(error (void-variable *stuff*))
    eval(*stuff*)
    eval-last-sexp-1(t)
    eval-last-sexp(t)
    eval-print-last-sexp()
    call-interactively(eval-print-last-sexp)

    Reply

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.