- May
- 3,515
- 5
Charles:
1/ MKSC - when the command is used to display properties of existing shortcuts, it would be nice to be able to list only selected ones. A model: option /F of Vince Fatica's WHICHWIN (in sysutils.dll). Suboptions could indicate if all properties displayed should be on a single line, and (for tabular display) the display width of each field (for single line mode only). There should be an option to display the linkfile on the same line, and whether or not it should be shown with or without path (analogous to the fp, fn and fpn fields of PDIR). Another feature could be that not naming a linkfile on the command line implies * (i.e., all) in the same manner as it does in DIR and PDIR.
2/ @SCINFO - the quoted/unquoted flag should be available as a mnemonic, instead of usable only with the numeric property selectors; there should be a code for linkfile; there should be width selection.
3/ @SCINFO - even using it inside @SAFEEXP it does not always return the "symbolic command separator" in its symbolic form %+ but converts it to its current definition (sometimes only the first one when there are two in the arguments field.
TIA!
1/ MKSC - when the command is used to display properties of existing shortcuts, it would be nice to be able to list only selected ones. A model: option /F of Vince Fatica's WHICHWIN (in sysutils.dll). Suboptions could indicate if all properties displayed should be on a single line, and (for tabular display) the display width of each field (for single line mode only). There should be an option to display the linkfile on the same line, and whether or not it should be shown with or without path (analogous to the fp, fn and fpn fields of PDIR). Another feature could be that not naming a linkfile on the command line implies * (i.e., all) in the same manner as it does in DIR and PDIR.
2/ @SCINFO - the quoted/unquoted flag should be available as a mnemonic, instead of usable only with the numeric property selectors; there should be a code for linkfile; there should be width selection.
3/ @SCINFO - even using it inside @SAFEEXP it does not always return the "symbolic command separator" in its symbolic form %+ but converts it to its current definition (sometimes only the first one when there are two in the arguments field.
TIA!