This follows up on
TINKERPOP-2216, which introduced a new status attribute for transmitting warning messages from a remotely executing Gremlin session to the client. Those warning messages are now displayed in the console. They can't be suppressed.
This issue would add some type of lever to gremlin-console so that users can disable display of these server-originated warnings, if desired.
I'm not sure what form that lever should take. Considering that it would be a client-side control, how about a new Preferences entry, accessible through :set warnings true|false? That was my best guess at a natural implementation, but maybe there is a better way.
I'll open a PR with the :set warnings true|false approach just to facilitate discussion, but of course, feel free to close it and take a different tack.