#55 Smarter Auto Typing

open
nobody
5
2006-08-15
2006-08-15
Eric Hacker
No

It would be nice if Smart Auto Typing could be more
context aware. If the next character is already defined
then either just insert the opening key or perhaps
enclose the whole word.

I do a lot of borrowing and recaftoring of code and
this would make that easier.

Example:
Existing text, need to add another parameter for sub:
my $var = shift;

Current behavior on typing open paren before $var:
my ()$var = shift;
^cursor between ()

New default behavior when not followed by whitespace:
my ($var = shift;
^cursor between ( $

With sub-option Grab Word set for Auto Typing ():
my ($var) = shift;
^cursor after close paren

The sub option would be best set for each and not global.

Thanks

Discussion

  • Kevin Benton
    Kevin Benton
    2007-06-19

    Logged In: YES
    user_id=856803
    Originator: NO

    I agree, especially when typing things like "<=" because EPIC assumes that I want a > because I typed a <. That's not necessarily true, especially in an conditional context.

    Kevin