From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Drew Adams" Newsgroups: gmane.emacs.bugs Subject: bug#3400: bug in add-text-properties Date: Fri, 29 May 2009 07:51:24 -0700 Message-ID: References: <20090528.234833.147211632.wl@gnu.org><20090529.090050.266105248.wl@gnu.org> Reply-To: Drew Adams , 3400@emacsbugs.donarmstrong.com NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1243609894 12445 80.91.229.12 (29 May 2009 15:11:34 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 29 May 2009 15:11:34 +0000 (UTC) To: "'Lennart Borgman'" , <3400@emacsbugs.donarmstrong.com>, "'Werner LEMBERG'" Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Fri May 29 17:11:30 2009 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1MA3k0-0004Kf-8k for geb-bug-gnu-emacs@m.gmane.org; Fri, 29 May 2009 17:11:28 +0200 Original-Received: from localhost ([127.0.0.1]:42421 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MA3jw-00061O-GJ for geb-bug-gnu-emacs@m.gmane.org; Fri, 29 May 2009 11:11:24 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MA3WT-00014A-Qn for bug-gnu-emacs@gnu.org; Fri, 29 May 2009 10:57:30 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MA3WN-00012H-Pi for bug-gnu-emacs@gnu.org; Fri, 29 May 2009 10:57:27 -0400 Original-Received: from [199.232.76.173] (port=32814 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MA3WL-00011n-RU for bug-gnu-emacs@gnu.org; Fri, 29 May 2009 10:57:21 -0400 Original-Received: from rzlab.ucr.edu ([138.23.92.77]:48988) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MA3WK-00045w-7w for bug-gnu-emacs@gnu.org; Fri, 29 May 2009 10:57:20 -0400 Original-Received: from rzlab.ucr.edu (rzlab.ucr.edu [127.0.0.1]) by rzlab.ucr.edu (8.14.3/8.14.3/Debian-5) with ESMTP id n4TEvHv7006816; Fri, 29 May 2009 07:57:18 -0700 Original-Received: (from debbugs@localhost) by rzlab.ucr.edu (8.14.3/8.14.3/Submit) id n4TEt8jW006261; Fri, 29 May 2009 07:55:08 -0700 X-Loop: owner@emacsbugs.donarmstrong.com Resent-From: "Drew Adams" Resent-To: bug-submit-list@donarmstrong.com Resent-CC: Emacs Bugs Resent-Date: Fri, 29 May 2009 14:55:08 +0000 Resent-Message-ID: Resent-Sender: owner@emacsbugs.donarmstrong.com X-Emacs-PR-Message: followup 3400 X-Emacs-PR-Package: emacs X-Emacs-PR-Keywords: Original-Received: via spool by 3400-submit@emacsbugs.donarmstrong.com id=B3400.12436086986006 (code B ref 3400); Fri, 29 May 2009 14:55:08 +0000 Original-Received: (at 3400) by emacsbugs.donarmstrong.com; 29 May 2009 14:51:38 +0000 X-Spam-Bayes: score:0.5 Bayes not run. spammytokens:Tokens not available. hammytokens:Tokens not available. Original-Received: from acsinet12.oracle.com (acsinet12.oracle.com [141.146.126.234]) by rzlab.ucr.edu (8.14.3/8.14.3/Debian-5) with ESMTP id n4TEpXmP005988 for <3400@emacsbugs.donarmstrong.com>; Fri, 29 May 2009 07:51:34 -0700 Original-Received: from acsinet15.oracle.com (acsinet15.oracle.com [141.146.126.227]) by acsinet12.oracle.com (Switch-3.3.1/Switch-3.3.1) with ESMTP id n4TEp8XD017281 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 29 May 2009 14:51:09 GMT Original-Received: from abhmt008.oracle.com (abhmt008.oracle.com [141.146.116.17]) by acsinet15.oracle.com (Switch-3.3.1/Switch-3.3.1) with ESMTP id n4TEqGxQ008939; Fri, 29 May 2009 14:52:17 GMT Original-Received: from dradamslap1 (/141.144.81.143) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Fri, 29 May 2009 07:51:24 -0700 X-Mailer: Microsoft Office Outlook 11 In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 Thread-Index: AcngYwjAQSO0NW+ASiueDF6zhLNa1gACLlTQ X-Source-IP: abhmt008.oracle.com [141.146.116.17] X-Auth-Type: Internal IP X-CT-RefId: str=0001.0A090203.4A1FF66D.0051:SCFSTAT5015188,ss=1,fgs=0 X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) Resent-Date: Fri, 29 May 2009 10:57:27 -0400 X-BeenThere: bug-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:28288 Archived-At: > >> Point is at position 1 (i.e. just before the char "1" rather than > >> before the char "A"), so it makes sense for C-h =3D to return data > >> about that position rather than about some other position one line > >> down. > > > > I disagree. =A0Whereever point is, it should report the=20 > > character after point which is accessible (this is, visible). > >=A0Perhaps it makes sense to add a red warning message in the > > output of `C-x =3D' that point is > > not located right before the displayed character. >=20 > I agree with you here, Werner. And I think the red warning is=20 > a good idea too. I haven't followed this thread, so apologies if I miss the point. To me, we want C-x =3D to give as much info as possible, including info = about positions that we might not be able to see or even to reach/access by positioning point. Since there already is a way to get info about the positions that are = accessible and those that are visible, by moving the cursor a bit, there is no loss = in also providing info about positions that are inaccessible or invisible. So I = think I agree with Stefan here (if this is in fact what he says): C-x =3D should = return info about the closest position you can access. That is, if C-x =3D can help by giving some info about invisible or = intangible chars, so much the better. Nothing prevents us from moving the cursor a = bit and getting the info about the accessible, visible, boundary positions. If the info shown for such unusual positions is accurate, it will, = itself, indicate that the char is intangible or invisible or whatever. But I do = agree that perhaps some extra notification (red or, preferably just an = additional statement) of this might be helful. (But please don't call such a = notification a "warning".) Again, ignore if not relevant.