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

Having Emacs plugins as a use case is pointless #45

Open
AlexKurisu opened this issue Dec 8, 2023 · 3 comments
Open

Having Emacs plugins as a use case is pointless #45

AlexKurisu opened this issue Dec 8, 2023 · 3 comments

Comments

@AlexKurisu
Copy link

AlexKurisu commented Dec 8, 2023

In my opinion, having Emacs plugins as a use case is pointless since Emacs already has a well-established format for that purpose and also has GNU ELPA, NonGNU ELPA and MELPA. Why would anyone make a switch?

@AlexKurisu AlexKurisu changed the title Having Emacs plugins as a use case is useless Having Emacs plugins as a use case is pointless Dec 8, 2023
@AlexKurisu
Copy link
Author

AlexKurisu commented Dec 8, 2023

Also, decentralized approach wouldn't work in Emacs anyways because its package-install relies on centralized package source.

@justinmk
Copy link
Member

justinmk commented Dec 8, 2023

In practice emacs won't change anything, but there is no technical reason why it is any different. Emacs packages are just source trees.

btw, where is it documented how emacs packages declare their dependencies? I found this, but it doesn't give any specifics: https://www.gnu.org/software/emacs/manual/html_node/elisp/Packaging-Basics.html

@AlexKurisu
Copy link
Author

AlexKurisu commented Dec 8, 2023

@justinmk In sources dependencies (and other stuff) are defined as shown in https://www.gnu.org/software/emacs/manual/html_node/elisp/Library-Headers.html. In actual distributed packages they are defined as shown in https://www.gnu.org/software/emacs/manual/html_node/elisp/Multi_002dfile-Packages.html with some well-known extensions, such as using :commit for build commit, :url for project url, :authors for authors, :keywords for keywords… You probably get the idea. Like

(define-package "company-auctex" "20200529.1835" "Company-mode auto-completion for AUCTeX"
  '((yasnippet "0.8.0")
    (company "0.8.0")
    (auctex "11.87"))
  :commit "9400a2ec7459dde8cbf1a5d50dfee4e300ed7e18" :authors
  '(("Christopher Monsanto <[email protected]>, Alexey Romanov" . "[email protected]"))
  :maintainers
  '(("Christopher Monsanto <[email protected]>, Alexey Romanov" . "[email protected]"))
  :maintainer
  '("Christopher Monsanto <[email protected]>, Alexey Romanov" . "[email protected]")
  :url "https://github.com/alexeyr/company-auctex/")

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

No branches or pull requests

2 participants