From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Karl Fogel Newsgroups: gmane.emacs.devel Subject: Re: eww Date: Tue, 18 Jun 2013 13:04:30 -0500 Message-ID: <87vc5bthw1.fsf@kwarm.red-bean.com> References: <87d2rkb1pi.fsf@fleche.redhat.com> <87fvwfa3ev.fsf@fleche.redhat.com> Reply-To: Karl Fogel NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1371578684 32131 80.91.229.3 (18 Jun 2013 18:04:44 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 18 Jun 2013 18:04:44 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jun 18 20:04:45 2013 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Up0Gp-0006h0-Si for ged-emacs-devel@m.gmane.org; Tue, 18 Jun 2013 20:04:44 +0200 Original-Received: from localhost ([::1]:43192 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Up0Gp-0006is-FE for ged-emacs-devel@m.gmane.org; Tue, 18 Jun 2013 14:04:43 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:45196) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Up0Gi-0006dh-Jr for emacs-devel@gnu.org; Tue, 18 Jun 2013 14:04:40 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Up0Gf-00062l-EE for emacs-devel@gnu.org; Tue, 18 Jun 2013 14:04:36 -0400 Original-Received: from mail-ie0-x232.google.com ([2607:f8b0:4001:c03::232]:61984) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Up0Gf-00062g-87 for emacs-devel@gnu.org; Tue, 18 Jun 2013 14:04:33 -0400 Original-Received: by mail-ie0-f178.google.com with SMTP id u16so10275414iet.23 for ; Tue, 18 Jun 2013 11:04:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:from:to:subject:references:reply-to:date:in-reply-to :message-id:user-agent:mime-version:content-type; bh=EnxcuwOB1aXxPDwaCyB77GsNkMfqI45fzg+T3icbWrU=; b=DbaGp0U+SgybhT1wU7gRkdnzU3xIJoHwuKgbxRvx+JCjhZj3LZz/aqDckkoyn/UxXh 7ktIU6A8UijiWYfkfRM4Un/OIwPH1uDefzEnxrtQEOuO2vSVLzDSJ5mSntYxMCSdN4W4 6TeT38vBpCH7MW2+UXKxAryQ8eG8pcibsIOwFjURHFTrfSSyDGXIWAB4NTqYVjIHk6jS erb00uD+6lycO2i01bDbZXXeRdrrfRb8Vtw/nkqnfNBrUCCL9yKWsVR3l0PQKdvl4Uxo jQMxptSWRLh11+DrmUeEN1rWbyteJeoxz4/kO30t3phVg7387Hz6nTI5AorCX7Cr54Xk a2Nw== X-Received: by 10.50.107.6 with SMTP id gy6mr3164071igb.5.1371578672303; Tue, 18 Jun 2013 11:04:32 -0700 (PDT) Original-Received: from kwarm.red-bean.com (74-92-190-113-Illinois.hfc.comcastbusiness.net. [74.92.190.113]) by mx.google.com with ESMTPSA id j3sm2092254igv.4.2013.06.18.11.04.31 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Tue, 18 Jun 2013 11:04:31 -0700 (PDT) In-Reply-To: (Lars Magne Ingebrigtsen's message of "Tue, 18 Jun 2013 17:48:47 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2607:f8b0:4001:c03::232 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:160590 Archived-At: Lars Magne Ingebrigtsen writes: >Currently eww uses a single buffer, and whenever you ask it to display a >new URL, it discards everything in the buffer. This means that when you >want to return to the previous page, eww has to re-fetch and re-render >the page. And you lose the data in
s you have filled out. > >Would it make more sense for eww to use new buffers every time? eww >would have a backlog of, say, ten buffers, and going back to the >previous page would just mean popping to the previous buffer. And it >could use `bury-buffer' and rename the previous buffer to a name with >something leading with " " when you go to a new page. > >Opinions? I second the questions Eli asked, but FWIW: No reason to limit the number of buffers here. It makes sense to always keep them except when the user explicitly kills one (or sets some var indicating that eww should kill buffers). Each buffer has a "reload" keybinding, right? And when a user goes to a URL that eww already has a buffer for, it can reuse that buffer and do the reload. The edge case question is: if you have filled-out form data in a buffer, and then eww does a reload, should it toss your data? In that case, I think it makes sense to rename the original buffer -- the one with the filled-out form data -- to "buffer" where N increases, and reload into "buffer". In other words, if someone panics and realizes they shouldn't have thrown away the novel they wrote in that gigantic text form, at least there is a way to recover it (from the "" buffer). Very excited about eww! -K