Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[feature request] Print line in code for lints and diagnostics #34

Open
appetrosyan opened this issue Jan 22, 2024 · 0 comments
Open

[feature request] Print line in code for lints and diagnostics #34

appetrosyan opened this issue Jan 22, 2024 · 0 comments

Comments

@appetrosyan
Copy link

Currently melpazoid provides feedback with little granularity, and only up to the offending section.

For example,

- The `;;; Commentary` for this file is much wider than 80 characters

I instead propose the format that states:

- lines [38--40] are wider than 80 characters

Or better yet,

- line 38 is 90 characters, should be less than 80. 
- line 39 is 92 characters, should be less than 80.

This format collaborates with the potential submitter by pointing them to the offending line, as is common with most modern tools/programming languages.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant