From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Space after inline comment char Date: Mon, 17 Apr 2006 07:55:13 -0400 Message-ID: <87irp8pgkm.fsf-monnier+emacs@gnu.org> References: <32708.1145055187@olgas.newt.com> <8764lbv8ia.fsf-monnier+emacs@gnu.org> <87zmilu3hn.fsf-monnier+emacs@gnu.org> <87ejzwsvxs.fsf-monnier+emacs@gnu.org> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1145274954 24060 80.91.229.2 (17 Apr 2006 11:55:54 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 17 Apr 2006 11:55:54 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Apr 17 13:55:53 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1FVSKe-0000bK-Ny for ged-emacs-devel@m.gmane.org; Mon, 17 Apr 2006 13:55:53 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FVSKe-0004UB-8z for ged-emacs-devel@m.gmane.org; Mon, 17 Apr 2006 07:55:52 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FVSK8-0004Lq-Ar for emacs-devel@gnu.org; Mon, 17 Apr 2006 07:55:20 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FVSK3-0004J9-O6 for emacs-devel@gnu.org; Mon, 17 Apr 2006 07:55:19 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FVSK3-0004Ih-5O for emacs-devel@gnu.org; Mon, 17 Apr 2006 07:55:15 -0400 Original-Received: from [209.226.175.110] (helo=tomts43-srv.bellnexxia.net) by monty-python.gnu.org with esmtp (Exim 4.52) id 1FVSKg-0005g8-QL for emacs-devel@gnu.org; Mon, 17 Apr 2006 07:55:55 -0400 Original-Received: from alfajor ([70.53.192.213]) by tomts43-srv.bellnexxia.net (InterMail vM.5.01.06.13 201-253-122-130-113-20050324) with ESMTP id <20060417115514.TNYE1543.tomts43-srv.bellnexxia.net@alfajor>; Mon, 17 Apr 2006 07:55:14 -0400 Original-Received: by alfajor (Postfix, from userid 1000) id 6BB52D7384; Mon, 17 Apr 2006 07:55:13 -0400 (EDT) Original-To: Ralf Angeli In-Reply-To: (Ralf Angeli's message of "Mon, 17 Apr 2006 11:28:23 +0200") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) 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:52957 Archived-At: >>> That will result in >>> ; foo >>> whereas it should be >>> ;; foo >> >> Good point. I believe the patch below has fixed it, > It did. I still think it would be nice if one could control spaces > after comment starterts with `comment-padding' _everywhere_, > i.e. after comment starters inserted by `comment-indent' as well. > That would feel more consistent. But then, the doc string of > `comment-padding' only talks about `comment-region'. When I re-implemented the comment commands in newcomment.el, I just preserved this part of the behavior (that comment-padding only applies to comment-region but not to comment-indent). I don't know what was the original motivation for it (if any), but without introducting a separate comment-indent-padding, changing the behavior would have meant that I'd have removed some functionality (the ability to (indirectly) specify different amounts of padding), so I decided to keep it as is. Stefan