From: Christopher Dimech <dimech@gmx.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: Help Gnu Emacs <help-gnu-emacs@gnu.org>
Subject: Re: RE: RE: RE: Viewing Info Files - Introduce Top Menu also before end of buffer
Date: Sat, 17 Oct 2020 01:51:43 +0200 [thread overview]
Message-ID: <trinity-460cc2af-e5f1-4d23-a683-e832e3cb48bb-1602892303419@3c-app-mailcom-bs14> (raw)
In-Reply-To: <f65c038c-1477-4911-842a-43ad41ed0fcd@default>
Have tried your suggestion and ended up commenting everything and
loading just your code. Scroll up gets me to the First Node I visited,
Scroll Down gets me to Last Node I visited.
> Sent: Saturday, October 17, 2020 at 1:08 AM
> 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
>
> > 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.
>
next prev parent reply other threads:[~2020-10-16 23:51 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
2020-10-16 23:51 ` Christopher Dimech [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=trinity-460cc2af-e5f1-4d23-a683-e832e3cb48bb-1602892303419@3c-app-mailcom-bs14 \
--to=dimech@gmx.com \
--cc=drew.adams@oracle.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.