Skip to content

[WIP] Refactor Emacs configuration to follow 2024 best practices#3

Draft
Copilot wants to merge 1 commit intomasterfrom
copilot/refactor-emacs-config-2024
Draft

[WIP] Refactor Emacs configuration to follow 2024 best practices#3
Copilot wants to merge 1 commit intomasterfrom
copilot/refactor-emacs-config-2024

Conversation

Copy link
Contributor

Copilot AI commented Jan 17, 2026

Thanks for asking me to work on this. I will get started on it and keep this PR's description up to date as I form a plan and make progress.

Original prompt

Act as an Emacs Lisp expert specializing in modern Emacs (version 29+). Refactor the attached configuration to follow 2024+ best practices:
Native use-package: Replace any manual require or install logic with the built-in use-package macro. Use :vc for packages that need to be fetched from source.
Built-in Alternatives: Identify third-party packages that can be replaced by built-in libraries (e.g., replace projectile with project.el, ivy/helm with vertico/marginalia, or flycheck with flymake) unless I have specific custom logic for them.
Byte-Compilation & Startup: Ensure all use-package blocks use :defer t or appropriate autoloads to keep startup fast. Move GUI-specific settings (tool-bars, menu-bars) to early-init.el logic.
Modern UI: Enable pixel-scroll-precision-mode and ensure display-line-numbers-mode is used instead of the older linum-mode.
Clean Syntax: Use setopt instead of setq for user-customizable variables where appropriate (available in Emacs 29+).


✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

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

Successfully merging this pull request may close these issues.

2 participants