-
Notifications
You must be signed in to change notification settings - Fork 10
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
Add package-lint target #134
Conversation
Run this command |
Ok, I see what you mean. Maybe Melpa is meant for simpler packages :-). More incentive to finish the release.
…-- Bob
On Dec 13, 2021, at 4:34 PM, Mats Lidell ***@***.***> wrote:
Run this command
> make package-lint 2>&1 | grep -v \"hyperbole\" | tee package-lint.txt
Grep it for removing all errors complaining about functions not having the package prefix "hyperbole". Around 2034 lines that is. 😄
The rest goes into the file below:
package-lint.txt
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
For this check the major difference we have is that we don't have a package unique prefix for all our files and functions. |
Yes, thinking about how we could break it into multiple packages, but definitely after V8 release.
…-- Bob
On Dec 14, 2021, at 2:21 AM, Mats Lidell ***@***.***> wrote:
For this check the major difference we have is that we don't have a package unique prefix for all our files and functions. hypb comes first to my mind in that respect. Would be a major undertake to fix that of course. Maybe also points in the direction of having multiple packages like, hypb for the hyperbole core, hypb-kotl for kotl-mode and possibly others depending on how you would want to slice and dice it. Anyway - think about it.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
d9baef1
to
d151ff8
Compare
This is a new run of package-lint with filtered out all the warning|errors about files and functions not having the proper prefix and that should not be used to separate prefix from rest of function|variables|symbols. That is above 3000 lines of error messages. What remains are: Some of these looks like easy fixes. I might attempt to fix some of them. |
Github mobile won’t open your link. Try changing it to a .org file and I’ll see if that works. Thanks. I am flying today, so just on my phone.
…-- Bob
On Jun 14, 2022, at 12:09 PM, Mats Lidell ***@***.***> wrote:
This is a new run of package-lint with filtered out all the warning|errors about files and functions not having the proper prefix and that should not be used to separate prefix from rest of function|variables|symbols.
That is above 3000 lines of error messages. What remains are:
package-lint-2.txt
Some of these looks like easy fixes. I might attempt to fix some of them.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.
|
*.org is not a known type. Trying with pdf!? |
Same problem. I’ll just look at it later on a computer. Thanks.
…-- Bob
On Jun 14, 2022, at 3:11 PM, Mats Lidell ***@***.***> wrote:
*.org is not a known type. Trying with pdf!?
output.pdf
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.
|
What
This is a setup to run package-lint on Hyperbole.
Why
I wanted to see what challenges we have if we would like to make Hyperbole package-lint clean. Provided here to share it and show the setup. Including example of running it.
Not intended to be merged at this point.