New answers tagged

2

The error seems to be saying that ((\, "http://melpa.org/packages/")) doesn't match the regex "\`https?:" Let's look at that value, the one being added to package-archives: '("melpa", "https://melpa.org/packages") If we put this into IELM, let's see what we get: ELISP> '("melpa", "https://melpa.org/packages") ("melpa" (\, "https://melpa.org/packages")...


2

The function edebug-instrument-for-tracing as defined in the following Elisp snippet works similar to edebug-defun. But, instead of instrumenting stuff for edebug it prepares it for tracing into the buffer *edebug-trace*. (defun edebug-untrace (form) "Remove tracing instructions from FORM." (if (consp form) (if (eq (car form) 'edebug-tracing) ...


1

I don't know anything like that, but if you want to see the calls (including parameters and return value) for a few specific functions you can use the trace-function command. Here's its docstring: (trace-function FUNCTION &optional BUFFER CONTEXT) Trace calls to function FUNCTION. With a prefix argument, also prompt for the trace buffer (...


3

The Elisp debugger doesn't provide a trace, but it does let you investigate (and even affect) the evaluation of Lisp code on the fly. You can enter the debugger, to walk or skip through any function, using M-x debug-on-entry. You can put breakpoints, which enter the debugger, at any place in Lisp source code, just by adding (debug). (See C-h f debug for ...


4

In your mode line, [...] suggests you have an existing backtrace is running, you need to quit this one in order to trigger a new backtrace, you can do this by C-x b *Backtrace* and q. If there is something in the mode line you don't understand, you can use mouse hover to see the tooltip. For example, if you hover [ or ], it will say something like "...


1

It seems it's intended: helm-internal calls helm-log-save-maybe calls (setq helm-debug nil) thus whenever a helm session ends, helm-debug will be reset to nil. I guess it's because the log buffer can grow too quickly. Instead of changing helm-debug directly, according to helm's own help (you can get it by type C-h m within any helm session, I have ...


0

Aha! This has been making me crazy for a long time. Today I spent some more time searching and exploring. I stumbled on the answer after doing ^H-m when in the minibuffer. The fourth keybinding listed is "q", quit-window. Typing q when completions are displayed closes the completion buffer and returns to the minibuffer, where ^G aborts normally. I don't ...


Top 50 recent answers are included