Should we modernize the custom commands?

[bigstar]

Should we modernize the custom commands?

Current design limitations.
1. Commands are limited to 250 characters.
2. Groups can only be 2 levels deep.
3. Shortcuts are limited to Ctrl+Shift+<key>
4. The semi-colon key ";" can't be used in a custom commands.

Umm Anything Else?

Feel free to add your suggestions.

[Fusion]

Items 2-4 are rather limiting, and I'd like very, very much to see an enhancement there. In part, that's why I've rarely hit the #1 limitation, so if you fix 2-4, you might just aswell do #1.

Also, can custom-commands, especially with parameters, be seamlessly nested, and if so, how deep?

[bigstar]

I'm not quite sure I understand what you mean, can you give me an example?

[exseven]

deleted

[Fusion]

Originally posted by bigstar
I'm not quite sure I understand what you mean, can you give me an example? Let's say you have one custom command that accepts parameters via prompts. Can a second custom command that also accepts parameters re-use the first command as parts of its run without prompting for more info? Or would we need to prompt for the same info repeatedly?

[Fusion]

Originally posted by exseven
its fusion
dazzle them with brilliance or baffel them with bullshit Both MxxCon and Shark would call that a useless post, ex.

[bigstar]

Originally posted by Fusion
Let's say you have one custom command that accepts parameters via prompts. Can a second custom command that also accepts parameters re-use the first command as parts of its run without prompting for more info? Or would we need to prompt for the same info repeatedly?


That's already possible.
I can't think of a usefull example but this will give you the idea.

For each %d prompt that value can later be accessed via %<num>

SITE %d %1

if %d = "Hello" the result would be SITE Hello Hello

[exseven]

maybe usefull example

site adduser %d(user) %d(pass) %d(ident); site change %1 flags %d

[cjr]

To tell you the truth I have never used this feature before and may never. I just can't see a need for it.

[bulbi]

to begin sorry for my english because i'm french...

it would bery cool u change the custom command
the best wlould be that we can use a custom command in a custom command!!!!
to increase the number of character would be a very good idea too

:) :) :)

[_fuji_]

Allow custom commands to be used inside of custom commands...

This would allow us to make use of the functions theory used in every programming language other than cobol i think it was...

#1 would be nice :)
#2 Never had a problem with it
#3 Never had a problem with it
#4 The semi colon use, or lack thereof can be limiting at times...

Perhaps a scripting language similar to leapftp could be implemented... because imo leap has the best support for scripting.

[JuvY]

Allow executing one code that will perform command over the selected dirs one by one.

Example:

rnfr %f
rnto %d

rnfr will be performed on the first of the selected dirs, then rnto on the same dir, and then it will move on to the next dir.

REN %f * %d doesn't wanna work at all times :(

[bigstar]

Originally posted by JuvY
Allow executing one code that will perform command over the selected dirs one by one.

Example:

rnfr %f
rnto %d

rnfr will be performed on the first of the selected dirs, then rnto on the same dir, and then it will move on to the next dir.

REN %f * %d doesn't wanna work at all times :(


with the current design rnfr %f rnto %d is impossible with multiple selected files.

what's wrong with REN %f * %d? I was not aware there was a problem, but if you can tell me about it I will try to fix it.

[ACDC]

Yeah, optimize this!

1.] Command in commands
2.] MUCH more than 250 characters
3.] Basic FlashFXP functions like browseandlistto.. cwd and then list will not work...
4.] Correct command queue Sample:

RNFR %f
RNTO %f_

on multiple files the first command is executed on all files, then the second. -->Wrong

5.] ALL ftp commands... which results may be saved in variables for later usage

That's all for the moment :D

[bigstar]

With the beta release of build 853 many of of these limitations have been addressed.

The following limitations no longer exist.
1. Commands are limited to 250 characters.
2. Groups can only be 2 levels deep.
3. Shortcuts are limited to Ctrl+Shift+<key>
4. The semi-colon key ";" can't be used in a custom commands.