| T O P I C R E V I E W |
| MiddleTommy |
Posted - Dec 21 2006 : 09:52:29 AM
Just a little shortcut suggestion:
When using auto closing })] and ", text is not inserted if you
press })] or " next to the matching closing character. Right?
So...
I suggest to also add a feature when ";" is pressed next to an auto closing character that it places the ";" on the outside of the closing character
ie.
character | represents blinking cursor
press: "|
auto text: "|"
type: "Some words|"
press semi-colon: "Some words;|"
auto text change to this: "Some words";|
|
| 5 L A T E S T R E P L I E S (Newest First) |
| feline |
Posted - Dec 28 2006 : 2:04:20 PM
It is an interesting idea. |
| MiddleTommy |
Posted - Dec 28 2006 : 10:28:21 AM
You could make it an option to turn it off inside quotes
or make you have to hold down CTRL with semicolon to allow the semicolon in side the string. etc.. etc... for each other closing character.
I bet the amount of semicolons inside string literals, etc... are far less than the ones at the end of each and every line in the entire program
I believe most would suffer a little for semicolons in strings to save tons of split seconds of having to press the arrow key or the like(a key not on the main keyboard which requires moving your hand and not just a finger) to go out of the closing character and then press semicolon
If that makes sense as a valid arguement?
Well I hope it makes it into future releases. |
| feline |
Posted - Dec 22 2006 : 07:53:47 AM
I am going to leave the priority alone, since this is a possible future enhancement, rather than a bug that is causing problems  |
| accord |
Posted - Dec 22 2006 : 07:24:19 AM
I also like this idea 
Can you pump up the priority?  |
| feline |
Posted - Dec 21 2006 : 11:26:38 AM
we could not do this inside double quotes, since you are typing a string. as soon as we start saying "you cannot type a semi colon in the middle of a literal string" this is going to cause problems.
there is a feature request to spot semi colon's in "invalid" locations, just before a closing bracket, and move them to after the closing bracket, which is the same basic idea as this.
case=296 |
