I'm using notmuch-mode from within Emacs to send email using isync/mbsync through Gmail. However, every time I send email from within Emacs, I get this error:
Debugger entered--Lisp error: (file-error "not a regular file" "/Users/peter/Dropbox/mail/gmail/sent")
insert-file-contents("/Users/peter/Dropbox/mail/gmail/sent" nil 0 100)
mail-file-babyl-p("/Users/peter/Dropbox/mail/gmail/sent")
message-output("/Users/peter/Dropbox/mail/gmail/sent")
message-do-fcc()
message-send()
send-message-without-bullets()
call-interactively(send-message-without-bullets nil nil)
command-execute(send-message-without-bullets)
Does anyone know how to fix this?
I can share relevant details from my .mbsyncrc if that would be helpful.
As answered on the notmuch mailing list, you need to use notmuch-mua-send rather than calling message-send directly.
Related
I was doing something in SLIME, and an error occurred. While trying to select the ABORT restart, I made a typo, and instead of the debugger closing, a new buffer named *slime-source* appeared. It contained a LAMBDA form with the expression I'd typed at the REPL, pretty-printed.
This is potentially useful, but I don't know how I did it. What did I type to make this buffer appear?
I'm having some issues getting company-rust to work the way it should. It loads fine initially, then dies with this error when I attempt to actually use it:
deferred error : (file-error "Searching for program" "no such file or directory" "racer")
The path is correct and I can use it in eshell. I'm on most-recent OSX, with the railwaycat/emacs-mac-port as emacs.
My init.el is here, and I'm not quite sure of what is causing it, and I'm kind of out of ideas.
(setq company-racer-executable "path/to/your/racer")
When using compose-mail to write a messages, and then using message-send-and-exit to send the message, I got a failure. In the messages buffer, I see:
Sending via mail...
sendmail-query-once: Symbol's function definition is void: nil
Running "version" gives: "GNU Emacs 24.3.1 (x86_64-pc-linux-gnu, GTK+ Version 3.10.7) of 2014-03-07 on lamiak, modified by Debian."
It seems like the variable send-mail-function has been set to nil for some reason. The function sendmail-query-once expects this variable to contain the name of a function that will send the message. Since nil is not a valid function, you get the error "Symbol's function definition is void: nil".
As a special case, if send-mail-function is set to sendmail-query-once, then you will be taken to a prompt for setting up sending email. Try setting it to that value, to go through the method selection again, and then the configuration will be saved automatically.
I am wrote the code with bugs.
Example:
(print (/ 1 0))
I am trying compile with C-c C-c.
And catch the error with stack frame.
I want see line in the code where an error occured. Clicked 'v' on line in stack frame and catched error.
Error: Cannot find source location for: #<COMPILED-CODE-LOCATION
(SB-C::VARARGS-ENTRY /)>
How can I go to the line in my code?
Screenshot:
As you can see from the error, the line you want to jump to, is somewhere in package SB-C, which is part of SBCL. If you don't have SBCL sources (you've installed a binary or deleted them), you should get them (relevant to your current SBCL version) and then link them up in .sbclrc like this (according to http://www.cliki.net/SLIME%20Features):
(setf (logical-pathname-translations "SYS")
'(("SYS:SRC;**;*.*.*" #P"/opt/sbcl/src/**/*.*")
("SYS:CONTRIB;**;*.*.*" #P"/opt/sbcl/contrib/**/*.*")))
Or just compile SBCL from source and it will know, where they are.
Do you have (proclaim '(optimize debug)) above that line somewhere? This function will ensure that your system has all the debugging data it can get.
I'm having a problem with an Emacs lisp package that I pulled down from the ubuntu distribution. The package is JDEE, and it complains of Args out of range: "63", 0, 4 in the mini buffer and the *Messages* buffer whenever I open a file. This bug appears to have been reported last September but no action has been taken. I'm not an emacs newbie, having written some Elisp code myself, but I've never attempted to debug anything like this. I would like to stop the file load in a debugger when this error happens to at least get an idea of where the problem is coming from. I've read section 18.1.1 of the Elisp manual on "Entering the debugger on error" but trying to load the file after playing with various combinations of values for debug-on-error, debug-ignored-errors, and debug-on-signal appears to have no effect. Has anybody got any suggestions for my next step?
If debug-on-error isn't working, I'd start with the source itself. Find the keybinding/event that is causing the problem, and locate the function.
C-h k <keystrokes>
M-x find-function <function-name-from-above>
Now, once you are at the source
M-x edebug-defun
And the next time you hit the key, you should be able to step through the program. At that point, you can see which portion causes an error - and drill down that way.
You can also try setting the variable 'stack-trace-on-error to see if you can find the culprit (though 'debug-on-error usually works for me, not sure why it doesn't for you).
As a last resort (if edebug-defun doesn't work), you can redefine the routine with a call to (debug) in it, sort of does the same.
I suppose JDEE is somehow inhibiting debug-on-error. Perhaps grep through its files for the error message "Args out of range". While debugging, make sure to load the uncompiled .el files, not the byte-compiled .elc files (you will notice it in the debugger if you are running byte-compiled code) by entering commands like (load "foo.el") instead of (load "foo").
I got the same error when using find-grep after accidentally redefining (current-time-string) in one of my own scripts.
Using the M-x edebug-defun tip posted above I managed to find the issue when I stepped through the code giving the error seeing the call to (current-time-string).
Not sure how helpful this is in your case.