From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13315 invoked by alias); 5 Jun 2011 22:25:04 -0000 Received: (qmail 13300 invoked by uid 22791); 5 Jun 2011 22:25:03 -0000 X-SWARE-Spam-Status: No, hits=-1.5 required=5.0 tests=AWL,BAYES_00,TW_QI,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from fencepost.gnu.org (HELO fencepost.gnu.org) (140.186.70.10) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 05 Jun 2011 22:24:50 +0000 Received: from ams by fencepost.gnu.org with local (Exim 4.71) (envelope-from ) id 1QTLkW-0002ER-Jq; Sun, 05 Jun 2011 18:24:48 -0400 Date: Sun, 05 Jun 2011 22:25:00 -0000 Message-Id: From: ams@gnu.org (Alfred M. Szmidt) To: Jan Kratochvil CC: schwab@linux-m68k.org, mark.kettenis@xs4all.nl, gdb-patches@sourceware.org In-reply-to: <20110605172340.GA14424@host1.jankratochvil.net> (message from Jan Kratochvil on Sun, 5 Jun 2011 19:23:40 +0200) Subject: Re: comments formatting [Re: [patch] physname regression: Non-matching type false breakpoint] Reply-to: ams@gnu.org References: <20110605153419.GA14873@host1.jankratochvil.net> <201106051557.p55FvVIu022894@glazunov.sibelius.xs4all.nl> <20110605161907.GA28751@host1.jankratochvil.net> <20110605163506.GA1273@host1.jankratochvil.net> <20110605165659.GA6565@host1.jankratochvil.net> <20110605172340.GA14424@host1.jankratochvil.net> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2011-06/txt/msg00084.txt.bz2 > OK (in VIM it is gq} or gqip ). I use 79 columns instead of 70. > So in the case of 70 columns what would be the right formatting of: > > /* The strchr check is there if any types were specified verify the single found found parameter types really match those specified by user in COPY. */ This is not a quote of my text, I wrote: /* The strchr check is there if any verify the single found found parameter foo types really match those specified by user in COPY. */ It (c-fill-paragraph) will reformat it correctly, comment starting at column 0: /* The strchr check is there if any verify the single found found parameter foo types really match those specified by user in COPY. */ Starting at column 8: /* The strchr check is there if any verify the single found found parameter foo types really match those specified by user in COPY. */ This applies only to the C mode though, since it takes care to look at how comments start and end; the normal text function, fill-paragraph, does not do that and pretends that a closing comment signature is just a normal word. In which case it would format it like so (column 0): /* The strchr check is there if any verify the single found found parameter foo types really match those specified by user in COPY. */ > It would be the one I produced in the previous email: The text I provided was specially crafted to hit the same problem with 70 columns as I faced with the 79 columns and as I / others will face in the future. When the GNU Coding Standard does describe the comments formatting rules one has to unfortunately reverse engineer them from Emacs. I think that the dangling */ on a single line is a cosmetic thing that hasn't been thought of that much; it looks ugly to have it on a single line.