V11 desiderata

#1
Extension of the WHICH command and its /A option to functions and internal
variables.
Extension of the WHICH command - display the name of the plugin implementing
a feature.

Enhance the "pause after each page" feature used by many commands to
consider wrapped lines

Display control options to force wrapping or truncating lines wider than the
current window (regardless of buffer width)

A display control option to indicate whether or not a line is wrapped (so
they could be distinguished from subsequent lines) - this might be in the
form of explicitly displaying an end-of-line indicator.

Command to convert between Unix NL and MS-DOS CR,LF.
--
Steve
 

rconn

Administrator
Staff member
May 14, 2008
10,533
94
#2
> Extension of the WHICH command and its /A option to functions and
> internal variables.

Why would that be useful? (Also IMO that's in no way related to the purpose of WHICH -- if there's a reason for it, it should probably be in a separate command.)

> Extension of the WHICH command - display the name of the plugin
> implementing a feature.

See above.

> Enhance the "pause after each page" feature used by many
> commands to consider wrapped lines

It always has -- do you have an example that's not working?

> Display control options to force wrapping or truncating lines wider
> than the current window (regardless of buffer width)

Not under my control; that's up to the console manager.

> Command to convert between Unix NL and MS-DOS CR,LF.

There's a bazillion of those already; I don't see how having it as an internal would add any value.
 
#3
|| Extension of the WHICH command and its /A option to functions and
|| internal variables.

| Why would that be useful? (Also IMO that's in no way related to the
| purpose of WHICH -- if there's a reason for it, it should probably
| be in a separate command.)

One often wants to know whether or not a function name is already in
use, and if so where it is defined. Likewise, there are some "internal
variables" which have been added by plug-ins, and later incorporated
into tcc.exe.

I used WHICH only to describe the desired new functionality, whether
it is implemented using a new command or as an extension of WHICH is
not important.

|| Extension of the WHICH command - display the name of the plugin
|| implementing a feature.

| See above.

Since HELP for each plug-in is implemented totally independently of
TCC's help, uniquely for each, one needs to know which plug-in or
plug-ins implement a feature to find its help. Specifying the plug-in
which implements a command is just like specifying the full path of a
batch file that implements an "external command".

|| Enhance the "pause after each page" feature used by many
|| commands to consider wrapped lines

| It always has -- do you have an example that's not working?

I recently observed a problem with an internal command, I think COPY.
Unfortunately I did not record which command.

|| Display control options to force wrapping or truncating lines wider
|| than the current window (regardless of buffer width)

| Not under my control; that's up to the console manager.
--
Steve
Would that be TCMD in a tabbed environment?

|| Command to convert between Unix NL and MS-DOS CR,LF.

| There's a bazillion of those already; I don't see how having it as
| an internal would add any value.

OK.
 

rconn

Administrator
Staff member
May 14, 2008
10,533
94
#5
||| Display control options to force wrapping or truncating lines wider
||| than the current window (regardless of buffer width)
||
|| Not under my control; that's up to the console manager.
|
| Would that be TCMD in a tabbed environment?

No, that would be the Windows console manager -- in or out of a tabbed environment.
 
#7
rconn wrote:
| ---Quote (Originally by Charles Dye)---
|| I think that would be useful, for commands anyway. Instead of
|| "frobit is a plugin command", how about "frobit is a plugin command:
|| c:\bin\tcmd\plugins\wondertools.dll" ?
| ---End Quote---
|
| Do 99.9% of the users care where the plugin command actually comes
| from?

They do - if they need to find the relevant plugin help.
--
Steve
 

Charles Dye

Super Moderator
Staff member
May 20, 2008
3,588
46
Albuquerque, NM
prospero.unm.edu
#8
rconn wrote:
| ---Quote (Originally by Charles Dye)---
|| I think that would be useful, for commands anyway. Instead of
|| "frobit is a plugin command", how about "frobit is a plugin command:
|| c:\bin\tcmd\plugins\wondertools.dll" ?
| ---End Quote---
|
| Do 99.9% of the users care where the plugin command actually comes
| from?

They do - if they need to find the relevant plugin help.
Or if there are name collisions between plugins, although I haven't yet encountered one.
 
#10
I have used the plugin command to look through the 160 or so plugin
provided names to see which one had a particular feature. I have had
to unload one or two in the past that had name collisions with things
I wrote, and it would be nice to figure out which one a bit more
quickly.

On Tue, Jul 14, 2009 at 7:22 PM, rconn<> wrote:

> ---Quote (Originally by Charles Dye)---
> I think that would be useful, for commands anyway. Instead of "frobit is a plugin command", how about "frobit is a plugin command: c:\bin\tcmd\plugins\wondertools.dll" ?
> ---End Quote---
>
> Do 99.9% of the users care where the plugin command actually comes from?
>
>
>
>
>


--
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.