Done Suggestion for V11

[Jim Cook]

.) I renew my request to have the ability for DIR /S to sort the
entire list together instead of first by folder.

.) I would like the ability to display relative/based (a limited form
of /F) paths for DIR /S that would start with the path specified and
only show subfolders from there -- not the entire path.

If the current folder had two sub folders, one of which had its own
sub folder, a DIR /S would show:

file1
sub1\file2
subsub1\file3
sub2\file4

If I did DIR /S SUB1\* it would show

sub1\file2
sub1\subsub1\file3

--
Jim Cook
2009 Saturdays: 4/4, 6/6, 8/8, 10/10, 12/12 and 5/9, 9/5, 7/11, 11/7.
Next year they're Sunday.

 

[Charles Dye]

* An option for INPUT /E and ESET to pre-select the default value for overtyping. (Can do it now with KEYSTACK ! SHIFT-END, but that's clumsy at best, and in TCmd 9/10 it's downright ugly.)

* Speaking of which, KEYSTACK ! hasn't worked for a while. Is it no longer technically feasible?

* Don't disable directory colorization with DIR /F or DIR /B /S. TCC always detects redirection correctly AFAIK, and in the unlikely event it doesn't there is always /D.

* Add a VARS keyword for tab completion of environment variables. (Might also be handy to have ALIASES, FUNCTIONS, etc.? How about INTERNALS?)

* A @REGREN function to rename registry keys/values

* Would it be possible to redefine Take Command's 16-color palette? On a per-tab basis? On the fly?

* Plugin API: Give plugins easy access to TCC's enhanced wildcards, ranges, /S etc.?

* Plugin API: Give plugins access to internet-files capabilities?

* HELP, F1, Ctrl-F1: Recognize plugin commands/variables/functions, and dispatch to the plugin for help?

 

[Jim Cook]

.) Make SETLOCAL/ENDLOCAL work from the command prompt

--
Jim Cook
2009 Saturdays: 4/4, 6/6, 8/8, 10/10, 12/12 and 5/9, 9/5, 7/11, 11/7.
Next year they're Sunday.

 

[Steve Fabian]

Jim Cook wrote:
|| .) I renew my request to have the ability for DIR /S to sort the
|| entire list together instead of first by folder.
||
|| .) I would like the ability to display relative/based (a limited form
|| of /F) paths for DIR /S that would start with the path specified and
|| only show subfolders from there -- not the entire path.
||
|| If the current folder had two sub folders, one of which had its own
|| sub folder, a DIR /S would show:
||
|| file1
|| sub1\file2
|| subsub1\file3
|| sub2\file4
||
|| If I did DIR /S SUB1\* it would show
||
|| sub1\file2
|| sub1\subsub1\file3

Concur. Same for PDIR too, of course. Add additional switches for /O: p
(path, relative or absolute); in PDIR, report field numbers, including
multiple sort key specification based on report fields (key evaluation
should be based on report fields, including embedded spaces and other
special characters if applicable).

PDIR options:
.) new field q, qp and qn - same an f, fp, and fn, but always enclosed in
quotation marks
.) new subfield for f and q: r = relative path: fr, frn

--
Steve

 

[Steve Fabian]

Charles Dye wrote:
|| * A @REGREN function to rename registry keys/values

* findfirst/findnext type search of registry allowing all keys to be found

* @regkeytype - return a code to indicate type of registry key
--
Steve

 

[drwtsn32]

Add the "cdspell" feature of bash (cd spell correction).

 

[samintz]

Not to poo-poo your ideas, but all modern versions of Windows from Win2K
on, have the external application REG.EXE that can do all that. While I
understand that there are purists out there who think that it's better if
it's built-in to TCC, functionally it's exactly the same.

And with V10 of TC you now have array support to hold the output as well
as the "/P command" switch in DO.

By the way, there is no native API that I know of to rename a registry
key. As far as I know, you need to copy the key to the new name and then
delete the old one.

-Scott


Steve F$BaC(Bi$BaO(B <> wrote on 06/03/2009 02:05:36 PM:

> Charles Dye wrote:
> || * A @REGREN function to rename registry keys/values
>
> * findfirst/findnext type search of registry allowing all keys to be

found

>
> * @regkeytype - return a code to indicate type of registry key
> --
> Steve
>
>
>
>

 

[Steve Fabian]

samintz wrote:
|| Not to poo-poo your ideas, but all modern versions of Windows from
|| Win2K
|| on, have the external application REG.EXE that can do all that.
|| While I understand that there are purists out there who think that
|| it's better if
|| it's built-in to TCC, functionally it's exactly the same.
||
|| And with V10 of TC you now have array support to hold the output as
|| well
|| as the "/P command" switch in DO.

Sorry, I was not aware of anything but REGEDIT, which is GUI. Yes, REG.EXE
may be sufficient, I need to dig into it.
--
Steve

 

[rconn]

Steve Fábián wrote:

> * findfirst/findnext type search of registry allowing all keys to be found

Not sure how useful that would be, given that there's already a Windows
external to do that.

> * @regkeytype - return a code to indicate type of registry key

How would that differ from the existing @REGTYPE?

Rex Conn
JP Software