Pretend you're an expert hacker and can type flawlessly
- Total 3K
- Win 2K
- Mac 532
- Linux 609
|Feb 28||Feb 27||Feb 26||Feb 25||Feb 24||Feb 23||Feb 22||Feb 21||Feb 20||Feb 19||Feb 18||Feb 17||Feb 16||Feb 15||Feb 14||Feb 13||Feb 12||Feb 11||Feb 10||Feb 9||Feb 8||Feb 7||Feb 6||Feb 5||Feb 4||Feb 3||Feb 2||Feb 1||Jan 31||Jan 30||Jan 29||Jan 28||Jan 27||Jan 26||Jan 25||Jan 24||Jan 23||Jan 22||Jan 21||Jan 20||Jan 19||Jan 18||Jan 17||Jan 16||Jan 15||Jan 14|
Pretend you're an expert hacker and can type flawlessly. Inspired by http://hackertyper.com/
Basically, the plugin (when enabled) looks for a file with the same name as the one you are editing, with an additional “.hackertyper”-extension.
When it finds this file, it treats it as the “solution” for the file. Whenever you type something, it will try to read the same number of characters from the solution file and replace whatever you typed.
Partly because it was fun. Partly because it can be useful when “live coding” something. Usually, when you're doing a talk and you're a little busy trying to make sense to your audience, you tend to do a lot of typos and silly mistakes. I still think it's a great way to engage the audience - but I'd rather skip all the mistakes ;-)
- Install the package through Sublime Package Control. Search for HackerTyper.
- Enable the plugin through the command palette (Shift+Ctrl+P). “HackerTyper: Enable”.
- Create solution files alongside the files you want to pretend you're writing. So, to create an
index.html-file based on a solution, create a
index.html.hackertyper-file with the content you want to be typed out.
index.htmland start writing.
Protip: You might want to include
"file_exclude_patterns": ["*.hackertyper"] in your project settings or user preferences to prevent the solution files from showing up in the sidebar etc.
It operates on length of the file instead of characters pressed. This means if you press enter and sublime would insert some tabs/spaces, it will add as many characters. This doesn't match up to your keypresses and seems weird. There does not seem to be a “key down” event in Sublime, however, which would have fixed this.
The only reliable way of seeing if content has been added/removed seems to be the “modified” event. Since we cannot edit in an eventlistener, we need to run a command. This command changes the content of the editor, which triggers a modified event, creating a recursion loop. It is eventually stopped because of a max recursion depth limit, but this is obviously unwanted behaviour. Not sure how to work around this.
MIT-licensed. See LICENSE.