A Sublime Text plugin that integrates a terminal directly into the editor for seamless shell access.
Glue is a Sublime Text plugin that integrates a terminal directly into the editor, allowing developers to execute shell commands, run scripts, and use system utilities without leaving their coding environment. It solves the problem of constant context switching between editor and terminal by bringing shell functionality into Sublime Text.
Sublime Text users who frequently use command-line tools and want to streamline their workflow by avoiding window switching.
Developers choose Glue because it provides seamless shell integration within Sublime Text with extensible custom commands, maintaining working directory state and supporting pipelining—all without needing external terminal applications.
Glue is a plugin that joins your shell to Sublime Text in quasi-perfect harmony.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Glue provides a dedicated view in Sublime Text for running shell commands and viewing output, eliminating context switching as shown by the command input box and output display examples.
Users can create custom command aliases via a simple JSON configuration file, enabling automation of frequent tasks like script execution, as demonstrated in the extension documentation.
The custom `cd` command maintains working directory state between shell calls, allowing consistent navigation without losing track of the current path.
It integrates with grep, cURL, Git, and multiple scripting languages, making it versatile for tasks from file searching to version control, as illustrated in the README examples.
The README explicitly states it is no longer under active development, meaning no bug fixes, updates, or support for newer Sublime Text versions or operating systems.
Glue only works with Sublime Text 2 and 3, excluding users of Sublime Text 4 or other editors, which severely limits its relevance in modern development environments.
Setup requires manual PATH confirmation and JSON-based command extensions, which can be cumbersome and error-prone compared to more integrated or plug-and-play solutions.