unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Christopher Dimech <dimech@gmx.com>
Cc: Help Gnu Emacs <help-gnu-emacs@gnu.org>
Subject: RE: RE: RE: Viewing Info Files - Introduce Top Menu also before end of buffer
Date: Fri, 16 Oct 2020 16:08:38 -0700 (PDT)	[thread overview]
Message-ID: <f65c038c-1477-4911-842a-43ad41ed0fcd@default> (raw)
In-Reply-To: <trinity-27870928-dd6b-40f4-8a83-da7d3a10c161-1602889127535@3c-app-mailcom-bs14>

> I will need to scrutinise my Init File, then and see what is changing
> things.

Binary search is your friend in such a case.

E.g., comment out 1/2 of your init file, then
3/4, 7/8, 15/16, ... till you find the culprit.

You can use command `comment-region' to comment
out a block of code (the region).  With `C-u'
the same command uncomments the region.

This method is blind but efficient.  It seems
to go slowly at first, then picks up quickly.

You might think you can figure things out
instead, by looking at your init file.  And
that might be true.  But it is also often a
trap/gotcha - a dumb binary search can often
be more efficient.



  reply	other threads:[~2020-10-16 23:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-16 20:37 Viewing Info Files - Introduce Top Menu also before end of buffer Christopher Dimech
2020-10-16 21:11 ` Drew Adams
2020-10-16 21:18   ` Christopher Dimech
2020-10-16 21:23   ` Christopher Dimech
2020-10-16 21:46   ` Christopher Dimech
2020-10-16 21:58     ` Drew Adams
2020-10-16 22:58       ` Christopher Dimech
2020-10-16 23:08         ` Drew Adams [this message]
2020-10-16 23:51           ` Christopher Dimech
2020-10-17 16:37             ` Drew Adams
2020-10-17 18:01               ` Christopher Dimech
2020-10-17 18:05               ` RE: RE: RE: " Christopher Dimech
2020-10-17 18:39                 ` Drew Adams
2020-10-17 19:03                   ` Christopher Dimech

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=f65c038c-1477-4911-842a-43ad41ed0fcd@default \
    --to=drew.adams@oracle.com \
    --cc=dimech@gmx.com \
    --cc=help-gnu-emacs@gnu.org \
    /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).