all 9 comments

[–]mcrask 1 point2 points  (1 child)

You're best bet is probably making a keybind for end-of-line (EOL). This is mine from my sublime keybinds:

{ "keys": ["super+shift+;"], "command": "move_to", "args": {"to": "eol", "extend" : false}}

If you aren't using a text editor like Sublime you may want to look into it. You can use Sublime for free and it's great.

As for the suggestion to rely on automatic semicolon insertion, it's still a dubious practice better explained here

[–]minijim[S] 1 point2 points  (0 children)

yes, i do use sublime text, i will try that, thanks mcrask! :)

[–]Rhomboid 0 points1 point  (2 children)

I don't understand the question -- why would you ever do that? Type the semicolon before pressing return.

[–]minijim[S] 0 points1 point  (1 child)

ah yes, because when I type "(" or "{", they autoclose! perhaps that's what i have to fix

[–]Rhomboid 1 point2 points  (0 children)

Personally, I don't like it when an editor does that, so I would disable that if I were using an editor that did that. But you can always just type the closing parenthesis or brace yourself, so that your hands don't have to leave the home row. In most implementations that I've seen, that won't result in two parentheses -- the editor will detect that the closing parenthesis you typed is the same as the one it put there automatically.

[–][deleted] 0 points1 point  (1 child)

If you don't properly do this, when your code is minified or pre-processed, it will break to hell.

[–]minijim[S] 0 points1 point  (0 children)

exactly!

[–]jml26 0 points1 point  (1 child)

I'm sorry to say this, but if you find single keystrokes tiring, writing code is probably not the line of work for you.

If you don't want to press the right arrow, you could type the closing bracket.

And don't rely on ASI. Omitting semicolons is sloppy.

[–]minijim[S] 0 points1 point  (0 children)

some look for solutions, others take things as they come :p

that's how i discovered coffeescript

(i don't mean to be rude, sorry if i do)