Meta-ticket: document configuring IDEs and text editors

[slelievre]

Document configuring each common IDE or text editor for using and/or developing Sage.

• CodeMirror
• Emacs + sage-shell-mode
• JupyterLab text editor
• PyCharm
• Spyder
• Sublime Text
• vi / vim
• VSCode / vscodium - #30484

and maybe others such as

• Alpha, Alphatk
• ATOM + Hydrogen
• Blender
• Eclipse
• IDLE
• Leo
• PyDev
• PyScripter
• Wing
• Xcode

What to document:

• setting up syntax highlighting for .py, .pyx, .spyx, .sage files
• telling the editor or IDE to use Sage's Python
• making Sage execute fragments of code

Maybe one ticket per IDE or text editor?

Existing material:

• some wiki pages
  • ​https://wiki.sagemath.org/IDE
  • ​https://wiki.sagemath.org/PyCharm
  • ​https://wiki.sagemath.org/SpyderInstructions

• some answers to questions, or discussions, on Ask Sage, sage-devel, sage-support, Stack Overflow

• ​Ask Sage question 39742: Make PyCharm recognise the Sage Python interpreter
• ​Stack Overflow question 47378147: Use PyCharm (or any Windows IDE) to run SageMath scripts
• ​sage-devel discussion, 2017-12: Running Sage from an IDE like PyCharm on Windows
• ​Ask Sage question 38750: How to use Sage in PyCharm in Ubuntu

Related:

• #30501: Syntax highlighting mode for Sage syntax, aware of the syntactic sugar Sage adds to Python syntax

• ​GitHub applies Python syntax highlighting to .sage and .sagews files

• ​Request to apply Python syntax highlighting to questions tagged sage on Stack Overflow

• #30453 - Document sage -tox

• ​Martin Albrecht: Conda, Jupyter and Emacs

[slelievre]

Maybe this is better done on the wiki, and the wiki should have a summary page pointing to a page for each IDE or text editor.

[slabbe]

Maybe the part about vim could mention :set backupcopy=yes (see #21739) to avoid issues with the attach command (well, it's in my vimrc since 2015, but I don't know if it is still needed).

[mkoeppe]

Replying to slelievre:

Maybe this is better done on the wiki, and the wiki should have a summary page pointing to a page for each IDE or text editor.

-1 for wiki - it's unmaintainable

+1 for extending the developer documentation

[slelievre]

New blog post:

• ​Martin Albrecht: Conda, Jupyter and Emacs