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

; Create melpazoid workflow #9

Closed
wants to merge 1 commit into from
Closed

; Create melpazoid workflow #9

wants to merge 1 commit into from

Conversation

Stebalien
Copy link
Contributor

EXWM is on ELPA, not MELPA, but melpazoid is still useful for running some basic linter checks.

See https://github.com/riscy/melpazoid.

EXWM is on ELPA, not MELPA, but melpazoid is still useful for running
some basic linter checks.

See https://github.com/riscy/melpazoid.
@Stebalien
Copy link
Contributor Author

Well, at this point, this PR is a bit aspirational.

@minad
Copy link
Member

minad commented Jan 15, 2024

Instead of melpazoid I'd prefer Purcell's emacs builds, which allows us to test or at least byte compile on various versions. (The melpazoid reviews annoy me a bit tbh.)

@minad
Copy link
Member

minad commented Jan 15, 2024

After having looked at the failed tests, I don't think we should use Melpazoid here, at least not for now. Both Exwm and Xelb are written quite coherently and respect namespaces, but do not follow the naming conventions.

@Stebalien
Copy link
Contributor Author

Yeah, fair enough.

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

Successfully merging this pull request may close these issues.

2 participants