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#3395: 23.0.94; Remove colon after option etc. name Date: Thu, 28 May 2009 09:08:25 -0700 Message-ID: <454F42E7EE4E4D469F610AF5A18AE342@us.oracle.com> References: <43B19EE291914BCFA51EC5AFA8C91ADB@us.oracle.com> <4A1EAAAA.9030706@gmx.at> <4A1EB10C.7090803@gmx.at> Reply-To: Drew Adams , 3395@emacsbugs.donarmstrong.com NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1243528216 21844 80.91.229.12 (28 May 2009 16:30:16 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 28 May 2009 16:30:16 +0000 (UTC) Cc: 3395@emacsbugs.donarmstrong.com To: "'martin rudalics'" Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Thu May 28 18:30:13 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 1M9iUc-0002G5-V5 for geb-bug-gnu-emacs@m.gmane.org; Thu, 28 May 2009 18:30:11 +0200 Original-Received: from localhost ([127.0.0.1]:41790 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1M9iUc-0004GM-EU for geb-bug-gnu-emacs@m.gmane.org; Thu, 28 May 2009 12:30:10 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1M9iTn-00041O-HE for bug-gnu-emacs@gnu.org; Thu, 28 May 2009 12:29:19 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1M9iTj-00040M-3W for bug-gnu-emacs@gnu.org; Thu, 28 May 2009 12:29:19 -0400 Original-Received: from [199.232.76.173] (port=52919 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1M9iTi-00040J-T8 for bug-gnu-emacs@gnu.org; Thu, 28 May 2009 12:29:14 -0400 Original-Received: from rzlab.ucr.edu ([138.23.92.77]:59206) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1M9iTi-0006Ek-D3 for bug-gnu-emacs@gnu.org; Thu, 28 May 2009 12:29:14 -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 n4SGTC2g010101; Thu, 28 May 2009 09:29:12 -0700 Original-Received: (from debbugs@localhost) by rzlab.ucr.edu (8.14.3/8.14.3/Submit) id n4SGF4FF008176; Thu, 28 May 2009 09:15:04 -0700 X-Loop: owner@emacsbugs.donarmstrong.com Resent-From: "Drew Adams" Resent-To: bug-submit-list@donarmstrong.com Resent-CC: Emacs Bugs Resent-Date: Thu, 28 May 2009 16:15:04 +0000 Resent-Message-ID: Resent-Sender: owner@emacsbugs.donarmstrong.com X-Emacs-PR-Message: followup 3395 X-Emacs-PR-Package: emacs X-Emacs-PR-Keywords: Original-Received: via spool by 3395-submit@emacsbugs.donarmstrong.com id=B3395.12435269137401 (code B ref 3395); Thu, 28 May 2009 16:15:04 +0000 Original-Received: (at 3395) by emacsbugs.donarmstrong.com; 28 May 2009 16:08:33 +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 n4SG8TPK007396 for <3395@emacsbugs.donarmstrong.com>; Thu, 28 May 2009 09:08:30 -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 n4SG84Ae022339 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 28 May 2009 16:08:06 GMT Original-Received: from abhmt003.oracle.com (abhmt003.oracle.com [141.146.116.12]) by acsinet15.oracle.com (Switch-3.3.1/Switch-3.3.1) with ESMTP id n4SG9BEq009039; Thu, 28 May 2009 16:09:11 GMT Original-Received: from dradamslap1 (/130.35.178.194) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 28 May 2009 09:08:20 -0700 X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <4A1EB10C.7090803@gmx.at> Thread-Index: AcnfqypefjdbDlXXS2qy5gJj3nbc5gAAbEqg X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 X-Source-IP: abhmt003.oracle.com [141.146.116.12] X-Auth-Type: Internal IP X-CT-RefId: str=0001.0A01020A.4A1EB6F4.0134:SCFSTAT5015188,ss=1,fgs=0 X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 3) Resent-Date: Thu, 28 May 2009 12:29:19 -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:28266 Archived-At: > > I specifically went to the trouble of speaking in generic > > terms, talking about "a command that picks up the symbol > > at point", without referring to any specific > > such command, such as `variable-at-point'. > > The colon _has_ punctuation syntax in custom buffers. It's the syntax > table chosen by `variable-at-point' which messes up things in > your case. I don't use `variable-at-point'. I do use a command that uses Emacs-Lisp symbol syntax, which is the right syntax to use here. Please stop trying to fix the command. The fix is to remove the useless colon. Trivial. > > The fix I mentioned lets you use any command at all that > > picks up symbol syntax here. A change to `variable-at-point' > > is not what I'm asking for - that will not > > affect other commands that (already DTRT) pick up a symbol > > name at or near point. > > Commands that do not change the syntax table do get this right. Try, > for example, info-lookup on such an item. It should even work for > unlispified items. That's fine, but it is totally unrelated to what I reported and requested. (FWIW, the interactive spec of `info-lookup' (`info-lookup-interactive-arguments') is very complex, requires specific knowledge of the given mode, and so on.) This is not about changing the command. It is simply about removing the useless colon. Is that too hard? > > Simply removing the colon solves the problem, and it has > > absolutely no negative effect. Besides being bothersome here, > > the colon is 100% useless. > > Changing customization code is 100% dangerous. Don't be ridiculous. You are making, in several separate ways, a mountain out of a mole hill.