unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] trunk r115470: eww: exit and close actions
Date: Fri, 13 Dec 2013 14:36:56 -0500	[thread overview]
Message-ID: <8761qso84n.fsf@flea.lifelogs.com> (raw)
In-Reply-To: jwv7gb84x0e.fsf-monnier+emacsdiffs@gnu.org

On Fri, 13 Dec 2013 10:06:41 -0500 Stefan Monnier <monnier@IRO.UMontreal.CA> wrote: 

>> Web browsing is a separate UI domain from the other UI domains Emacs
>> covers.  The UI for navigation, input, and even scrolling is different.
>> It's most like an Info file but there are fundamental differences (no
>> clear hierarchy, interactive, etc.)  So my idea was to make web browsing
>> in Emacs more like web browsing outside Emacs, and I thought my changes
>> were a step in that direction.

SM> I view it as trying to lie to the user ;-)

All computing is lying to the user, so I am OK with that.

>> The idea was to separate "close" from "exit" even if the current
>> implementation doesn't do it perfectly, because tha separation is
>> typical in the "web browsing" UI domain.

SM> AFAIK "close" should mean "close the current tab", and "exit" should
SM> mean "exit the application, closing all tabs and killing the process".

Right.

SM> Some of the problems I see in the context of eww:
SM> - eww doesn't have tabs.
SM> - eww-exit doesn't exit the application.
SM> - eww-exit does not close all the eww buffers/tabs/windows you might
SM>   have opened in the current Emacs session.
SM> - eww can display a web page multiple times in different windows, so the
SM>   meaning of "close the tab" is unclear.

I agree the current implementation is suboptimal but your problem is
with the fundamental idea of separating "close" from "exit."  So unless
you want to separate them at some level or at least acknowledge the
difference between them, there's no point in discussing the items above
and we should instead focus on improving `quit-window' or the eww
equivalent thereof.

SM> I really see it as trying to put a square peg in a round hole.
SM> And I really don't see the benefit since eww users will be familiar with
SM> Emacs anyway, so it's not like we'd impose them some new concepts they
SM> shouldn't need to know.

OK, so what would you like (and let's wait for Lars to comment before we
take action, if you want to revert)?

- revert back to `q' being `quit-window', no "close" or "exit" concepts
- implement some way to quit all eww windows for privacy and security
- implement "close" and "exit" differently but still try to separate them
- implement "close" and "exit" separately with different names
- some combination?  something else?

Thanks
Ted




  reply	other threads:[~2013-12-13 19:36 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1Vqp1Z-0004La-IR@vcs.savannah.gnu.org>
2013-12-12 18:52 ` [Emacs-diffs] trunk r115470: eww: exit and close actions Stefan Monnier
2013-12-12 19:17   ` Ted Zlatanov
2013-12-12 22:14     ` Stefan Monnier
2013-12-13 14:36       ` Ted Zlatanov
2013-12-13 15:06         ` Stefan Monnier
2013-12-13 19:36           ` Ted Zlatanov [this message]
2013-12-14  2:07             ` Stefan Monnier
2013-12-14 17:33               ` Ted Zlatanov
2013-12-14 17:49             ` Lars Magne Ingebrigtsen
2013-12-16  0:21               ` T.V. Raman
2013-12-16 22:25               ` Ted Zlatanov
2013-12-16 22:30                 ` Glenn Morris
2013-12-19 16:27                   ` Ted Zlatanov
2013-12-20  0:41                     ` Stephen J. Turnbull
2013-12-20  1:07                       ` Ted Zlatanov
2013-12-20 11:15                         ` Andreas Schwab
2013-12-20 11:32                           ` Ted Zlatanov
2013-12-20 12:00                           ` Stephen J. Turnbull
2013-12-20 13:12                           ` Steinar Bang
2013-12-20 14:36                             ` Ted Zlatanov

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=8761qso84n.fsf@flea.lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=emacs-devel@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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).