> For the complete documentation index, see [llms.txt](https://docs.bcbi.brown.edu/codiac-for-health/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bcbi.brown.edu/codiac-for-health/computing/text-editors.md). # Text Editors Programming languages are written using text editor applications. These applications allow users to create and edit free text, which can then be run as programs. Text editors differ in complexity, some including extra functionality for easier, more efficient programming. Text editors with auto-complete suggest common functions or existing variables as the programmer begins to type, which the programmer can then select without needing to finish typing. Some text editors offer options to run individual lines of code or entire programs while editing files. ## Popular Text Editors ### Microsoft Visual Studio Code (recommended) * Available for Mac, Windows, and Linux operating systems * Includes support for debugging, syntax highlighting, auto-complete, and additional user-friendly functionality * [Download Microsoft Visual Studio Code](https://code.visualstudio.com/) ### Jupyter Notebooks * Web application text editor, no download necessary * Includes options for interactive output (HTML, images, videos, LaTeX, and custom MIME types), support for big data tools, such as Apache Spark, and options for sharing notebooks with others * Run individual lines of code or entire programs at once * [Get started with Jupyter Notebooks](https://jupyter.org/) ### VI/VIM * Highly configurable * Included in most UNIX operating systems (e.g., Linux, or MacOS), no download necessary * Write files from the Terminal * [Interactive VIM Tutorial](https://www.openvim.com/) ### Emacs * Highly configurable * Included in most UNIX operating systems (e.g., Linux, or MacOS), no download necessary, also available for Windows * Wide range of built-in features for text editing, such as syntax highlighting, automatic indentation, and search and replace * [Learn more about Emacs](https://opensource.com/resources/what-emacs) ### Pico * Included in most UNIX operating systems (e.g., Linux, or MacOS), no download necessary * Most of the editing commands are displayed at the bottom of the editing screen for easy reference * [Learn more about Pico](https://ts.vcu.edu/askit/research-math-science/unix-for-researchers-at-vcu/unix-text-editors/the-pico-editor/) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.bcbi.brown.edu/codiac-for-health/computing/text-editors.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.