Fixing a flycheck + straight.el + package.el issueI've been tinkering with my config lately, which…
انتشار: 2026/08/14 15:07 UTCدریافت: 2026/08/16 09:30 UTCآخرین مشاهده: 2026/08/16 09:30 UTC
Fixing a flycheck + straight.el + package.el issueI've been tinkering with my config lately, which has me running Emacs directly rather than firing up a server and client. Because of this, I noticed the following warning:>⛔ Warning (straight): package.el was loaded when straight.el was already loaded. You may wish to delete ~/.emacs.d/elpa or add (setq package-enable-at-startup nil) to ~/.emacs.d/early-init.el to avoid multiple versions of the same packages being loaded.I don't want to have to deal with mysterious package version mismatch issues down the road, so I decided to try and fix it. Obvious way to start was by deleting ~/.emacs.d/elpa/ and adding (setq package-enable-at-startup nil) to my ~/.emacs.d/early-init.el, and this seemed to work, at first. A little while later I made some changes to one of my personal packages and reloaded, and the warning came back.This led to some grueling trial and error. I was able to pin it down to Emacs lisp files, specifically ones that don't belong to Emacs (such as init.el or early-init.el). I went through the minor modes I use in emacs-lisp-mode one by one, and was able to highlight flycheck as the issue.Actually solving the issue was interesting. Flycheck apparently fires background Emacs processes using -Q --batch to do its checking which makes a lot of sense for performance and such, but it also calls (package-initialize) to install any packages referenced by whatever you're working on. This happens out-of-band of your current Emacs instance, and in that separate Emacs instance none of your normal initialization code gets run. The arguments it passes to those instances are set in a constant flycheck-emacs-args, and I wouldn't want to alter those to use my config (or any part of it really) since that would likely bog things down.What I ended up having to do was inject some code into flycheck-emacs-lisp-check-form at the very beginning of the (progn ...) it contains: (with-eval-after-load 'flycheck ;; flycheck-emacs-lisp-check-form is stored in a string, so we have to ;; parse it to a list before operating on it (let ((form (read flycheck-emacs-lisp-check-form))) ;; inject an override setting package-user-dir to the temporary ;; directory so when the flychecker initializes packages they don't get ;; written to ~/.emacs.d/elpa/, which causes startup warnings (setcdr form (cons '(setq package-user-dir (expand-file-name "flycheck-elpa" temporary-file-directory)) (cdr form))) (setq flycheck-emacs-lisp-check-form (prin1-to-string form))))This moves package-user-dir for those instances to a temporary directory, so they can do what they need to do without interfering with normal Emacs usage and operation.redd.it/1vo7jns@r_emacs
پستهای تلگرام — /r/emacs
Org-draw: Drawing inside org-mode using tl;drawyoutu.be/04zbf-tosNQhttps://redd.it/1vpon…
Magit Ricing?preview.redd.it/t1owu3yvkmjh1.png?width=9… really starting to like Magit from a functionality standpoint, but I hate to say it—it’s ugly. It’s probably the better choice for me practically, especially since I’m already using Emacs, but I really like the way Lazygit looks and feels.What I especially like about Lazygit is the panel-based layout. Files, branches, commits, diffs, etc. are visually separated into their own areas, which makes the interface feel much cleaner and easier to scan than having everything in one continuous buffer.Has anyone riced or customized Magit to get closer to that kind of look? I’m not necessarily trying to recreate Lazygit exactly, but I’d love stronger visual separation between sections and more of that clean, organized panel/dashboard feel.redd.it/1vphmxv@r_emacs
A Tour of Magit's Status InterfaceI just wrote a post about Magit's status screen, focusing on why it's powerful rather than just saying it is, I've always found the "why" gets asserted more than explained. It's written to be approachable for non-Emacs folks. Planning follow-ups on staging/committing and cherry-pick/rebase.For those who have been using Git CLI, what workflow did Magit make so painless you now take it for granted?heiwiper.com/posts/magit-status-tour/http…
Has anyone gotten org-display-remote-inline-images to work ?Found a post that says org-display-remote-inline-images only functional for TRAMP paths. Is this accurate ? I tried both 'cache and 'download options still getting "No images to display inline" Tried both with and without double brackets. (Local images work fine)emacs: 30.2 org mode : 9.7.11redd.it/1vpcccc@r_emacs
Gptel new interaction interface ?youtu.be/T9HSTSm7i5Mhttps://redd.it/1voxx…
Capture dotfiles using org-captureSince I discovered org mode, I always was balancing between using symlinks and org babel tangle to manage my configuration. Now I'm in point that work related items are org babel managed and system level config is symlinked, because, often tools write back to their files. Another reason why I did not go full on babel was that I don't like workflow:1. found file that requires backup2. copy file3. paste in to org mode4. fill all details5. tangle.But yesterday I was visited by GNU spirit and she gave mi this org-capture template that reduces adding new file to backup to C-c k (my capture prefix) b (backup) and then tangle that file to original place: * [[%(project-root (project-current))]] [[%(abbreviate-file-name (org-capture-get :original-file))][%(file-relative-name (org-capture-get :original-file) (project-root (project-current)))]] - repository :: [[%(project-root (project-current))]] - file :: [[%(abbreviate-file-name (org-capture-get :original-file))][%(file-relative-name (org-capture-get :original-file) (project-root (project-current)))]] #+header: :tangle %(abbreviate-file-name (org-capture-get :original-file)) #+begin_src %^{Language|shell|elixir|nix|python|elisp|fundamental|eshell|conf} %(with-temp-buffer (insert-file-contents (org-capture-get :original-file)) (buffer-string)) #+end_srcI cannot comprehend how simple it is and how I never realized I could do this. Two think I think would be nice in future: \- if only it can automatically group those captures by project, but thinking of creating project backup capture template and simply refile from capture buffer \- automatic detangle so I can get back changes written by tools to their files, but not all of them support comments and many of them don't patch but dump state to file, so probably unsolvable using build in tools, only by elisp scriptingI'm trying to avoid longer elisp scripting for now 😄 What do you think?redd.it/1vowo7f@r_emacs