unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: Lars Magne Ingebrigtsen <larsi@gnus.org>, emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] trunk r115470: eww: exit and close actions
Date: Sat, 14 Dec 2013 12:33:20 -0500	[thread overview]
Message-ID: <871u1fnxr3.fsf@flea.lifelogs.com> (raw)
In-Reply-To: <jwvlhzo198s.fsf-monnier+emacsdiffs@gnu.org> (Stefan Monnier's message of "Fri, 13 Dec 2013 21:07:00 -0500")

On Fri, 13 Dec 2013 21:07:00 -0500 Stefan Monnier <monnier@IRO.UMontreal.CA> wrote: 

>> I agree the current implementation is suboptimal but your problem is
>> with the fundamental idea of separating "close" from "exit."

SM> No, the problem is with calling eww-close instead of quit-window, and
SM> with calling eww-exit instead of kill-this-buffer.  To me, this is
SM> just obfuscation.

I understand we disagree on this.

>> - revert back to `q' being `quit-window',

SM> Yes.  As I said elsewhere, I think this binding should basically be
SM> inherited from special-mode-map.

>> - implement some way to quit all eww windows for privacy and security

SM> If someone wants that, I'm not opposed to it (tho "quitting all windows"
SM> won't give you any privacy or security benefits, so it will presumably
SM> do something else).  But I wouldn't call it "exit".  The name should
SM> instead include something like clear/wipe/flush/...

I will wait for Lars to make the final decision.  If he agrees with you,
going to just `special-mode-map' is probably the best way, and we can
forget about special "quit all" functionality.

Ted



  reply	other threads:[~2013-12-14 17:33 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
2013-12-14  2:07             ` Stefan Monnier
2013-12-14 17:33               ` Ted Zlatanov [this message]
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=871u1fnxr3.fsf@flea.lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.org \
    --cc=monnier@IRO.UMontreal.CA \
    /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).