From: Sharon Kimble <boudiccas@skimble.plus.com>
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>
Subject: Re: moving between buffers side-by-side using the keyboard
Date: Wed, 15 Feb 2017 15:24:47 +0000 [thread overview]
Message-ID: <87h93v5veo.fsf@skimble.plus.com> (raw)
In-Reply-To: <60a47df2-c660-4be7-88ad-03e0d1185053@default> (Drew Adams's message of "Wed, 15 Feb 2017 06:41:56 -0800 (PST)")
[-- Attachment #1: Type: text/plain, Size: 2454 bytes --]
Drew Adams <drew.adams@oracle.com> writes:
>> But if I do 'C-x o' now , it shows
>> (wrong-type-argument commandp outline-minor-mode-prefix) in command-execute
>>
>> So where do I go from here please?
>>
>> I don't have windmove or ace-window installed, but I'm quite prepared to
>> if it means that I get the required functionality.
>
> I'd say that _independently_ of whether you decide to use some
> other method, you might want to get the above problem straightened
> out. How you do that can help you with other, similar problems later.
>
> First, what you are asking about is switching _windows_, not
> _buffers_. Knowing the kind of thingie you are asking about can
> help you when trying to figure things out by looking at function
> and variable names, consulting the doc, etc.
>
> Second, to find whatever in your setup is taking over `C-x o' and
> stop it from doing so, recursively bisect your init file - that's
> a binary search for the culprit, and it is quite quick to do.
>
> You can do that by commenting out a region of text in your init
> file. Comment out first 1/2 of it (stopping after a full sexp
> (expression), of course, so that what is commented out can be
> evaluated without error). Then comment out half of the half that
> is problematic (so you've now narrowed it down to 1/4). Then
> from 1/4 you keep doing the same thing: 1/8, 1/16, 1/32, 1/64,
> 1/128... until you get to whatever code is causing the problem.
>
> This is blind and dumb, but it is quick and systematic, and it
> cannot fail.
>
> If the problem turns out to be in some library that you load,
> then either stop loading it (!) or repeat the same operation
> on it, to see which part of it is problematic.
>
> To comment out a region of text you can use command
> `comment-region'. (Bind it to a key, if you want.) With a
> plain prefix arg (`C-u') it UNcomments the region instead.
> (That is, it removes one level of comments, leaving nested
> comments.)
Unfortunately I don't have the time to bisect my config, I need the time
for my book that I'm writing. Maybe I'll have the time at the weekend.
I accept that I used wrong terminology for my problem, but I felt that
calling it a 'buffer' would show what I was thinking and asking about.
Thanks
Sharon.
--
A taste of linux = http://www.sharons.org.uk
TGmeds = http://www.tgmeds.org.uk
Debian 8.6, fluxbox 1.3.5-2, emacs 25.1.1.1
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
next prev parent reply other threads:[~2017-02-15 15:24 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 [this message]
2017-02-15 16:07 ` Drew Adams
2017-02-16 4:44 ` Marcin Borkowski
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=87h93v5veo.fsf@skimble.plus.com \
--to=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.