all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Marcin Borkowski <mbork@mbork.pl>
To: Drew Adams <drew.adams@oracle.com>
Cc: Joost Kremers <joostkremers@fastmail.fm>,
	help-emacs <help-gnu-emacs@gnu.org>,
	Filipe Silva <filipe.silva@gmail.com>,
	Sharon Kimble <boudiccas@skimble.plus.com>
Subject: Re: moving between buffers side-by-side using the keyboard
Date: Thu, 16 Feb 2017 05:44:47 +0100	[thread overview]
Message-ID: <87a89meocg.fsf@jane> (raw)
In-Reply-To: <adbd4416-b462-4d4f-8b92-26257b57dd80@default>


On 2017-02-15, at 17:07, Drew Adams <drew.adams@oracle.com> wrote:

> It _seems_ slow at first.  And yes, it's dumb.  But it's power is
> exponential - it quickly gets very quick. ;-)  Think of the old
> story of doubling the grains of rice on a chessboard.  Yes, at
> first it seems like very little rice is involved...
>
> The slowest part of this particular binary search is to restart
> Emacs each time, after you've commented out part of your init
> file.  But the more that is commented out, the closer the startup
> becomes to a virgin startup (i.e., `emacs -Q': no init file).

Also, see https://github.com/Malabarba/elisp-bug-hunter for a way to
automate the dumb part.

Best,

-- 
Marcin Borkowski



  reply	other threads:[~2017-02-16  4:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-15 12:08 moving between buffers side-by-side using the keyboard Sharon Kimble
2017-02-15 12:16 ` Filipe Silva
2017-02-15 12:25   ` Sharon Kimble
2017-02-15 12:34     ` tomas
2017-02-15 12:40     ` Joost Kremers
2017-02-15 13:52       ` Sharon Kimble
2017-02-15 14:04         ` Kaushal Modi
2017-02-15 14:41         ` Drew Adams
2017-02-15 15:24           ` Sharon Kimble
2017-02-15 16:07             ` Drew Adams
2017-02-16  4:44               ` Marcin Borkowski [this message]
2017-02-15 19:47         ` Filipe Silva
2017-02-15 12:29 ` Joost Kremers
2017-02-15 19:11   ` Eric Abrahamsen

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=87a89meocg.fsf@jane \
    --to=mbork@mbork.pl \
    --cc=boudiccas@skimble.plus.com \
    --cc=drew.adams@oracle.com \
    --cc=filipe.silva@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=joostkremers@fastmail.fm \
    /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.