Need help with debugging. Emacs error reporting is still too weak in 2026.I just lost time debuggin…
انتشار: 2026/08/02 07:07 UTCدریافت: 2026/08/05 17:32 UTCآخرین مشاهده: 2026/08/05 17:32 UTC
Need help with debugging. Emacs error reporting is still too weak in 2026.I just lost time debugging something that should have been obvious.Emacs refused to load my init.el with this message: load-with-code-conversion: Symbol’s function definition is void: defmacro*That’s it. No useful file. No clear line. No real context.Important detail: I always launch Emacs with `--debug-init`. It’s in my bash aliases. Every single time. I also have `debug-on-error t` in my init.el.The error occurred while scraping/compiling loaddefs. It blamed `f/bin/docs.el`, but the actual culprit was an old vendored `ert.el` sitting in `s/dev/` that still contained `defmacro*` and had been pulled into the autoloads file. The error message (even with --debug-init) gave me almost zero help finding that.This isn’t a minor warning. This completely prevented Emacs from loading my init.el. My entire environment was down.Hitting a void function during loaddefs/byte-compilation should produce something a lot more helpful, for example:- Which file actually contained the defmacro*- That it came from autoloads or a dependency- That defmacro* is an obsolete cl macro- A clearer, more actionable backtrace by defaultRight now the signal-to-noise ratio on this class of error is bad. For experienced users it’s annoying. For newcomers it’s actively hostile, they see a cryptic void-function error, their config won’t load, and they have no idea where to start.I don’t expect miracles, but basic “where did this undefined function actually come from” information during init/loaddefs failures would be a lot more helpful.Maybe I’m missing something, a variable, a package, or some setting that would provide more useful information in these cases? Anybody?redd.it/1vd8iyt@r_emacs
تاریخچه بازدید مشاهدهشده
حدود 0 بازدید تازه در ساعت در این نمونهپستهای تلگرام — /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