Skip to content

Conversation

@randolph555
Copy link

@randolph555 randolph555 commented Dec 22, 2025

  • I'm the package's author and/or maintainer.
  • I have read the docs.
  • I have tagged a release with a semver version number. (v1.0.0)
  • My package repo has a description and a README describing what it's for and how to use it.
  • My package doesn't add context menu entries. *
  • My package doesn't add key bindings. **
  • Any commands are available via the command palette.
  • Preferences and keybindings (if any) are listed in the menu and the command palette, and open in split view.
  • If my package is a syntax it doesn't also add a color scheme.
  • I use .gitattributes to exclude files from the package.

*Context menu: Only adds one "Execute Command" entry for running selected text as shell command.

**Key bindings:

  • macOS: Cmd+Enter (run command), Ctrl+Tab (history complete)
  • Linux: Ctrl+Enter (run command), Ctrl+Tab (history complete)

My package is similar to Terminus, however it should still be added because:

  1. Lightweight - No terminal panel, executes commands directly in the editor
  2. Inline output - Command output appears right below the command line
  3. Streaming output - Real-time output display, doesn't block the editor
  4. Pipe support - Select text + |command to pipe content to shell commands
  5. History autocomplete - Auto-complete from command history
  6. Dangerous command protection - Confirms before running rm -rf, sudo rm, etc.

This is useful for quick command execution without leaving the editor context.

Add sublime-run-command package
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant