Closed conao3 closed 3 years ago
And the dependency of bind-key
is also something wrong.
The bind-key
is for the user, not the package.
As proof, this exwm-x
is the only package that depends on bind-key
except for use-package related packages. (see MELPA bind-key page)
This is because packages can create minor modes and set shortcuts to take precedence over other major/minor modes.
This will ensure that key bindings are successfully released when exwmx-mode
is turned off (if defined).
I do not think so :-)
the problem should be solved
Thanks, great.
Hi!
Currently, the dependencies of this package (exwm-x) include things that are unnecessary for the user, and the modularity of the package is impaired. For example, users have their own favorite packages for switch-window and ivy dependencies, and relying on unnecessary packages will cause users to install useless packages. I'm using
ivy
so no problem, buthelm
users won't want to installivy
. I also useace-window
instead ofswitch-window
, soswitch-window
is not necessary.Bundled sample configuration examples will be welcomed, but we don't think you will be asked to install the suite. If @purcell has any additional comments about the general MELPA packaging strategy, please comment. (maybe divide the package as
exwm-x
andexwm-x-ivy
for ivy integration code)