This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: comments formatting [Re: [patch] physname regression: Non-matching type false breakpoint]


> Date: Sun, 5 Jun 2011 18:35:06 +0200
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
> 
> On Sun, 05 Jun 2011 18:23:40 +0200, Andreas Schwab wrote:
> > Jan Kratochvil <jan.kratochvil@redhat.com> writes:
> > > I agree, this commonly happens, I do not know what is the right way to do with it.
> > 
> > M-q (c-fill-paragraph)
> 
> What does it do?  I use VIM.

See, there is your problem ;).

Seriosuly though, given that people use different tools some
reformatting of comments simply can't be avoided.  If I make changes
to a comment I'll make some effort to minimize the diff, but if the
changes are in the middle of the comment, or if the end-result simply
looks wrong I'll simply hit M-q and be done with it.  And */ on a line
of its own will almost certainly make me hit M-q.  Which is why I
brought this up.

In this case I'd simply move the last word of the previous line to the
next line to avoid the dangling */.

Cheers,

Mark


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]