Rc error output written to current buffer

[ambihelical]

The following happens everytime I perform the following actions:

1) create a new .h or .cpp buffer 2) add some text 3) wait a few seconds Note: at no point is the file saved on disk yet.

I get the following text added to the buffer (actual file path changed here to ==path to file==):

Can't open [==path to file==] for reading
unexpected option -- '--no-color'
Try 'rc --help' for more information.

I have rtags-set-periodic-reparse-timeout set to 2, and it seems to happen after about that interval.

Rtags built from source at commit c93f47f9f67878352c33d31243b5e285623554c7 rc says it is version 2.4.100 rtags emacs package version is 20160825.1435 from melpa

Here is my rtags config minus keybindings:

(use-package rtags
  :commands ( rtags-location-stack-back rtags-location-stack-forward )
  :init
  (progn
    (setq rtags-autostart-diagnostics t
          rtags-use-helm t
          rtags-tooltips-enabled nil
          rtags-display-current-error-as-message nil
          rtags-process-flags "--config ~/.config/rtags/config"
          rtags-completions-enabled t)
    (add-hook 'c-mode-common-hook #'rtags-start-process-unless-running)
    (add-hook 'c-mode-common-hook #'me:flycheck-rtags-setup)
    (add-hook 'company-mode-hook  #'me:company-rtags-setup))
  :config
  (progn
    (rtags-diagnostics)
    (rtags-set-periodic-reparse-timeout 2)
    (rtags-enable-standard-keybindings))
  :diminish rtags-mode
 )

[Andersbakken]

Weird. I can't quite seem to reproduce it but I see what's going on and I think it should be fixed now.

Can you check after my last two fixes?

Anders

On Thu, Sep 1, 2016 at 2:20 PM, ambihelical notifications@github.com wrote:

The following happens everytime I perform the following actions:

1) create a new .h or .cpp buffer 2) add some text 3) wait a few seconds Note: at no point is the file saved on disk yet.

I get the following text added to the buffer (actual file path changed here to ==path to file==):

I have rtags-set-periodic-reparse-timeout set to 2, and it seems to happen after about that interval.

Can't open [==path to file==] for reading unexpected option -- '--no-color' Try 'rc --help' for more information.

Rtags built from source at commit c93f47f https://github.com/Andersbakken/rtags/commit/c93f47f9f67878352c33d31243b5e285623554c7 rc says it is version 2.4.100 rtags emacs package version is 20160825.1435 from melpa

Here is my rtags config minus keybindings:

(use-package rtags :commands ( rtags-location-stack-back rtags-location-stack-forward ) :init (progn (setq rtags-autostart-diagnostics t rtags-use-helm t rtags-tooltips-enabled nil rtags-display-current-error-as-message nil rtags-process-flags "--config ~/.config/rtags/config" rtags-completions-enabled t) (add-hook 'c-mode-common-hook #'rtags-start-process-unless-running) (add-hook 'c-mode-common-hook #'me:flycheck-rtags-setup) (add-hook 'company-mode-hook #'me:company-rtags-setup)) :config (progn (rtags-diagnostics) (rtags-set-periodic-reparse-timeout 2) (rtags-enable-standard-keybindings)) :diminish rtags-mode )

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/Andersbakken/rtags/issues/779, or mute the thread https://github.com/notifications/unsubscribe-auth/AAEdSptBSgeLWpOisywqU6Tke7eZvDtrks5ql0GhgaJpZM4JzJMk .

[ambihelical]

I don't get the text in the buffer anymore. But there is an error message now:

Error running timerrtags-reparse-file-if-needed': (wrong-type-argument stringp nil)`

[Andersbakken]

Hm. I don't seem to get that one. Can you see if you can get a stack trace from it or maybe try to catch it in edebug?

[Andersbakken]

Strike that. I got it now. The last fix should take care of that I think.

[ambihelical]

After updating the melpa package, the error seems to be gone.

[Andersbakken]

Glad to hear. Let me know if any new problems show up.

On Sun, Sep 4, 2016 at 10:31 PM, ambihelical notifications@github.com wrote:

After updating the melpa package, the error seems to be gone.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/Andersbakken/rtags/issues/779#issuecomment-244661822, or mute the thread https://github.com/notifications/unsubscribe-auth/AAEdSrXAb3IJ3ic_ETe4WIs-_JJu9VcCks5qm6lFgaJpZM4JzJMk .