From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.bugs Subject: Re: comment-kill can't deal with following situation Date: Sun, 02 Mar 2008 00:14:14 -0500 Message-ID: References: <198A33EB1E9E344EBC566802C7761D6B4ACE3C@CNSHGSMBS04.ad4.ad.alcatel.com> <86tzjsqb47.fsf@163.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1204434871 30194 80.91.229.12 (2 Mar 2008 05:14:31 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 2 Mar 2008 05:14:31 +0000 (UTC) Cc: bug-gnu-emacs@gnu.org To: lgfang Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sun Mar 02 06:14:57 2008 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 1JVgXI-0005tF-JZ for geb-bug-gnu-emacs@m.gmane.org; Sun, 02 Mar 2008 06:14:57 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JVgWl-0002GF-C2 for geb-bug-gnu-emacs@m.gmane.org; Sun, 02 Mar 2008 00:14:23 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JVgWg-0002GA-Ir for bug-gnu-emacs@gnu.org; Sun, 02 Mar 2008 00:14:18 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JVgWd-0002Fy-VI for bug-gnu-emacs@gnu.org; Sun, 02 Mar 2008 00:14:17 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JVgWd-0002Fv-PB for bug-gnu-emacs@gnu.org; Sun, 02 Mar 2008 00:14:15 -0500 Original-Received: from ironport2-out.pppoe.ca ([206.248.154.182]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JVgWd-0003JH-Sp for bug-gnu-emacs@gnu.org; Sun, 02 Mar 2008 00:14:16 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ao8CAKPGyUdMCpz5Wmdsb2JhbACQZgEgmT+BAA X-IronPort-AV: E=Sophos;i="4.25,433,1199682000"; d="scan'208";a="15451103" Original-Received: from smtp.pppoe.ca ([65.39.196.238]) by ironport2-out.pppoe.ca with ESMTP; 02 Mar 2008 00:14:14 -0500 Original-Received: from pastel.home ([76.10.156.249]) by smtp.pppoe.ca (Internet Mail Server v1.0) with ESMTP id IIQ10415; Sun, 02 Mar 2008 00:14:15 -0500 Original-Received: by pastel.home (Postfix, from userid 20848) id 6C0D38279; Sun, 2 Mar 2008 00:14:14 -0500 (EST) In-Reply-To: <86tzjsqb47.fsf@163.com> (lgfang's message of "Fri, 29 Feb 2008 19:02:16 +0800") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux) X-detected-kernel: by monty-python.gnu.org: Genre and OS details not recognized. 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:17634 Archived-At: > comment-kill is defined in newcomment.el. It is supposed to kill > comments (refer to its document). But it can't deal with the cases in > which there are more than one comment in a line. An example is: If you do not provide a prefix arg, comment-kill should only kill 1 comment. Indeed when providing a prefix arg, the behavior is probably not right. Actually, when I wrote it I just tried to reproduce the previous behavior. But in the presence of multi-line comments, the behavior doesn't match the docstring either. I don't know of anybody who uses the prefix arg of comment-kill, so if you could explain how you use it, it might help decide what the behavior should be. Stefan