Lots of "Error running timer: (wrong-type-argument syntax-table-p t)" errors when run with company-mode

[vkazanov]

Lots of "Error running timer: (wrong-type-argument syntax-table-p t)" errors when run with company-mode

[tigersoldier]

Looks like it's unrelated to JavaComp. This error is thrown from sp-ui-sideline calling thing-at-point.

Please make sure you don't have any package overriding thing-at-point. Your version in the stack trace is different from mine. Here is what this function looks like from my Emacs 26.1:

;;;###autoload
(defun thing-at-point (thing &optional no-properties)
  "Return the THING at point.
THING should be a symbol specifying a type of syntactic entity.
Possibilities include `symbol', `list', `sexp', `defun',
`filename', `url', `email', `word', `sentence', `whitespace',
`line', `number', and `page'.

When the optional argument NO-PROPERTIES is non-nil,
strip text properties from the return value.

See the file `thingatpt.el' for documentation on how to define
a symbol as a valid THING."
  (let ((text
         (if (get thing 'thing-at-point)
             (funcall (get thing 'thing-at-point))
           (let ((bounds (bounds-of-thing-at-point thing)))
             (when bounds
               (buffer-substring (car bounds) (cdr bounds)))))))
    (when (and text no-properties (sequencep text))
      (set-text-properties 0 (length text) nil text))
    text))

[vkazanov]

Thanks you! I'll check and either close the ticket if it's not related to JavaComp or expand on this one if it turns out something is wrong.

BTW. There's extra quote in the README use-package setup example ((require 'lsp-javacomp'), notice the tailing quote).

[vkazanov]

Thanks you so much! I have a really big config, which made through multiple emacs versions. It turns out I had a tweaked thing-at-point implementation which overrided the bundled one.

Now things really do work as intended!