Allow .cmd as editor executable #2271

Closed
jerone opened this Issue Sep 13, 2015 · 3 comments

Projects

None yet

3 participants

@jerone
Contributor
jerone commented Sep 13, 2015

I would like to use Atom IDE as my userscript editor, but Atom's executable (.exe) is moved to another folder for every new release. To get around this, Atom supplies a .cmd file, but GM doesn't support this file extension to be set as userscript editor.

@jerone jerone changed the title from Allow .cmd as executable to Allow .cmd as editor executable Sep 13, 2015
@janekptacijarabaci
Contributor

Actually this can be addressed with:
1

@jerone
Contributor
jerone commented Sep 13, 2015

@janekptacijarabaci commented on 13 sep. 2015 12:15 CEST:

This can be addressed with:

1

Confirmed, but feels a bit hacky...

@arantius arantius added this to the 3.5 milestone Sep 13, 2015
@arantius arantius added a commit to arantius/greasemonkey that referenced this issue Sep 24, 2015
@arantius arantius Merge remote-tracking branch 'jerone/issues/#2271-allow-cmd'
Fixes #2271
0fec26a
@arantius arantius closed this in #2272 Sep 24, 2015
@arantius
Collaborator

This should be fixed and included in 3.5beta2, let me know if you still see problems with that version.
https://addons.mozilla.org/firefox/downloads/file/354794/greasemonkey-3.5beta2-fx.xpi?src=devhub

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment