1. 21 May, 2021 2 commits
  2. 17 May, 2020 2 commits
  3. 19 Feb, 2020 1 commit
  4. 15 May, 2019 1 commit
  5. 01 Nov, 2018 1 commit
  6. 18 Oct, 2018 1 commit
    • Nikita Sirgienko's avatar
      [Sage] Some improvments · 9c54a06e
      Nikita Sirgienko authored
       - Fix bug, that first executed entry don't change status to "Computing" at all.
       - Fix broken handling syntax error in command text
       - In "SageExpression::parseError" show error as error message instead of as result (but sage don't use stderr, so this change do nothing, but maybe it's will be useful in future)
      9c54a06e
  7. 05 Oct, 2018 1 commit
  8. 01 Sep, 2018 1 commit
  9. 31 Aug, 2018 2 commits
  10. 15 Aug, 2018 1 commit
  11. 24 Jul, 2018 1 commit
  12. 01 Jul, 2018 1 commit
  13. 30 Apr, 2018 1 commit
  14. 13 Nov, 2017 1 commit
  15. 01 Jun, 2017 1 commit
  16. 11 Nov, 2014 1 commit
  17. 26 Jan, 2014 1 commit
    • Raphael Kubo da Costa's avatar
      Rename SageSession::VersionInfo::{major,minor}(). · 9bfdc48b
      Raphael Kubo da Costa authored
      Their names were causing conflicts: on BSD systems (and also on Linux with
      _BSD_SOURCE defined as is the case for KDE software), sys/types.h has two
      macros called major and minor.
      
      The build was failing on BSD systems but was passing on Linux due to how
      they are defined in glibc:
      
        #define major(dev) gnu_dev_major (dev)
        #define minor(dev) gnu_dev_minor (dev)
      
      In effect, after preprocessing those two methods were actually called
      SageSession::VersionInfo::gnu_dev_{major,minor}() on Linux.
      
      Rename the methods to majorVersion() and minorVersion() to avoid those
      conflicts.
      
      REVIEW:		115322
      9bfdc48b
  18. 24 Nov, 2013 2 commits
    • Alexander Rieder's avatar
      fix typesetting for newer sage versions · 9ae29115
      Alexander Rieder authored
      Since version 4.12 sage doesn't support the command sage.misc.latex.pretty_print_default anymore.
      Instead we use the %display ipython magic. In order to keep the code clean the
      specific commands have moved to a dedicated python function "__cantor_enable_typesetting(enable)"
      that gets declared on init and called by the backend when needed.
      This patch also introduces a finer handling of version numbers instead of just having a simple
      "legacy mode".
      
      Tested with Sage versions 5.10 (old commands) and 5.12 (new command)
      
      CCBUG: 327259
      FIXED-IN: 4.12
      (cherry picked from commit c3626842)
      9ae29115
    • Alexander Rieder's avatar
      fix typesetting for newer sage versions · c3626842
      Alexander Rieder authored
      Since version 4.12 sage doesn't support the command sage.misc.latex.pretty_print_default anymore.
      Instead we use the %display ipython magic. In order to keep the code clean the
      specific commands have moved to a dedicated python function "__cantor_enable_typesetting(enable)"
      that gets declared on init and called by the backend when needed.
      This patch also introduces a finer handling of version numbers instead of just having a simple
      "legacy mode".
      
      Tested with Sage versions 5.10 (old commands) and 5.12 (new command)
      
      BUG: 327259
      FIXED-IN: 4.12
      c3626842
  19. 23 Jun, 2013 1 commit
  20. 24 Sep, 2012 1 commit
    • Alexander Rieder's avatar
      fix the unit tests for Sage and Maxima · 716cae02
      Alexander Rieder authored
      this includes fixing the following bugs in sage:
      - wait for another prompt after __END_OF_INIT__ until indicating that sage is ready
      - we are sending 2 newlines for each command, count the prompts accodringly. This fixes proper queuing of commands again
      716cae02
  21. 09 May, 2012 1 commit
    • Martin Küttler's avatar
      The basic featues of CommandEntry work · c79cb0b0
      Martin Küttler authored
      CommandEntry is usable, but not everything works as of yet:
       - SyntaxHighlighting is crippled. It does not work in Maxima, but
         in Qalculate some things are highlighted.
       - Completion does not work, because Tabs are not recognised.
       - The WorksheetTextItems do not look nice: They have a wierd border,
         and the cursor is not shown.
       - WorksheetTextItems are also too small, they should fill the whole
         line.
       - Cursor movement does not work for additional information blocks.
         But I am not sure whether one should be able to navigate out of
         those, as any modification outside should abort the evaluation
         and destroy the additional information.
       - There most certainly is more.
      Other Entries can not yet be added to the Worksheet.
      c79cb0b0
  22. 16 Mar, 2012 1 commit
  23. 12 Feb, 2010 1 commit
  24. 07 Nov, 2009 1 commit
  25. 04 Oct, 2009 1 commit
  26. 30 Sep, 2009 1 commit
  27. 24 Sep, 2009 1 commit
  28. 03 Sep, 2009 1 commit
  29. 11 Aug, 2009 1 commit
  30. 06 Jul, 2009 1 commit
  31. 30 May, 2009 1 commit
  32. 27 May, 2009 1 commit
  33. 03 May, 2009 1 commit