You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running tests that log with a custom format, I see that go-test-mode wrongly buttonizes random lines that contain references to file names. Here's an example log line that gets fontified:
This error doesn't match any of the regexes on go-test-compilation-error-regexp-alist-alist (but matches some referenced by the default compilation-error-regexp-alist). As a workaround, I've started doing this:
...and this aligns regexes to correctly buttonize this output; This leads me to suspect gotest picks up the default error regexps from compilation-error-regexp-alist. Is this workaround what I should be doing?
The text was updated successfully, but these errors were encountered:
When running tests that log with a custom format, I see that go-test-mode wrongly buttonizes random lines that contain references to file names. Here's an example log line that gets fontified:
I'd like to define a regexp matching the references contained in these errors, but the following doesn't cause a button to be created:
This error doesn't match any of the regexes on
go-test-compilation-error-regexp-alist-alist
(but matches some referenced by the defaultcompilation-error-regexp-alist
). As a workaround, I've started doing this:...and this aligns regexes to correctly buttonize this output; This leads me to suspect gotest picks up the default error regexps from
compilation-error-regexp-alist
. Is this workaround what I should be doing?The text was updated successfully, but these errors were encountered: