unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Thorsten Jolitz'" <tjolitz@googlemail.com>, <help-gnu-emacs@gnu.org>
Subject: RE: Invalid tags table
Date: Tue, 20 Nov 2012 14:25:30 -0800	[thread overview]
Message-ID: <D8ABDC1D13E843C39CB782FD1E111A9D@us.oracle.com> (raw)
In-Reply-To: <87obisncy8.fsf@googlemail.com>

> > 2. `M-x debug-on-entry visit-tags-table-buffer'
> 
> I tried this first, since I have quite a lot of customisation files.
> 
> That was a great tip, I wasn't even aware of this option, and 
> it helped me to figure out...  Now it works. Thanks a lot.

You're welcome, and I'm glad it was so easy.

In general, however, I recommend the other option I mentioned: bisect your init
file - regardless of how big your init file is or how much it loads.

Binary search is your friend.  The difference between handling an init file that
is 32 times bigger (and that's a lot) is only 5 more bisections.  It really
doesn't take long.

We humans tend to entertain multiple possibilities when troubleshooting ('cause
we think we're so smart, I guess, and we like to play detective).  And
especially when you have a big init file, that means trying to juggle lots of
possibilities at the same time.

Sticking blindly to a binary search means not even considering half, then 3/4,
then 7/8,... of those possibilities.  Not even considering.  Not even thinking.
Pure thoughtless magic.

Yeah, sometimes it can help to combine a little thought with blind search.  But
sometimes that can lead you astray as well.




  reply	other threads:[~2012-11-20 22:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-20 20:47 Invalid tags table Thorsten Jolitz
2012-11-20 21:39 ` Drew Adams
2012-11-20 22:09   ` Thorsten Jolitz
2012-11-20 22:25     ` Drew Adams [this message]
2012-11-20 23:01       ` Thorsten Jolitz
2012-11-22 16:50     ` Stefan Monnier
2012-11-23 12:46       ` Thorsten Jolitz

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=D8ABDC1D13E843C39CB782FD1E111A9D@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=tjolitz@googlemail.com \
    /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.
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).