reddit / emacs

Need help to debug a lisp error

Danrobi1 · 2022-07-26 03:34
I do not have any coding knowledge. I'd like some help to learn how to pin point the issue in a backtrace debugger buffer. I got this weird bug now and I cant find what's wrong. Or may be there's other debugger packages available for Emacs that would be more specific about what's wrong in my init file that is causing this issue? When I'm running 'C-g' on 'M-x' I get this backtrace now. That's new. The problem here is that I've added a few stuff in my init file since before running 'C-g' on 'M-x'. There's no way now that I can recall what could be causing the issue. I definitely need to find what's causing this from a degugger. Here's the [backtrace](https://codeberg.org/danrobi/dotfiles/issues/1). I've tried to look for something related with 'minibuffer-quit' in my init file. There's nothing with 'minibuffer-quit' anywhere in my init file. Here's my [init file](https://codeberg.org/danrobi/dotfiles/src/branch/main/emacs/init.el) Thank's for any help.
tektektektektek · 2022-07-26 03:50
I suggest you scatter logging throughout your `.emacs` file, e.g.: ;------------------------------------------------------------------------------ ; Set message log parameters ; (setq message-log-max 1000) (message ":File _emacs") That should go into your `Messages` buffer which you can switch to after your `.emacs` file bombs. Put log messages throughout your `.emacs` file and you'll be able to narrow down _where_ the issue is occurring.
Danrobi1 · 2022-07-26 04:15
Well, Thank's for the help anyway. debug-on-quit is a variable defined in ‘C source code’. Its value is nil Non-nil means enter debugger if quit is signaled (C-g, for example). I added set to 't'. F me!