elpaca VS zed

Elpaca [1] does not do this. I use it and it works a treat.

1: https://github.com/progfolio/elpaca

As others have said your packages work well and should still be widely supported. use-package has been blessed by the maintainers of emacs and will be a default package when Emacs 29 is released. If you are looking for another package manager /u/nv-elisp 's https://github.com/progfolio/elpaca would be a good one to checkout.

One of my biggest challenges with it is for packages that have extensions. Where they just work with Elpa/Melpa but then when you convert over to Elpaca they break and you have to go digging around Elpaca's manual and try to figure out the right file incantation that will make things works.

;; Example Elpaca configuration -*- lexical-binding: t; -*- (defvar elpaca-installer-version 0.3) (defvar elpaca-directory (expand-file-name "elpaca/" user-emacs-directory)) (defvar elpaca-builds-directory (expand-file-name "builds/" elpaca-directory)) (defvar elpaca-repos-directory (expand-file-name "repos/" elpaca-directory)) (defvar elpaca-order '(elpaca :repo "https://github.com/progfolio/elpaca.git" :ref nil :files (:defaults (:exclude "extensions")) :build (:not elpaca--activate-package))) (let* ((repo (expand-file-name "elpaca/" elpaca-repos-directory)) (build (expand-file-name "elpaca/" elpaca-builds-directory)) (order (cdr elpaca-order)) (default-directory repo)) (add-to-list 'load-path (if (file-exists-p build) build repo)) (unless (file-exists-p repo) (make-directory repo t) (condition-case-unless-debug err (if-let ((buffer (pop-to-buffer-same-window "*elpaca-bootstrap*")) ((zerop (call-process "git" nil buffer t "clone" (plist-get order :repo) repo))) ((zerop (call-process "git" nil buffer t "checkout" (or (plist-get order :ref) "--")))) (emacs (concat invocation-directory invocation-name)) ((zerop (call-process emacs nil buffer nil "-Q" "-L" "." "--batch" "--eval" "(byte-recompile-directory \".\" 0 'force)"))) ((require 'elpaca)) ((elpaca-generate-autoloads "elpaca" repo))) (kill-buffer buffer) (error "%s" (with-current-buffer buffer (buffer-string)))) ((error) (warn "%s" err) (delete-directory repo 'recursive)))) (unless (require 'elpaca-autoloads nil t) (require 'elpaca) (elpaca-generate-autoloads "elpaca" repo) (load "./elpaca-autoloads"))) (add-hook 'after-init-hook #'elpaca-process-queues) (elpaca `(,@elpaca-order)) ;; Install use-package support (elpaca elpaca-use-package ;; Enable :elpaca use-package keyword. (elpaca-use-package-mode) ;; Assume :elpaca t unless otherwise specified. (setq elpaca-use-package-by-default t)) ;; Block until current queue processed. (elpaca-wait) ;;Load your "./modes" files here (cl-loop for mode in (directory-files "./modes" 'full "\\.el$") (load-file mode)) ;; Local Variables: ;; no-byte-compile: t ;; no-native-compile: t ;; no-update-autoloads: t ;; End:

Elpaca. https://github.com/progfolio/elpaca - an alternative to the built in package manager. Very fast with an eminently decent UI, and allows for any or no fine-tuning how any given package should be installed.

Here's an overview of the current structure of Elpaca:

If you get around to actually measuring it, let me know. I'm collecting data points for comparison with Elpaca.

Elpaca has the elpaca-fetch command for this purpose. It fetches a package repository and will display the commit log. Each commit hash is a button which will open a magit diff view if magit is installed. It could very easily be extended to work with vc, ediff, etc. Here's a screenshot of what the update log looks like:

Zed is a new, open source, multiplayer code editor written in Rust. It was developed by the creators of Atom and Tree-sitter — Nathan Sobo, Antonio Scandurra, and Max Brunsfeld. The team launched Zed in early 2023 and later open sourced it in 2024.

There is an open issue about helix keybinds:

https://github.com/zed-industries/zed/issues/4642

Currently vim, but I’m very excited about Zed.

https://zed.dev/

The software engineering world has changed a lot, but it seems like both workers and companies haven't fully caught up yet. Recently, I've been having a lot of fun using Zed. It made programming enjoyable for me again, just like it was many years ago. Some people think Zed is just another unfinished editor, but that's not right. Zed is an AI tool. If you're not using Zed with GitHub Copilot and OpenAI GPT, you're not using it correctly, and you likely don't need Zed at all.

I don't mean to reply-guy this thread, but it builds on Windows (and Linux)

https://github.com/zed-industries/zed/blob/main/docs/src/dev...

You can try it out by downloading it from here https://zed.dev/

Now, fast forward to last year's Rails World conference that I was a lucky attendee of. What a breeze of fresh air! Among the many many inspiring people, talks and presentations, I noticed one thing: most people use VS Code, some use Vim but – more importantly – a lot of people tweak their editor / IDE almost as routinely as they tweak the code they work on professionally! And I thought: I want that too, how come I've lost this mindset here? I’ve taken for granted that I can tweak every imaginable aspect of my Linux OS as well as the Gnome environment so why not my IDE – the program that I literary spend most hours a day in? That was the final nudge for me to try to switch to something – anything really – that would be feasible for me to tweak and that’s how I ended up in VS Code. I’m not saying this will be my final IDE destination (looking at you Zed, Fleet or perhaps even Vim) but I know I want to stay closer to where a more active developer community around the editor is.

The GitHub issue #4424 for Zed relates to the lack of a feature for using local large language models (LLMs). In response to this, I proposed a workaround that enables the integration of local LLMs into Zed. This solution addresses the need for a non-proprietary, offline alternative to mainstream models like ChatGPT, potentially increasing privacy and control for users.

To integrate a custom model in Zed, I bypassed the limitation of only using OpenAI models. I did this by running the Mistral model from the Ollama library and cloning it to appear as "gpt-4-1106-preview." The steps included pulling and running the Mistral model, then using Ollama's commands to clone it. I updated Zed's settings to point to the local API URL of the cloned model. Restarting Zed applied these changes, enabling the use of the local LLM within Zed's environment.

For more details, you can refer to the GitHub issue directly: https://github.com/zed-industries/zed/issues/4424#issuecomme...