::new;

[jacky]

Ok, I'm filling this under bug because I think it's one.

I have a problem with the command new, and the fact that when triggered it goes into rename mode automatically. This should not be the case, or at least there need an optional parameter to disable this behavior.

Also, it gets weird/unexpected result right now, when other commands are used after. For instance, try this when you have one item selected on List ::new a::selpos 1, 2
Sure the first two items get selected, but the first one doesn't have a name shown, and we're still in rename mode for the newly-created file "a", or so it seems ! Because pressing enter to validate gets an error message like we're trying to rename the first item (without a name visible at that time) !!
And indeed, typing in "foobar" and pressing enter renames that first item, not the one just created, though it was it the one that appeared to be on rename mode.

I found a way around it using focus (::focus t::focus l) but I think that we should have a paramater to not go in rename mode. And maybe, if this parameter isn't set, the script execution shouldn't go on until the rename mode is "closed" ?

[admin]

Code: Select all

      ' syntax: new [name], file|dir, [source], [r]
      '   r = invoke rename mode after creation

Delivery tomorrow (along with <clipboard>)...

[jacky]

Code: Select all

      ' syntax: new [name], file|dir, [source], [r]
      '   r = invoke rename mode after creation

Delivery tomorrow (along with <clipboard>)...

Awesome!