5 ms·
Please put file locations (as many as might be relevant) at the start of a line in the standard format! The other changes look valuable. Improving error repor
by dllthomas 10y ago
Please put file locations (as many as might be relevant) at the start of a line in the standard format!
The other changes look valuable. Improving error reporting is great.
Edited to add emphasis: I really did mean a line, not every line.
- pcwalton 10y agoThose file locations repeated every line accounted for a lot of the noise in the previous format. I'm glad they're gone.
- db48x 10y agoAgreed. Get a dozen errors at once and you can feel your eyes glass over from all of the repeated file names. Better to just update the error parser in emacs.
- dllthomas 10y agoI actually agree about the repetition. I was speaking to formatting of the file locations that are included. Far better to remove (or move) for characters, than to update every tool to handle yet another format (and/or increase false positives in detection of src locations in an error stream).
- dllthomas 10y agofour characters too late to edit...
- dllthomas 10y agoThe repetition is not what I was speaking of. As you say, including the same file name N times with successive line numbers just because you've localized the error somewhere in that span means a bunch of noise. But where you are going to include a file location (and one is included), put it at the beginning of the line, to be friendly to existing to existing tooling. Putting the "-->" in front of the location is not what makes this format more readable. (Including multiple locations is great where they are actually distinct locations.)
- __david__ 10y agoAll I want is for C-x ` to work in Emacs's built-in compilation-mode. As long as the new error reporting doesn't break that, I and the other Emacs "M-x compile" users will be happy campers.
- nhaehnle 10y agoPlease, take those complaints from others seriously. There are plenty of tools that help people (including myself) to deal with compiler errors more easily, and they're not limited to emacs either. For most purposes, having at least _one_ line in the standard 'filename:linenumber:[column:] {error,warning,...}:' format is sufficient for compatibility. You have such a line already; just remove the '-->', add the 'error:' or whatever back in, and you should be good to go without sacrificing any of the (very welcome!) improvements from this change.
- steveklabnik 10y ago> Please, take those complaints from others seriously. We are absolutely taking it seriously. We do not want to regress on tooling for this, and in fact, plan on making it _better_ not worse.
- Ygg2 10y agoAs I u understand it, he wants errors to start with filename:line:col and not with error [E0080], for Emacs compatibility?
- dllthomas 10y agoPersonally I care about vim (and some scripts I have), but I do think emacs assumes errors of the same format. It's generally easy to work with, and output by a lot of things (including [git] grep -n). For my use, what I care about is that important locations that I might want to visit appear at the beginning of the line as either "filename:line:col: " or "filename:line: ". Other lines can begin with "error[E0080]" - that does no harm. If others have more particular needs, I hope they voice them. (nhaehnle seems to want severity following location?)