Differences
This shows you the differences between the selected revisions of the page.
ui_customcommand 2015-02-18 | ui_customcommand 2023-03-08 (current) | ||
Line 5: | Line 5: | ||
The //Description// box is where you type name (or description) of the custom command. The box is present when you are adding or editing [[custom_command|custom command]] only. | The //Description// box is where you type name (or description) of the custom command. The box is present when you are adding or editing [[custom_command|custom command]] only. | ||
- | You will see your custom command under this name in menu //File(s) > Custom Commands//. You can insert ampersand (''&'') before a letter to make it keyboard accelerator, for example ''&Grep''. | + | You will see your custom command under this name in menu //Files > Custom Commands//. You can insert ampersand (''&'') before a letter to make it keyboard accelerator, for example ''&Grep''. |
The //Custom command// box is where you type the actual [[custom_command|custom command]]. The command typically include [[custom_command#patterns|patterns]]. | The //Custom command// box is where you type the actual [[custom_command|custom command]]. The command typically include [[custom_command#patterns|patterns]]. | ||
Use //Remote command// and //Local command// to select [[custom_command#types|type of custom command]]. | Use //Remote command// and //Local command// to select [[custom_command#types|type of custom command]]. | ||
+ | |||
+ | ~~AD~~ | ||
Check //Apply to directories// checkbox to make the command be executed even for selected directories. The option is disabled for commands that does not work with files. | Check //Apply to directories// checkbox to make the command be executed even for selected directories. The option is disabled for commands that does not work with files. | ||
Line 17: | Line 19: | ||
When you check neither //Apply to directories// nor //Execute recursively//, the selected directories will be ignored. | When you check neither //Apply to directories// nor //Execute recursively//, the selected directories will be ignored. | ||
- | Check //Show results in terminal// checkbox to make the output of the custom command be shown in [[ui_console|Console window]]. Check //Copy results to clipboard// checkbox to make the output of the custom command be copied to clipboard. Neither option can be used with [[custom_command#types|local custom commands]]. | + | Check //Show results in terminal// checkbox to make the output of the custom command be shown in [[ui_console|Console window]]. The option cannot be used with [[custom_command#types|local custom commands]]. To keep an output of a local console command in a console window, use syntax like ''cmd /C dir & pause''. |
+ | |||
+ | Check //Copy results to clipboard// checkbox to make the output of the custom command be copied to clipboard. The option can be used with [[custom_command#types|local custom commands]] only. To copy an output of a local console command to the clipboard //in the latest stable version//, pipe the command output to ''[[https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/clip|clip]]'' like ''cmd /C dir | clip''. This of course makes sense with console applications only. | ||
Check //Use remote files// with a local custom command to make ''!'', ''!&'' and ''!/'' [[custom_command#patterns|patterns]] refer to remote paths, instead of paths to a local copy of the remote files (prevents the download itself too). | Check //Use remote files// with a local custom command to make ''!'', ''!&'' and ''!/'' [[custom_command#patterns|patterns]] refer to remote paths, instead of paths to a local copy of the remote files (prevents the download itself too). | ||
The //Keyboard shortcut// box is where you can associate [[custom_key_shortcuts|custom keyboard shortcut]] with the custom command. | The //Keyboard shortcut// box is where you can associate [[custom_key_shortcuts|custom keyboard shortcut]] with the custom command. |