From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: 37592@debbugs.gnu.org
Subject: bug#37592: Using tabs in EWW
Date: Fri, 04 Oct 2019 10:34:32 +0300 [thread overview]
Message-ID: <83zhih55h3.fsf@gnu.org> (raw)
In-Reply-To: <87pnjdh1up.fsf@mail.linkov.net> (message from Juri Linkov on Fri, 04 Oct 2019 01:39:42 +0300)
> From: Juri Linkov <juri@linkov.net>
> Cc: 37592@debbugs.gnu.org
> Date: Fri, 04 Oct 2019 01:39:42 +0300
>
> > Instead of adding another defcustom, how about doing this by default
> > if tab-bar-mode is enabled?
>
> I guess the users still need to decide whether they want to open
> new tabs in the tab-bar (when eww-browse-url-new-window-is-tab is non-nil),
> or new tabs in the tab-line (when eww-browse-url-new-window-is-tab is nil)
> that just creates a new buffer displayed in the window-local tab-line -
> this is the current behavior.
>
> Another use case is that when tab-bar-mode is not yet enabled,
> users migth prefer that clicking on a link with a Ctrl key
> could enable the tab-bar and open a new tab in automatically
> enabled tab-bar.
It seems to me that there are sensible defaults in each of these
situations, and we could use those defaults unconditionally until
users complained.
Adding too many user options has a downside as well, you know.
Just one opinion.
next prev parent reply other threads:[~2019-10-04 7:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-02 20:31 bug#37592: Using tabs in EWW Juri Linkov
2019-10-02 21:20 ` Juri Linkov
2019-10-03 2:44 ` Eli Zaretskii
2019-10-03 22:39 ` Juri Linkov
2019-10-04 7:34 ` Eli Zaretskii [this message]
2019-10-05 22:35 ` Juri Linkov
2019-10-06 17:22 ` Eli Zaretskii
2019-10-06 20:06 ` Lars Ingebrigtsen
2019-10-06 21:08 ` Juri Linkov
2019-10-19 22:40 ` Juri Linkov
2019-10-03 14:20 ` Lars Ingebrigtsen
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=83zhih55h3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=37592@debbugs.gnu.org \
--cc=juri@linkov.net \
/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.