From: "R. Diez" <rdiezmail-emacs@yahoo.de>
To: Jay Kamat <jaygkamat@gmail.com>
Cc: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: Re: Separate area at the top for a serious tab bar
Date: Mon, 25 Jun 2018 06:24:23 +0000 (UTC) [thread overview]
Message-ID: <16868055.1966258.1529907863571@mail.yahoo.com> (raw)
In-Reply-To: <87bmbz8o9f.fsf@gmail.com>
> [...]
> I would highly reccomend giving the buffer
> based workflow a try, however. Once I tried seriously
> dropping tabs, I can't imagine going back to a tabbed workflow.
> [...]
You are not the first with that kind of suggestion.
I still have not seen what makes that "buffer based workflow" better. Sometimes I do use ibuffer to clean buffers up, or to find some buffer I 'lost', but tabs give you a kind of positional orientation that is hard to beat.
I do not switch buffers with the mouse. I use Ctrl+Up and Ctrl+Down to navigate the tab bar. With Ctrl+Shift+Up and Ctrl+Shift+Down I can reorder the tabs with the keyboard. I do this all the time, so that the buffers I am working on at the moment are near each other.
By the way, those are exactly the keys that Firefox uses for its tabbar.
For example, when working on C/C++ code, I place the .h and .cpp files next to each other, the .h file to the left, and the .cpp file to the right. I know I can open the other one with 'other', but that is not reliable, for example, if the .h file is not next to the .cpp file, but in some other include/ directory. If I am moving code, I place the old source file to the left, and the new one next to it, to the right, so switching is immediate. I can open a script and have next to it a shell to test it out. And many such pairs happily coexist in the same, long tabbar.
Best regards,
rdiez
next prev parent reply other threads:[~2018-06-25 6:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <376678535.4221832.1529478419186.ref@mail.yahoo.com>
2018-06-20 7:06 ` Separate area at the top for a serious tab bar R. Diez
2018-06-20 12:16 ` martin rudalics
2018-06-20 12:55 ` Van L
2018-06-27 8:44 ` R. Diez
2018-06-27 9:17 ` martin rudalics
2018-06-20 14:09 ` Drew Adams
2018-06-22 5:51 ` Van L
2018-06-20 16:32 ` Teemu Likonen
2018-06-24 18:31 ` Grant Rettke
2018-06-25 4:48 ` Jay Kamat
2018-06-25 6:24 ` R. Diez [this message]
2018-06-25 9:28 ` Marcin Borkowski
2018-06-25 10:20 ` R. Diez
2018-06-25 14:49 ` Eli Zaretskii
2018-06-25 14:56 ` Jean-Christophe Helary
2018-06-25 15:25 ` Eli Zaretskii
2018-06-26 18:55 ` Bob Proulx
2018-06-26 19:01 ` 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
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=16868055.1966258.1529907863571@mail.yahoo.com \
--to=rdiezmail-emacs@yahoo.de \
--cc=help-gnu-emacs@gnu.org \
--cc=jaygkamat@gmail.com \
/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).