While we would like do more with non-MathWorks languages like C, Java, Fortran, etc, there are already great environments for programming these languages like Visual Studio, Xcode, Eclipse, IntelliJ, etc. As far as I know, MATLAB is only IDE with a fully-functional Editor/Debugger for the MATLAB language. Therefore our first responsibility is to help out people programming MATLAB code.

That doesn’t mean we don’t have some new and neat features planned for editing other languages. :-)

I think you could fit a small button below the existing ‘Fix’ one in the dead space (right aligned on the same line as ‘Press Alt-Enter to fix, Alt-??? to suppress). Otherwise you’d have to switch to the keyboard when you were just using the mouse to view the message. A keybinding would also be helpful though for when you are navigating with the keyboard.

To address your first point, if you already have your hand on the mouse to hover over the message, why would you move to the keyboard to expand it rather than click the hyperlink? (That’s the general “you”, btw) That was our thinking for not providing the keyboard expand action in the mouse situation.

Your second point would be convenient, but we did not want to complicate an already busy “tooltip” by adding more buttons. I’m toying with the idea of adding a keybinding for quick message suppression.

I noticed that if I bring up the M-lint message by hovering over it with the mouse, Ctrl-m doesn’t expand it - this only works if you initially bring up the message by cursoring to it and then Ctrl-m’ing. This seems odd.

Also, it would be nice if there was a ‘Suppress’ button on the message alongside the ‘Fix’ button. Right now you have to switch to a different context/menu using right-click and then find the correct option, instead of just quickly clicking a button.

Best,
Eric S.

The %#ok directives are particular to each message type, depending on the ID. For example for the using semicolon in a function, the directive is %#ok<NOPRT>. This will suppress the “Terminate statement with semicolon…” for just the line the directive appears on. You can also with a single directive suppress all “Terminate statement…” mssages in the file; it looks like: %#ok<*NOPRT>. The context menu will insert these automatically for you.

the first solution is the general one, I mentioned as not satisfying, as it treats all lines in the same way (it only distinguishes between scripts and functions).

The second one is a more specific solution which seems to fit my needs. One question: Does the %#ok directive only deactivate the semicolon warning or are all tests omitted?

Michael

You have a few options in this case:

1. Specifically for the semi-colon, we have two separate messages, one for functions and one for scripts. From the M-Lint Preferences (File -> Preferences) you can disable the message for scrips and leave the one for functions enabled.

2. You can suppress an individual warning just for one instance or the whole file using the right-click context menu on an individual message. This inserts a %#ok directive into the file’s text.

In most cases it is usefull to supress the output, but especially in scripts I want to see selected outputs in the command window.

In this situation I can only deactivate the specific warning complete or not. The result is, the specific item will not be checked in the whole file or there will be some warnings, I have to ignore.

Michael