> Yippee! All of those are serious time savers! Thanks!
>
>> Beta testers, please let me know what problems you have.
>> I felt like I added a lot of requested features this iteration, so
>> keep them coming.
>
> I will :-)
>
> An to start with:
>
> - C-C C-j seems to get confused by tabs in the input, and triggers
> automatic completion:
As far as I'm concerned, tabs in input are always wrong. Python even
has an error (TabError) for this, no? This is wontfix for me.
> - Is there general support in emacs for switching between two modes,
> depending on whether one is in the code or in comments? I very much
> like the rst-mode of emacs, and in the long run it would be great
> to edit the doctests in rst-mode and the code in sage-mode.
Yes and no: yes, people have hacked ways of doing this; no, there is
no general support. Multiple-major-modes is the best of them, at
least it was some time ago.
> - > * `next-error' now jumps between top-level errors, avoiding
> lower
>> level source files. Lower level source files are still hyperlinked.
>
> It might be jumping a bit too much. It detects no error in the test
> result in PS.
This I can't explain. The regexp is
(defvar sage-test-regexp-alist
'(("File \"\\(.*?\\)\", line \\([0-9]+\\):"
1 2)
("File \"\\(.*?\\)\", line \\([0-9]+\\),"
1 2 nil 0)
)) ;; a `compilation-error-regexp-alist' for sage doctest errors
And your examples should hit the first one. Is it consistently wrong?
Nick
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
