From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Simon Josefsson Newsgroups: gmane.emacs.devel Subject: Re: Problems with info (emacs version) Date: Tue, 03 Jun 2003 08:35:51 +0200 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: References: <200306020333.h523XMC23468@eel.dms.auburn.edu> <200306030522.h535MWh24584@eel.dms.auburn.edu> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1054622394 18239 80.91.224.249 (3 Jun 2003 06:39:54 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Tue, 3 Jun 2003 06:39:54 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Tue Jun 03 08:39:52 2003 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 19N5Sa-0004k3-00 for ; Tue, 03 Jun 2003 08:39:52 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian)) id 19N5jZ-0001F4-00 for ; Tue, 03 Jun 2003 08:57:25 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.20) id 19N5Pr-0003c4-4j for emacs-devel@quimby.gnus.org; Tue, 03 Jun 2003 02:37:03 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20) id 19N5PR-0003RP-D3 for emacs-devel@gnu.org; Tue, 03 Jun 2003 02:36:37 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20) id 19N5PG-00039t-Ng for emacs-devel@gnu.org; Tue, 03 Jun 2003 02:36:27 -0400 Original-Received: from 178.230.13.217.in-addr.dgcsystems.net ([217.13.230.178] helo=yxa.extundo.com) by monty-python.gnu.org with esmtp (Exim 4.20) id 19N5Ot-00030Z-GK; Tue, 03 Jun 2003 02:36:03 -0400 Original-Received: from latte.josefsson.org (yxa.extundo.com [217.13.230.178]) (authenticated bits=0) by yxa.extundo.com (8.12.9/8.12.9) with ESMTP id h536ZpB4009331 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK); Tue, 3 Jun 2003 08:35:52 +0200 Original-To: Miles Bader Mail-Copies-To: nobody X-Payment: hashcash 1.2 0:030603:miles@gnu.org:4a3d40fa3c473e11 X-Hashcash: 0:030603:miles@gnu.org:4a3d40fa3c473e11 X-Payment: hashcash 1.2 0:030603:teirllm@dms.auburn.edu:be7649a86e6e3b81 X-Hashcash: 0:030603:teirllm@dms.auburn.edu:be7649a86e6e3b81 X-Payment: hashcash 1.2 0:030603:emacs-devel@gnu.org:558d59b404373b01 X-Hashcash: 0:030603:emacs-devel@gnu.org:558d59b404373b01 X-Payment: hashcash 1.2 0:030603:rms@gnu.org:a656ec56c7d8bc35 X-Hashcash: 0:030603:rms@gnu.org:a656ec56c7d8bc35 In-Reply-To: (Miles Bader's message of "03 Jun 2003 15:07:00 +0900") User-Agent: Gnus/5.1003 (Gnus v5.10.3) Emacs/21.3.50 (gnu/linux) Original-cc: rms@gnu.org Original-cc: Luc Teirlinck X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1b5 Precedence: list List-Id: Emacs development discussions. List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:14619 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:14619 Miles Bader writes: > Simon Josefsson writes: >> I'd say this is a bug in the mail sending part of Emacs. Message asks >> the user if she knows about the hidden parts. > > That's a solution, but not a very good one in my experience. > I think final message sending is the wrong time to do this -- whenever I > get that message I'm a bit surprised and unsure what to do, as it's not > always clear _where_ the invisible text was, and having to go back and > re-edit a message that I thought was ready to send is very annoying. I agree! A similar topic was just discussed on the ding mailing list. A better solution may be to somehow visually highlight the hidden text. That may sound like a contradiction, but of course, it should only happen that way in the mail buffer, so makes some sense. > What's wrong with just adding `invisible' to the default list of > properties stripped by yanking? Could work. But if, say, message uses the invisible property internally to keep some hidden data around in the buffer, cut'n'paste within the message buffer can generate unexpected result.