From: Drew Adams <drew.adams@oracle.com>
To: bvraghav@iitk.ac.in
Cc: 23987@debbugs.gnu.org
Subject: bug#23987: 24.5; Icy with Ggtags Problem
Date: Fri, 22 Jul 2016 07:01:35 -0700 (PDT) [thread overview]
Message-ID: <6bcabe89-33a6-4259-bb42-28f59497c255@default> (raw)
In-Reply-To: <87a8h96fnt.fsf@ram.bvr.dp.lan>
> > (defun compilation-auto-jump (buffer pos)
> > (when (buffer-live-p buffer) ; <=======
...
> This function did not help the use case...
Hm. I thought that the error reported was that some code tried
to use a buffer that was dead (killed). And that the code
that raised the error was invoked from `compilation-auto-jump'
(which is invoked from an idle timer).
Error running timer `compilation-auto-jump': (error "Selecting
deleted buffer")
Are you getting the _same_ error even after changing the code
as indicated? If so then I might not understand what's going
on.
I'm guessing that the new definition of `compilation-auto-jump'
was not getting invoked. The old definition was still getting
invoked, as it was built into the original timer (which is not
assigned to any variable, so you cannot easily cancel it).
To test with the suggested code, try something like this:
Make a _copy_ of compile.el, and move the original and any
byte-compiled version (compile.elc) somewhere that is not
in your `load-path' (so you can move them back again after
testing, if need be).
Then replace the original definition in the copy of file
compile.el that _is_ in your `load-path' with the new
definition. Don't bother to compile the file. Then test
in a new Emacs session or at least a new compilation buffer.
The point is to be sure to pick up the new version.
You can also add a call to `message' to the new version,
to let you know that it is getting called (the messages
get logged in buffer `*Messages*'). E.g.:
(defun compilation-auto-jump (buffer pos)
(message "CAJ, BUF: %S, POS: %S" buffer pos) <=======
(when (buffer-live-p buffer)
...))
next prev parent reply other threads:[~2016-07-22 14:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-14 17:27 bug#23987: 24.5; Icy with Ggtags Problem B.V. Raghav
2016-07-20 7:42 ` Glenn Morris
2016-07-21 16:44 ` Drew Adams
2016-07-22 12:06 ` B.V. Raghav
2016-07-22 14:01 ` Drew Adams [this message]
2016-07-22 14:51 ` B.V. Raghav
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6bcabe89-33a6-4259-bb42-28f59497c255@default \
--to=drew.adams@oracle.com \
--cc=23987@debbugs.gnu.org \
--cc=bvraghav@iitk.ac.in \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).