all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Kamphausen <skampi@gmx.net>
To: help-gnu-emacs@gnu.org
Subject: Re: moving around multiple buffers
Date: Fri, 21 Aug 2009 18:07:31 +0200	[thread overview]
Message-ID: <87iqghw3p8.fsf@usenet.my.skamphausen.de> (raw)
In-Reply-To: 4aece418-c7b5-49cc-8270-625d1b277880@d9g2000prh.googlegroups.com

Hi,

Xah Lee <xa...@gmail.com> writes:

> On Aug 20, 9:08 am, "Farhan Ahmed" <far...@alienfluid.com> wrote:
>>
>> FWIW, I've mapped shift+TAB to 'next buffer and C+shift+TAB to 'previous
>> buffer and now I only use one window to edit code. Takes a little getting
>> used to, but it works.
>
> using Tab is probably worst, because every mode vie for that key.
>

[...]

I've been using Ctrl-TAB for (lambda () (interactive (other-window 1)))
for years and I rarely clash with modes.  Similar I've been using
Shift-TAB for comint-dynamic-complete for years without many clashes.
Maybe the occasional incompatibility here and there (mainly org) but I'm
happy with that.

Whenever I need to work with one of those
shift-movement-selects-software wannabes I feel slightly disgusted.  

>
> not recommended to pile on such a key.

As for recommendations... Just for the record: I rebind C-v and C-b to
mean someting like C-x and C-c respectively (global and mode-local
bindings) but for my personal use.  For years.  No problems with almost
all the modes (and I use lots of different major modes).

> Also, i noticed, tab key is not actually a good key.

Now, what may a "good key" be?  Easily reachable? Big? 

> Need to take care of your pinkies.

No problems here after some 15 years of Emacs/XEmacs usage.


So, Ahmed, just stick with your bindings and be happy with it.  :-)


Cheers,
Stefan
-- 
Stefan Kamphausen --- http://www.skamphausen.de
a blessed +42 regexp of confusion (weapon in hand)
You hit. The format string crumbles and turns to dust.


  reply	other threads:[~2009-08-21 16:07 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-20  8:58 moving around multiple buffers Tamas K Papp
2009-08-20  9:21 ` Joost Kremers
2009-08-20  9:56   ` Lennart Borgman
     [not found]   ` <mailman.4882.1250762244.2239.help-gnu-emacs@gnu.org>
2009-08-20 10:10     ` Joost Kremers
2009-08-20 10:23       ` Tamas K Papp
2009-08-20 10:43         ` Joost Kremers
2009-08-20 14:07           ` Stefan Kamphausen
2009-08-20 22:29             ` Joost Kremers
2009-08-20 16:08         ` Farhan Ahmed
     [not found]         ` <mailman.5013.1250859765.2239.help-gnu-emacs@gnu.org>
2009-08-21 15:03           ` Xah Lee
2009-08-21 16:07             ` Stefan Kamphausen [this message]
2009-08-20 10:11 ` Xah Lee
2009-08-21  5:50   ` Torben Knudsen
2009-08-21  7:12     ` Xah Lee
2009-08-21 16:56       ` Benjamin Andresen
2009-08-22  2:35         ` Xah Lee
2009-08-20 15:17 ` Drew Adams
2009-08-20 16:45 ` A.Politz
2009-08-20 17:01 ` Nikolaj Schumacher
2009-08-22  1:33 ` Kevin Rodgers

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=87iqghw3p8.fsf@usenet.my.skamphausen.de \
    --to=skampi@gmx.net \
    --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.