From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ivan Shmakov Newsgroups: gmane.emacs.devel Subject: EWW buffers Date: Wed, 19 Nov 2014 16:12:17 +0000 Message-ID: <87wq6r41b2.fsf_-_@violet.siamics.net> References: <87a93oh180.fsf@lifelogs.com> <83h9xw9zg3.fsf@gnu.org> <83d28k9yb9.fsf@gnu.org> <83ppcj9740.fsf@gnu.org> <871toze1tl.fsf@lifelogs.com> <87wq6rcidx.fsf@lifelogs.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1416413577 18944 80.91.229.3 (19 Nov 2014 16:12:57 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 19 Nov 2014 16:12:57 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Nov 19 17:12:49 2014 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 1Xr7s8-00036z-Rx for ged-emacs-devel@m.gmane.org; Wed, 19 Nov 2014 17:12:48 +0100 Original-Received: from localhost ([::1]:59287 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xr7s8-0001Lt-Bx for ged-emacs-devel@m.gmane.org; Wed, 19 Nov 2014 11:12:48 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:34268) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xr7rr-0001HF-0h for emacs-devel@gnu.org; Wed, 19 Nov 2014 11:12:34 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Xr7rn-0003vE-1o for emacs-devel@gnu.org; Wed, 19 Nov 2014 11:12:30 -0500 Original-Received: from fely.am-1.org ([2a01:4f8:d15:1b86::2]:47605) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xr7rm-0003ux-R0 for emacs-devel@gnu.org; Wed, 19 Nov 2014 11:12:26 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=siamics.net; s=a2013295; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Message-ID:In-Reply-To:Date:Sender:References:Subject:To:From; bh=PHctY7kCvtyvJN4a30TgR61zT6aKm+2Jlp0xGxcYzQ0=; b=WCHcchYzDj6RzJX/XUVRaOl+S8jfO0j/K31UHhOnF0oQzCYG9n5QsROD831F9dtyrGqiNWI5xMyFQEuFwH8q/WIs62AJh41khOuA6QPkBDfoj7xQPvgXtMG9gq0Dx4MFJZrWsvjo35Mt+PoN9DIKGHDrfmR+YVaADDqM/6Egl6s=; Original-Received: from [2a02:2560:6d4:26ca::1:1d] (helo=violet.siamics.net) by fely.am-1.org with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1Xr7rl-0005NS-M8 for emacs-devel@gnu.org; Wed, 19 Nov 2014 16:12:25 +0000 Original-Received: from localhost ([::1] helo=violet.siamics.net) by violet.siamics.net with esmtps (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1Xr7re-0006eK-If for emacs-devel@gnu.org; Wed, 19 Nov 2014 23:12:18 +0700 In-Reply-To: (Lars Magne Ingebrigtsen's message of "Wed, 19 Nov 2014 16:47:43 +0100") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a01:4f8:d15:1b86::2 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:177768 Archived-At: >>>>> Lars Magne Ingebrigtsen writes: >>>>> Ted Zlatanov writes: >> You could create the *eww* buffer immediately? > We could, but it would look kinda odd. Or perhaps not? Pop up the > empty buffer saying "Loading..." It's possible. It=E2=80=99s also perfectly possible to create that buffer but do /not/ switch to it until it=E2=80=99s ready. It won=E2=80=99t help in the scena= rio being discussed, but to be honest, EWW already pops its buffers way to often to my taste. Consider, for instance, invoking eww-reload in a handful of buffers in a row, =E2=80=93 EWW will switch to each of these buffers as soon as one=E2=80=99s done, which could very well happen in the middle of user interaction with some specific buffer. Granted, it=E2=80=99s possible to switch to a EWW buffer, invoke eww-reload, wait for it to complete, and only /then/ go to some other buffer (whether EWW or not), but that kind of spoils the benefits of asynchronous url-retrieve operation, doesn=E2=80=99t it? [=E2=80=A6] --=20 FSF associate member #7257 http://boycottsystemd.org/ =E2=80=A6 3013 B6A0= 230E 334A