GNU bug report logs - #8943
octave mode: "mismatched parentheses" warning on multiline comments

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 8943 in the body.
You can then email your comments to 8943 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: fork <forkandwait <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: octave mode: "mismatched parentheses" warning on multiline comments 
Date: Mon, 27 Jun 2011 17:05:10 +0000 (UTC)

When using multiline comments in octave mode, there is a "mismatched
parentheses" warning issued to the mini-buffer when closing the comment.  

For example, the warning appears on the final "}" in the following code:

%{
blah blah blah 
%}

There doesn't seem to be any problems with indentation.  Also, I see the same
result for both "#{" and "%{"

Thanks for all your excellent work!

Message #8 received at 8943 <at> debbugs.gnu.org (full text, mbox):

From: Stefan Monnier <monnier <at> iro.umontreal.ca>
To: fork <forkandwait <at> gmail.com>
Cc: 8943 <at> debbugs.gnu.org
Subject: Re: bug#8943: octave mode: "mismatched parentheses" warning on
	multiline comments
Date: Mon, 04 Jul 2011 16:20:23 -0400

tags 8943 wontfix
thanks

> When using multiline comments in octave mode, there is a "mismatched
> parentheses" warning issued to the mini-buffer when closing the comment.
> For example, the warning appears on the final "}" in the following code:

> %{
> blah blah blah 
> %}

> There doesn't seem to be any problems with indentation.  Also, I see the same
> result for both "#{" and "%{"

Indeed, that's a bug.  A related bug that can be seen in all programming
modes is that if you type something like

     // some comment (and some
     // side note).

the final ) will not be matched to the opening (.  It will either raise
a "mismatched parenthesis" warning or will be matched to some
unrelated open parenthesis.

Your case is slightly different since the paren is actually part
of the comment-marker rather than being inside the comment, but the
problem has basically the same origin.

I don't expect we'll fix this problem any time soon, tho.


        Stefan

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.