all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Separate area at the top for a serious tab bar
Date: Mon, 25 Jun 2018 17:49:06 +0300	[thread overview]
Message-ID: <83po0esyzh.fsf@gnu.org> (raw)
In-Reply-To: <406844585.2241039.1529922018350@mail.yahoo.com> (rdiezmail-emacs@yahoo.de)

> Date: Mon, 25 Jun 2018 10:20:18 +0000 (UTC)
> From: "R. Diez" <rdiezmail-emacs@yahoo.de>
> Cc: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>,
> 	Jay Kamat <jaygkamat@gmail.com>
> 
> > Though I understand the "positional orientation" idea.
> 
> This is a personal preference. Many people thrive in chaos. Other must have a tidy desktop. There is nothing wrong per se with each way.
> 
> A tabbar does not preclude other buffer switching methods. I often have many buffers open. But I tend to keep the "local context" (the tabs that are visible right now) sorted (.h left from .cpp and so on).
> 
> There is a tabbar in Firefox. There is one in most desktop environments (Windows, Xfce, KDE...). There will always be people and scenarios where a tabbar is the right approach, even in Emacs.
> 
> I would not underestimate this kind of usability matter. It may well be one of the biggest factors driving people away from Emacs. It could even be a necessary evil until most people learn to do away with the tabbar. Humans are just like that.

FWIW, I consider tabbar to be in the same class as line numbers: while
not really an Emacs'y thing, at least not for us veteran curmudgeons,
they are very popular in some quarters, and if we want to make those
people happy, we should have them.

I also think this kind of feature needs support in the display engine;
anything else will always look like a hacky band-aid.  Volunteers are
welcome to work on that.



  reply	other threads:[~2018-06-25 14:49 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
2018-06-25  9:28       ` Marcin Borkowski
2018-06-25 10:20         ` R. Diez
2018-06-25 14:49           ` Eli Zaretskii [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83po0esyzh.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.
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.