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:
If we put this into IELM, let's see what we get:
ELISP> '("melpa", "http://melpa.org/packages/")
Is there a way to get a pretty-printed backtrace buffer?
There is, but you'll have to wait for Emacs 27 to be released or get a build of it in the meantime. Quoth its etc/NEWS file:
* Changes in Specialized Modes and Packages in Emacs 27.1
*** The Lisp Debugger is now based on 'backtrace-mode'.
Backtrace mode adds fontification and commands ...
You have an extra right paren, ), somewhere in your init file. Here's one way to find it:
Start Emacs using emacs -Q (no init file).
Visit this file - the one that Emacs was trying to load when it barfed:
C-x C-f /Users/user/.emacs
Comment out 1/2 of that file (roughly), using M-x comment-region.
Do M-x eval-buffer.
If you get an error, then comment out ...
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 ...
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 "...
The function which produces that warning is magit--magit-popup-warning.
You can use M-x debug-on-entry RET magit--magit-popup-warning RET to discover what is causing it to be called.
See C-hig (elisp)Debugger Commands for what you can do from inside the debugger, and how to exit it.
Use M-x cancel-debug-on-entry if you don't want that to happen any more.
Load the source file (*.el, not *.elc) that defines the function you're interested in. E.g., M-x load-file or M-x load-library (but be sure to specify .el).
Then use M-x debug-on-entry, to enter the debugger when that function is called. Step through the debugger with d (or c to skip through a step you're not interested in). Use e to evaluate any sexp (e.g. ...
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)
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 (...
I have a solution that worked for me, after some trial and error. Please bear with me as this is my first time answering a question on StackExchange.
I also had Org agenda break with the error message Symbol's value as variable is void: org-tag-group-re. For me, this occurred while trying to install org-drill.
For context, I'm running Emacs 26.3 on MacOS ...
This took me forever to figure out, but it turns out Spacemacs had cached a bunch of environment variables. One in particular, $XAUTHORITY, was making it so that qutebrowser wouldn't start. Manually editing my spacemacs env file and updating that variable fixed the problem.
I think you need to access the property values that narrow to region needs.
(defun outer-paren ()
"Move point to the outermost parenthesis."
(defun func ()
(let ((start (outer-paren))
You are trying to use the values returned by functions outer-paren and sp-forward-sexp, instead of the positions they move to.
The error message tells you that narrow-to-region expects buffer positions - numbers or markers. So clearly your values of start and end aren't such. They aren't numbers or markers because functions outer-paren and sp-forward-sexp ...
Emacs 27: C-hig (elisp)Backtraces
Debugger mode is derived from Backtrace mode, which is also used to show
backtraces by Edebug and ERT. (*note Edebug::, and *note the ERT manual:
The backtrace buffer shows you the functions that are executing and
their argument values. When a backtrace buffer is created, it ...
After some more googling, I think I found the answer to my own question. The following code works:
(setq auto-mode-alist ())
The list auto-mode-alist seems to be a hash that has file extensions as keys and major modes as values: https://www.emacswiki.org/emacs/AutoModeAlist
If you are using messages to yourself while developing then:
That's fine - nothing wrong with using message.
You can also define a wrapper for such uses of message, which respects a global variable you define. That gives you a quick way to turn such messages on/off or otherwise affect them.
An alternative is to use debug, to use the Emacs debugger:
The current name for the highest priority value is org-highest-priority instead of org-priority-highest. They changed the names in January 2020 in this commit. An alias was added for the old name, but there was a bug in the way it was done.
This bug appears to be in 9.3.6 and fixed in 9.3.7. Try updating your org-mode.
It's possible to format backtraces differently using mapbacktrace with a custom function. One such example is always printing the items as list, I've contributed a patch introducing the debugger-stack-frame-as-list customizable that does that. Check out the implementation of backtrace in Emacs 26.1 or newer.
It seems that you need to give a non-nil value to variable grep-find-template. So customize that user option or bind it around your (rgrep "test" "*.org" "~/Org/wiki") or call (grep-compute-defaults) before evaluating calling rgrep.
I found this out by looking at the backtrace. The first argument passed to grep-expand-template is nil. rgrep-default-...
Looks like its just a bug in RTags (at least when installed through Emacs). The package I had the problem with was installed from melpa-stable, and was Rtags 2.38. I tried installing a version 20200221.38 from melpa instead, and it seems to work now.
I don't know a solution yet, but I can explain a little bit. Your back-trace tells us, that the message call happens in tramp-sh-handle-vc-registered. And indeed, its body is wrapped by
(with-temp-message "" ...)
This is done in order to preserve the recent message in the echo area while running tramp-sh-handle-vc-registered, which has an own progress ...
Let's have a look at
(when (and awesome-tab-display-icon
(ignore-errors (require 'all-the-icons)))
when is a macro defined in subr.el:
(defmacro when (cond &rest body)
"If COND yields non-nil, do BODY, else return nil.
When COND yields non-nil, eval BODY forms sequentially and return
value of last one, or nil if there are none.
It turns out that one of the blogspot blogs on my list, which I'd followed for a while previously, had started to require password authentication (and I didn't know the password). Some result of caching was that it was breaking the whole system. Here was the solution:
Remove the offending blog from newsticker-url-list (which I defined via customize, in my ...
When saving the desktop file, emacs used to also save which font-backend is being used by the various frames it has open. Emacs-26 on GNU/Linux by default uses the xft backend, whilst emacs-27 can use the ftcr (Cairo) backend, so that's what it saves in the desktop file. That wouldn't normally be a problem, except that until recently, emacs would crash if ...
I made this work by passing argument when launching gdb.
M-x gdb RET gdb -i=mi -ex "target extended-remote <remote>:44421" -ex "set remote exec-file ./executable" --args "-c config.xml"
Then in gdb launched i also had to set set non-stop off.
I ran gdbserver as gdbserver --multi :44421 in the folder on remote where executable was.
It worked. But ...