4 ms·

Emacs has a lot of amazing extensions! Magit is unparalleled for working with Git. The problem is that they break more frequently, in my experience. The very fa

by jolux 6y ago

Emacs has a lot of amazing extensions! Magit is unparalleled for working with Git. The problem is that they break more frequently, in my experience. The very fact that I have to install a 3rd-party DSL to have a sane package management experience is beyond the pale from a usability perspective.

clircle 6y ago
Thank you for this thoughtful comment. I assume you are talking about use-package? I've been using it for several years. There is a long standing effort to have it merged into emacs/elpa, so we hope the situation will improve. https://github.com/jwiegley/use-package/issues/282 https://github.com/jwiegley/use-package/issues/282
- jolux 6y ago
  Yes, I think it should be merged. Although the fact that this has been open since 2015 also highlights how the copyright assignment requirement slows down the pace of development.
  - anaerobicover 6y ago
    Honestly, it's kept me from contributing to packages, too. I have no problem with the outcome, my patch being "owned" by the project -- that would be my intention by contributing. I just have a strong dislike of bureaucracy, form-filling, and being "on file" somewhere.
jamienicol 6y ago
Clunky interface aside (a given with emacs), what's wrong with package-list-packages and customize? It's essentially no different to installing and configuring packages in vscode. Why do you think use-package is necessary?
- legends2k 6y ago
  Tying configurations and customizations to a package, inter-package configurations, etc. are taken care by use-package. Disable a package, its related configuration is also cleanly disabled.
- TeMPOraL 6y ago
  use-package + eschewing customize makes it easier to manage your Emacs configuration as code, and keep it synced across Emacs installations on different machines. Otherwise, package-list-packages and customize are awesome. The interface isn't even that clunky, and it's more powerful than equivalent interfaces in other software. Particularly customize, I'm very impressed by how it works.

by jolux 6y ago

clircle 6y ago

Thank you for this thoughtful comment. I assume you are talking about use-package? I've been using it for several years. There is a long standing effort to have it merged into emacs/elpa, so we hope the situation will improve. https://github.com/jwiegley/use-package/issues/282 https://github.com/jwiegley/use-package/issues/282

jolux 6y ago
Yes, I think it should be merged. Although the fact that this has been open since 2015 also highlights how the copyright assignment requirement slows down the pace of development.
- anaerobicover 6y ago
  Honestly, it's kept me from contributing to packages, too. I have no problem with the outcome, my patch being "owned" by the project -- that would be my intention by contributing. I just have a strong dislike of bureaucracy, form-filling, and being "on file" somewhere.

jamienicol 6y ago

Clunky interface aside (a given with emacs), what's wrong with package-list-packages and customize? It's essentially no different to installing and configuring packages in vscode. Why do you think use-package is necessary?

legends2k 6y ago
Tying configurations and customizations to a package, inter-package configurations, etc. are taken care by use-package. Disable a package, its related configuration is also cleanly disabled.
TeMPOraL 6y ago
use-package + eschewing customize makes it easier to manage your Emacs configuration as code, and keep it synced across Emacs installations on different machines. Otherwise, package-list-packages and customize are awesome. The interface isn't even that clunky, and it's more powerful than equivalent interfaces in other software. Particularly customize, I'm very impressed by how it works.