From: "R. Diez" <rdiezmail-emacs@yahoo.de>
To: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: Separate area at the top for a serious tab bar
Date: Wed, 20 Jun 2018 07:06:59 +0000 (UTC) [thread overview]
Message-ID: <376678535.4221832.1529478419186@mail.yahoo.com> (raw)
In-Reply-To: 376678535.4221832.1529478419186.ref@mail.yahoo.com
Hi all:
A tab bar is a very important usability element. Virtually every other editor has it. For many people, including myself, visual, positional clues makes life much easier.
I just do not want to live without one. Therefore, I am a long-time user of tabbar.el . I have installed several little enhancements and hacked together some dodgy Lisp code over the years. It is a problematic solution that still frustrates me on a regular basis.
I am no Lisp expert, but I am sure that many smarter people would quickly write a better tab bar package if given a good chance. My bet is that something is holding them back.
The reason may be the lack of a separate area for a tab bar. If I remember correctly, the current tabbar.el steals an area designed for displaying a ruler. This stealing causes problems, because the handling of that area is not flexible enough and yields trouble here and there. It is not a good basis to build upon.
I have just read the following in the Emacs 26.1 change log:
"Emacs now supports optional display of line numbers in the buffer. This is similar to what 'linum-mode' provides, but much faster and doesn't usurp the display margin for the line numbers."
I guess that there was a similar problem there: the old code had to usurp the margin for another purpose.
This is my plea to the Emacs gurus: Implement a suitable area at the top of windows/frames/whatever to pave the way for a serious tab bar implementation.
Best regards,
rdiez
next parent reply other threads:[~2018-06-20 7:06 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 ` R. Diez [this message]
2018-06-20 12:16 ` Separate area at the top for a serious tab bar 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
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=376678535.4221832.1529478419186@mail.yahoo.com \
--to=rdiezmail-emacs@yahoo.de \
--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).