Skip to content

function alert-after-compilation-finish seems conflict with ggtags #388

Closed
@kongfy

Description

I'm now using ggtags to navigate in C/C++ code base, but I found when I jump to some tag in the same file, ggtags give me the error blow:

error in process sentinel: if: Selecting deleted buffer
error in process sentinel: Selecting deleted buffer

With toggle-debug-on-error, it produce something like:

Debugger entered--Lisp error: (error "Selecting deleted buffer")
  alert("Compilation finished\n" :buffer #<killed buffer> :category compilation)
  (if (catch (quote is-visible) (walk-windows (function (lambda (w) (if (eq (window-buffer w) buf) (progn (throw ... t)))))) nil) nil (alert (concat "Compilation " result) :buff$
  sanityinc/alert-after-compilation-finish(#<killed buffer> "finished\n")
  run-hook-with-args(sanityinc/alert-after-compilation-finish #<killed buffer> "finished\n")
  compilation-handle-exit(exit 0 "finished\n")
  compilation-sentinel(#<process global> "finished\n")

Which sounds like a conflict between your function alert-after-compilation-finish and ggtags to me, Is it possible to fix it ?

Now I just comment out the hook to this function and everything works fine.

Thank you!

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions