brackets-archive / bracketsIssues

Archive of issues in brackets.
0 stars 0 forks source link

[CLOSED] altering external packages #6123

Open core-ai-bot opened 3 years ago

core-ai-bot commented 3 years ago

Issue by oracleofammon Tuesday Feb 04, 2014 at 00:15 GMT Originally opened as https://github.com/adobe/brackets/issues/6747


i'm using brackets on a windows machine. i downloaded the emmet extension and am trying to change the key bindings. to do so, i must alter emmet's keymap.json file; however, i've looked in the brackets folder on my desktop but can't seem to find where the extension files are. where can i find them?

core-ai-bot commented 3 years ago

Comment by TomMalbran Tuesday Feb 04, 2014 at 00:19 GMT


In Brackets, go to Help -> Show Extensions Folder. Inside the user folder you should see the emmet extension.

core-ai-bot commented 3 years ago

Comment by MarcelGerber Tuesday Feb 04, 2014 at 16:12 GMT


@oracleofammon But keep in mind this file is overwritten with every Update of Emmet. Better copy it into another folder!

core-ai-bot commented 3 years ago

Comment by peterflynn Tuesday Feb 04, 2014 at 18:17 GMT


Right -- if you're going to patch an extension, better to clone it from git and keep it in the www/extensions/dev folder so you can control when & how updates are merged into your changes.

Closing since this is a question, not a bug.

core-ai-bot commented 3 years ago

Comment by oracleofammon Tuesday Feb 04, 2014 at 20:38 GMT


thanks so much for your help! one last thing: is the brackets/www/extenstions/dev folder not overwritten when brackets is updated?

core-ai-bot commented 3 years ago

Comment by peterflynn Tuesday Feb 04, 2014 at 21:37 GMT


Good point -- yes, it is. I'm used to the workflow where you're also pulling Brackets itself from git, and in that case it isn't overwritten. That's definitely the best choice for serious extension development, since it also lets you test out upcoming API changes before they're released, etc.

For what you're doing, it sounds fine to just keep the forked extension in the Help > Show Extensions Folder location. You can eliminate the risk of accidentally overwriting it with an extension update if you just modify the extension id in your copy (in package.json). (And then use git pull/merge workflows whenever you want to merge in changes from the original extension).

core-ai-bot commented 3 years ago

Comment by oracleofammon Wednesday Feb 05, 2014 at 15:17 GMT


you're right, i might stick to modifying through the Show Extensions Folder locations. i would pull it from git but i develop on a virtual machine that runs ubuntu and as far as i know, brackets isn't yet supported on linux-variant operating systems.

thus far, i've just been playing with it on my local windows machine and like it a lot. thanks so much for your help!

core-ai-bot commented 3 years ago

Comment by TomMalbran Wednesday Feb 05, 2014 at 19:17 GMT


It should work in Ubuntu. There is a Linux version of Brackets. In http://download.brackets.io/ if you click in all downloads, you can get all the versions.