From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Feeling lost without tabs
Date: Sun, 20 Jul 2014 20:30:42 +0300 [thread overview]
Message-ID: <83lhro3pkt.fsf@gnu.org> (raw)
In-Reply-To: <CAP_d_8X4zvsGetRjJTzQ7sZs4LohrQFZokan28jwDZ2fy1+pxA@mail.gmail.com>
> Date: Sun, 20 Jul 2014 23:48:52 +0700
> From: Yuri Khan <yuri.v.khan@gmail.com>
> Cc: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
>
> On Sun, Jul 20, 2014 at 1:09 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>
> >> To switch buffers efficiently, I need a visual representation of their
> >> relative order
> >
> > AFAIK, each frame orders the buffers separately, so I don't see why
> > you would have a problem here.
>
> The problem here is that I need to see the list before I start pressing keys.
Only if there are a lot of them. Keep your frames project-specific,
and there won't be too many of them you'll need to remember. E.g.,
with programming projects, I normally switch to a buffer via some
tags-related command, so I don't even need to remember the buffer
name. And if I need to switch to a buffer visiting a specific source
file, then I know that buffer's name by definition. Etc. etc.
> The workflow with C-x b is: fingers press C-x b, eyes see the default
> next buffer, brain tests if that’s the right one.
A frame can display more than a single buffer, so you don't need to
switch buffers so frequently. And when you do switch, even if you do
that with "C-x b", chances are it's the buffer displayed previously in
the same window, so no such complex procedure is needed. I usually
just press "C-x b RET" without even looking.
> The cognitive load (roughly, the number of eyes-brain-fingers
> roundtrips) is much worse in the second case as the operations cannot
> be done concurrently.
Granted, you are happy with your workflow, as much as I'm happy with
mine (for many years now). You asked me how do I manage my buffers,
and I told you. We don't need to prove each other that the other's
workflow is worse.
next prev parent reply other threads:[~2014-07-20 17:30 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-20 1:47 Feeling lost without tabs Sampath Weerasinghe
2014-07-20 4:08 ` Yuri Khan
2014-07-20 4:27 ` Eli Zaretskii
2014-07-20 5:12 ` Yuri Khan
2014-07-20 6:09 ` Eli Zaretskii
2014-07-20 16:48 ` Yuri Khan
2014-07-20 17:30 ` Eli Zaretskii [this message]
2014-07-21 14:15 ` Stefan Monnier
2014-07-22 3:51 ` Yuri Khan
[not found] ` <mailman.5771.1405874938.1147.help-gnu-emacs@gnu.org>
2014-07-20 18:40 ` Emanuel Berg
2014-07-21 3:56 ` Yuri Khan
2014-07-20 7:19 ` Bob Proulx
[not found] ` <mailman.5741.1405840784.1147.help-gnu-emacs@gnu.org>
2014-07-20 18:36 ` Emanuel Berg
2014-07-20 23:48 ` Dan Espen
2014-07-21 0:29 ` Emanuel Berg
2014-07-21 1:08 ` Charles Philip Chan
2014-07-21 2:25 ` Dan Espen
2014-07-21 16:25 ` Bob Proulx
2014-07-22 0:57 ` Robert Thorpe
[not found] ` <mailman.5823.1405959942.1147.help-gnu-emacs@gnu.org>
2014-07-21 18:04 ` Dan Espen
2014-07-21 21:05 ` Bob Proulx
[not found] ` <mailman.5831.1405976742.1147.help-gnu-emacs@gnu.org>
2014-07-21 21:22 ` Dan Espen
2014-07-21 21:54 ` Emanuel Berg
2014-07-21 23:57 ` Robert Thorpe
2014-07-22 2:33 ` Dan Espen
2014-07-22 21:28 ` Emanuel Berg
2014-07-21 21:47 ` Emanuel Berg
2014-07-21 21:43 ` Emanuel Berg
2014-07-21 21:40 ` have new Gnus message not always fullscreened (was: [gnu.emacs.help] Re: Feeling lost without tabs) Emanuel Berg
2014-07-20 5:22 ` Feeling lost without tabs Tak Kunihiro
[not found] ` <mailman.5729.1405830475.1147.help-gnu-emacs@gnu.org>
2014-07-22 15:14 ` Javier
2014-07-22 15:32 ` Ken Goldman
2014-07-22 21:01 ` Emanuel Berg
2014-07-23 0:57 ` Javier
2014-07-23 2:21 ` Emanuel Berg
[not found] ` <mailman.5871.1406043177.1147.help-gnu-emacs@gnu.org>
2014-07-22 21:03 ` Emanuel Berg
[not found] ` <<lqlv3t$hog$1@speranza.aioe.org>
2014-07-22 17:03 ` Drew Adams
2014-07-20 6:25 ` Filipp Gunbin
2014-07-20 9:20 ` Kevin Le Gouguec
2014-07-20 17:36 ` Drew Adams
2014-07-20 18:02 ` Robert Thorpe
2014-08-16 21:13 ` Marcin Borkowski
[not found] <mailman.5726.1405828965.1147.help-gnu-emacs@gnu.org>
2014-07-20 14:19 ` Dan Espen
2014-07-20 18:11 ` Bob Proulx
2014-07-20 18:34 ` Emanuel Berg
[not found] ` <mailman.5777.1405879906.1147.help-gnu-emacs@gnu.org>
2014-07-20 21:44 ` Emanuel Berg
2014-07-21 17:02 ` Bob Proulx
2014-07-20 23:52 ` Dan Espen
2014-07-21 22:54 ` Emanuel Berg
2014-07-21 23:33 ` Bob Proulx
2014-07-22 2:44 ` Dan Espen
2014-07-22 21:23 ` Emanuel Berg
[not found] ` <mailman.5833.1405985639.1147.help-gnu-emacs@gnu.org>
2014-07-22 22:02 ` Emanuel Berg
2014-07-20 18:28 ` Emanuel Berg
2015-11-03 14:07 ` swe20144
2015-11-03 14:21 ` Dan Espen
2015-11-03 15:22 ` Yuri Khan
2015-11-03 15:46 ` Dirk-Jan C. Binnema
2015-11-03 17:31 ` Michael Heerdegen
2015-11-03 17:47 ` Charles Philip Chan
2015-11-03 21:24 ` Michael Heerdegen
2015-11-03 15:37 ` Filipp Gunbin
2015-11-03 15:53 ` Aziz Yemloul
2015-11-03 15:56 ` Charles Philip Chan
2015-11-03 20:07 ` Bob Proulx
2015-11-03 23:48 ` Kendall Shaw
[not found] <mailman.5835.1405987077.1147.help-gnu-emacs@gnu.org>
2014-07-22 21:18 ` Emanuel Berg
2014-07-22 22:32 ` Robert Thorpe
[not found] <mailman.5882.1406068755.1147.help-gnu-emacs@gnu.org>
2014-07-22 23:57 ` Emanuel Berg
2014-07-23 1:25 ` Robert Thorpe
[not found] <mailman.5886.1406078772.1147.help-gnu-emacs@gnu.org>
2014-07-23 2:29 ` Emanuel Berg
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=83lhro3pkt.fsf@gnu.org \
--to=eliz@gnu.org \
--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).