Nicholas Vollmer
Nicholas Vollmer
> Just bike shedding, but do you have any other suggestions for a better mode name? Perhaps exwm-client-mode for the global minor mode?
> exwm-mode as is and only introduce the new exwm-wm-mode. Personally, I'm not a fan of the name "exwm-wm-mode". The only thing I could think of was "exwm-client-mode", but I'm...
> I consider `exwm-client-mode` misleading, not meaningful enough. What about `exwm-manager-mode` or `exwm-desktop-mode`? I still find `exwm-wm-mode` best, since that's what it is, a mode controlling the window manager. Fair...
> @progfolio, thank you again, that will be helpful. I defined some labels in @ch11ng:exwm, are you able to label issues over there? If so I can add more labels...
From a quick glance it seems like many of the calls to `exwm--log` are inserted as the first form in a function and do not make use of any arguments....
> Some packages like yaml.el sligthly exceed the default `max-lisp-eval-depth` > value of 1600, yielding an "Eager macro-expansion failure". Unable to reproduce the issue on my end. Do you see...
FYI: I'm working on a refactor which addresses this as well as some other design issues. The [feat/refactor ](https://github.com/progfolio/elpaca/tree/feat/refactor) branch contains the `elpaca-with-emacs` macro which can modify the `elpaca-with-emacs-env-form` to...
@raxod502 In light of the commit message: > (These are the only two recipes that require that a file is renamed.) Do we think it's worth implementing translation for the...
`elpaca-fetch` `elpaca` should default to a commit log. I suggest pairing that with `elpaca-log-update-mode` for all packages. Some of the commit changes offer more technical details than would be found...
The above assessment looks sound to me. I don't use this package, so I don't have a strong implementation preference. Another solution is to add optional args to the setup...