catdad/brackets-open-shell-here

:turtle: open a shell window in the project root

brackets-open-shell-here

Windows

Supported shells include the default CMD, PowerShell, and on Windows 10, when enabled, bash is supported as well.

Linux

Ubuntu is now supported, using gnome-terminal. If you requite any other distros, please feel free to open a new issue and I will take a look.

macOS

I plan on adding macOS support as I get time (and a system to test on). For now, this extension will do nothing on a Mac.

Building the extension

gulp

This will create the requires zip file in the output folder.

brackets-open-shell-here's Issues

use mock-stdio module

https://github.com/catdad/mock-stdio

setting multiple paths seems to prevent npm from executing local node_modules binaries

Found this out when I was trying to run npm start on a server that used nodemon as its start script. It was not able to find the binary from a Brackets-opened cmd, but worked fine from a regular cmd. I deleted the PATH variable, leaving only Path, and it worked fine.

Not totally sure why this is happening yet...

with April 2018 update, the bash on Windows buttons opens the wrong bash

> where bash
C:\Program Files (x86)\Git\bin\bash.exe
C:\Windows\System32\bash.exe

Maybe it's not Windows? But I really didn't change anything else. It now opens git-bash rather than bash on Windows. I didn't really change anything other than install the April 2018 update.

support for bash is broken in brackets 1.9

Also, it opens the wrong cmd again. They must have gone back to 1.7 ways of doing things, which is annoying af.

add build

some bad logging exists

[catdad.open-shell-here] %s shell successfully started, showing %s default C:/Users/Kiril/AppData/Roaming/Brackets/extensions/user/brackets-open-shell-here/

add support for bash on Windows 10

• clean up old crap
• enable picking which shells to have a button in the toolbar
• save in prefs

add macOS shell support

For terminal and iterm:

spawn('open', ['-a', term, path])

• Terminal
• iTerm
• update CSS
• how can I test it?

add ability to open the file explorer

add error handling to all of the shell spawn processes

A spawn error brings down the entire Node service, causing all sorts of errors in Brackets. That seems like a Brackets bug (should probably run extensions in isolation), but go figure...

open an admin cmd?

get rid of stupid Windows workarounds in Brackets 1.8

Yay Node 6!

• title
• test Ctrl+C for exiting processes
• clean up all the old crap

add README

update README to remove old C workaround stuff

uploaded release zips should have the version number on them

• update zip name output by gulp
• update travis artifact name to be uploaded

add Linux shell support

• gnome-terminal
• xfce4-terminal
• make sure css is updated
• what happens when the default is not available?