improve usability about exporthtml HOT 3 CLOSED

Configuration is fine, but it is useless when I can not apply the plugin. It should work out of box after installation.

Slow down. You seem frustrated, but lets lay down some facts:

• On https://sublime.wbond.net/packages/ExportHtml ExportHtml has ~10,000 installs, and you are the first person to post that they can't use the plugin out of the box due to it being so unintuitive (unless there was an actual bug). Occasionally there are actual bugs or limitations like issue #5.
• You assume I have provided no way to use it out of the box instead of assuming maybe there is something wrong with your setup. Did you read the first line of https://github.com/facelessuser/ExportHtml#usage-exporting-html. Here I mention there are already default commands in the command palette (so it can work out of the box). All you have to do is type "export" to see them. Look here for actual commands that should be in the palette https://github.com/facelessuser/ExportHtml/blob/master/Default.sublime-commands. I even added options in the context menu if you right click on a view (granted I don't think the documentation mentions this, but I think it is pretty intuitive if you ever right click your view). While I am not the best with keeping my documentation up to date, I am usually good about providing answers to questions.
• You haven't really asked me anything in this issue. All you've done is tell me I have created an unintuitive plugin that doesn't work out of the box...thanks...?

I do all of my Sublime plugins in my free time, charge no money, and offer free support. I'm not running a business here, I am just kindly providing plugins that I spent my free time writing to the community so they don't have to write it themselves. Are some of my plugins rough around the edges? Sure, sometimes. I write these plugins first for myself and then I share them.

Let's keep in mind, the very install system for plugins sometimes can be fragile. Sometimes the convoluted nature of some plugins is because of Sublime's interface for plugins. Sometimes, there are quirks on systems that prevent plugins from working (ST2 on Linux has been problematic when people import the python plist library). Sometimes people install the wrong branch because they don't use Package Control for some reason. Sometimes Package Control seems to install the wrong branch. I really don't need a lecture on end users and documentation. Once you feel like you understand the problem, feel free to update the documentation in a pull request if you feel it is lacking.

Just politely ask me a question and/or describe your problem and I will get back to you when I have some time. You could have just said, "Hey, I tried looking in the command palette, but I can't find any commands, is there an easy way to use this out of the box? I installed this via Package Control on my Windows box. I am running Sublime version XXXX." See the difference?

from exporthtml.

Heh, just came here looking to see if anyone had reported the same difficulty :)

I created #22 to make it a little clearer. Thanks for the great plugin.

from exporthtml.

@edspencer Thanks! I know I blew up a little earlier. I appreciate you jumping in and taking care of this.

from exporthtml.