Oh, sorry. The RET means type return not something you actually type.
-Ivan
> On May 15, 2015, at 8:56 AM, Zach Elgood <zachelg...@gmail.com> wrote:
>
> When attempting the first command, I get the following:
> Debugger entered--Lisp error: (error "Trailing garbage following expression")
> read-from-minibuffer("Eval: " nil (keymap (9 . completion-at-point) (27
> keymap (9 . lisp-complete-symbol)) keymap (18 . helm-minibuffer-history)
> (menu-bar keymap (minibuf "Minibuf" keymap (previous menu-item "Previous
> History Item" previous-history-element :help "Put previous minibuffer history
> element in the minibuffer") (next menu-item "Next History Item"
> next-history-element :help "Put next minibuffer history element in the
> minibuffer") (isearch-backward menu-item "Isearch History Backward"
> isearch-backward :help "Incrementally search minibuffer history backward")
> (isearch-forward menu-item "Isearch History Forward" isearch-forward :help
> "Incrementally search minibuffer history forward") (return menu-item "Enter"
> exit-minibuffer :key-sequence "
> " :help "Terminate input and exit minibuffer") (quit menu-item "Quit"
> abort-recursive-edit :help "Abort input and exit minibuffer") "Minibuf")) (10
> . exit-minibuffer) (13 . exit-minibuffer) (7 . minibuffer-keyboard-quit)
> (C-tab . file-cache-minibuffer-complete) (9 . self-insert-command) (XF86Back
> . previous-history-element) (up . previous-history-element) (prior .
> previous-history-element) (XF86Forward . next-history-element) (down .
> next-history-element) (next . next-history-element) (27 keymap (114 .
> previous-matching-history-element) (115 . next-matching-history-element) (112
> . previous-history-element) (110 . next-history-element))) t
> read-expression-history)
> (let ((minibuffer-completing-symbol t)) (read-from-minibuffer "Eval: " nil
> read-expression-map t (quote read-expression-history)))
> (list (let ((minibuffer-completing-symbol t)) (read-from-minibuffer "Eval:
> " nil read-expression-map t (quote read-expression-history)))
> current-prefix-arg)
> ad-Orig-call-interactively(eval-expression nil nil)
> call-interactively(eval-expression nil nil)
>
>
> Similarly, the second one yields
>
> Debugger entered--Lisp error: (error "Trailing garbage following expression")
> read-from-minibuffer("Eval: " nil (keymap (9 . completion-at-point) (27
> keymap (9 . lisp-complete-symbol)) keymap (18 . helm-minibuffer-history)
> (menu-bar keymap (minibuf "Minibuf" keymap (previous menu-item "Previous
> History Item" previous-history-element :help "Put previous minibuffer history
> element in the minibuffer") (next menu-item "Next History Item"
> next-history-element :help "Put next minibuffer history element in the
> minibuffer") (isearch-backward menu-item "Isearch History Backward"
> isearch-backward :help "Incrementally search minibuffer history backward")
> (isearch-forward menu-item "Isearch History Forward" isearch-forward :help
> "Incrementally search minibuffer history forward") (return menu-item "Enter"
> exit-minibuffer :key-sequence "
> " :help "Terminate input and exit minibuffer") (quit menu-item "Quit"
> abort-recursive-edit :help "Abort input and exit minibuffer") "Minibuf")) (10
> . exit-minibuffer) (13 . exit-minibuffer) (7 . minibuffer-keyboard-quit)
> (C-tab . file-cache-minibuffer-complete) (9 . self-insert-command) (XF86Back
> . previous-history-element) (up . previous-history-element) (prior .
> previous-history-element) (XF86Forward . next-history-element) (down .
> next-history-element) (next . next-history-element) (27 keymap (114 .
> previous-matching-history-element) (115 . next-matching-history-element) (112
> . previous-history-element) (110 . next-history-element))) t
> read-expression-history)
> (let ((minibuffer-completing-symbol t)) (read-from-minibuffer "Eval: " nil
> read-expression-map t (quote read-expression-history)))
> (list (let ((minibuffer-completing-symbol t)) (read-from-minibuffer "Eval:
> " nil read-expression-map t (quote read-expression-history)))
> current-prefix-arg)
> ad-Orig-call-interactively(eval-expression nil nil)
> call-interactively(eval-expression nil nil)
>
> I reinstalled sage-mode (downloaded the spkg, as the command given yielded a
> 404 error), but unfortunately it did not fix the issue.
>
>
> On Wednesday, May 13, 2015 at 12:59:13 PM UTC-4, Ivan Andrus wrote:
> That’s really bizarre. What’s the value of sage-command? You set it to the
> right thing in your .emacs, but maybe it’s being set somewhere else.
>
> Does
>
> M-: (sage-create-new-sage nil) RET
>
> work correctly? How about
>
> M-: (sage-create-new-sage "/home/zach/sage-6.6-x86_64-Linux/sage") RET
>
>
> Thanks for your patience. Perhaps something in byte-compilation went wrong.
> Reinstalling might fix it if you’re eager to get back to work (which I assume
> you are). Just running
>
> sage -f sage_mode
>
> should reinstall everything cleanly.
>
> -Ivan
>
>> On May 13, 2015, at 8:26 AM, Zach Elgood <zache...@gmail.com <javascript:>>
>> wrote:
>>
>> Sage-version: 6.6; emacs-version: 24.3.1 (apparently I was wrong about the
>> version), sage-mode: 0.14.
>>
>> The issue occurs when launching sage. I managed to start up sage-mode using
>> init.el, and that worked out fine, and opening sage files work, but
>> attempting to start sage causes the issue.
>>
>> This is the backtrace:
>>
>> "Debugger entered--Lisp error: (wrong-type-argument stringp
>> sage-create-new-sage)
>> read-from-minibuffer("Run sage (like this): " sage-create-new-sage nil nil
>> sage-run-history sage-create-new-sage)
>> (list (read-from-minibuffer "Run sage (like this): " default nil nil
>> (quote sage-run-history) default) current-prefix-arg)
>> (let ((default (or cmd sage-command))) (list (read-from-minibuffer "Run
>> sage (like this): " default nil nil (quote sage-run-history) default)
>> current-prefix-arg))
>> (progn (let ((default (or cmd sage-command))) (list (read-from-minibuffer
>> "Run sage (like this): " default nil nil (quote sage-run-history) default)
>> current-prefix-arg)))
>> ad-Orig-call-interactively(sage-create-new-sage nil nil)
>> call-interactively(sage-create-new-sage)
>> sage(nil nil nil)
>> ad-Orig-call-interactively(sage record nil)
>> call-interactively(sage record nil)
>> command-execute(sage record)
>> execute-extended-command(nil "sage")
>> smex-read-and-run(("toggle-debug-on-error" "sage" "version"
>> "customize-group" "sage-mode" "inferior-sage-mode"
>> "highlight-indentation-mode" "cd" "5x5" "arp" "dbx" "dig" "erc" "ert" "ftp"
>> "gdb" "irc" "jdb" "man" "mpc" "pdb" "pwd" "rsh" "sdb" "xdb" "yow" "calc"
>> "diff" "dirs" "ffap" "gnus" "grep" "help" "ielm" "info" "life" "mail" "mpuz"
>> "ping" "pong" "smex" "talk" "term" "undo" "yank" ...))
>> smex()
>> ad-Orig-call-interactively(smex nil nil)
>> call-interactively(smex nil nil)"
>>
>> On Wednesday, May 13, 2015 at 1:16:08 AM UTC-4, Ivan Andrus wrote:
>> I’m sorry for the problems you’re experiencing. I have a few questions to
>> help diagnose the problem.
>>
>> When you say most recent version of sage-mode, what version is that exactly
>> (you can check the sage-mode-version variable)? Same for Emacs and Sage.
>>
>> Is the error is when you try to start sage, open a sage file, or load the
>> sage elisp library (during startup)?
>>
>> If you could get a backtrace that would be very helpful. You can do this by
>> turning on debugging with M-x toggle-debug-on-error RET and then try
>> starting sage.
>>
>> -Ivan
>>
>>> On May 12, 2015, at 1:03 PM, Zach Elgood <zache...@gmail.com <>> wrote:
>>>
>>> I just recently installed the most recent version of sage-mode, sage, and
>>> emacs (using Prelude), and the installation ran smoothly. However, I get
>>> multiple errors while attempting to load it in emacs.
>>>
>>> When attempting to load sage, I get the following error: list: Wrong type
>>> argument: stringp, sage-create-new-sage. I can boot up sage in the
>>> terminal, so it must be a problem with emacs/sage-mode.
>>>
>>> The only lines involving sage that I have in my init.el file are
>>> (add-to-list 'load-path
>>> "/home/zach/sage-6.6-x86_64-Linux/local/share/emacs/site-lisp/sage-mode")
>>> (require 'sage "sage")
>>> (setq sage-command "/home/zach/sage-6.6-x86_64-Linux/sage")
>>>
>>>
>>> --
>>> You received this message because you are subscribed to the Google Groups
>>> "sage-support" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to sage-support...@googlegroups.com <>.
>>> To post to this group, send email to sage-s...@googlegroups.com <>.
>>> Visit this group at http://groups.google.com/group/sage-support
>>> <http://groups.google.com/group/sage-support>.
>>> For more options, visit https://groups.google.com/d/optout
>>> <https://groups.google.com/d/optout>.
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "sage-support" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to sage-support...@googlegroups.com <javascript:>.
>> To post to this group, send email to sage-s...@googlegroups.com
>> <javascript:>.
>> Visit this group at http://groups.google.com/group/sage-support
>> <http://groups.google.com/group/sage-support>.
>> For more options, visit https://groups.google.com/d/optout
>> <https://groups.google.com/d/optout>.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-support" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-support+unsubscr...@googlegroups.com
> <mailto:sage-support+unsubscr...@googlegroups.com>.
> To post to this group, send email to sage-support@googlegroups.com
> <mailto:sage-support@googlegroups.com>.
> Visit this group at http://groups.google.com/group/sage-support
> <http://groups.google.com/group/sage-support>.
> For more options, visit https://groups.google.com/d/optout
> <https://groups.google.com/d/optout>.
--
You received this message because you are subscribed to the Google Groups
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.
