From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Juanma Barranquero" Newsgroups: gmane.emacs.devel Subject: Re: Image mode Date: Mon, 5 Feb 2007 10:16:29 +0100 Message-ID: References: <87k5yxeg19.fsf@jurta.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1170667012 9219 80.91.229.12 (5 Feb 2007 09:16:52 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 5 Feb 2007 09:16:52 +0000 (UTC) Cc: Juri Linkov , emacs-devel@gnu.org To: "Chong Yidong" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Feb 05 10:16:44 2007 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1HDzxr-00032I-TD for ged-emacs-devel@m.gmane.org; Mon, 05 Feb 2007 10:16:44 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HDzxr-0002i2-Az for ged-emacs-devel@m.gmane.org; Mon, 05 Feb 2007 04:16:43 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HDzxg-0002hx-UH for emacs-devel@gnu.org; Mon, 05 Feb 2007 04:16:32 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HDzxf-0002hl-4v for emacs-devel@gnu.org; Mon, 05 Feb 2007 04:16:32 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HDzxe-0002hi-Tm for emacs-devel@gnu.org; Mon, 05 Feb 2007 04:16:30 -0500 Original-Received: from an-out-0708.google.com ([209.85.132.244]) by monty-python.gnu.org with esmtp (Exim 4.52) id 1HDzxe-0005jy-Mi for emacs-devel@gnu.org; Mon, 05 Feb 2007 04:16:30 -0500 Original-Received: by an-out-0708.google.com with SMTP id b8so845263ana for ; Mon, 05 Feb 2007 01:16:30 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=DX3gP+ripxMoPH5+KQdcQi5ufV3fqDEVRr3iTyEkMCkaLFb6vypVLBcGLJy7tIu6oFXSB4z/Y6psz6d2U4bApUs8IZs5LS55UDH9QSBMWan+4hUR3UFfvnn9zarkDZc+z2AfDdwUIB17Fel9s+jIw174wWwn77zb0YN5ujyG8Rk= Original-Received: by 10.114.111.1 with SMTP id j1mr575031wac.1170666989711; Mon, 05 Feb 2007 01:16:29 -0800 (PST) Original-Received: by 10.114.234.16 with HTTP; Mon, 5 Feb 2007 01:16:29 -0800 (PST) In-Reply-To: Content-Disposition: inline X-detected-kernel: Linux 2.6 (newer, 2) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:65894 Archived-At: On 2/5/07, Juanma Barranquero wrote: > Completely fine by me. On second thought, no, it's not fine by me. If you re-enable `image-toggle-display', having the images *not* shown by default is just an inconvenience: the user's gonna do C-c C-c and wonder why are we making things hard for him. There's no security protection at all, because the user won't be aware there's a security risk. So, if you want to re-enable it, let's scrap the whole last month of image changes and start rethinking it all: whether we want content auto-detection for images, how to warn the user of the possible risks, allowing easy customization for people that already understand the issues, etc. Rewriting is good sometimes. And it shouldn't take long. I'm serious. It's better to delay Emacs 22 a week or two that release a partial solution no one is happy with. /L/e/k/t/u