Two small inaccuracies in the TC help

Jun 3, 2008
9
0
57
Switzerland
#1
I have found the following inaccuracies in the TC help (v.9.02.152):


The help contains by the "Key Mapping Directives":

LIST Keys (Overview)

ListFindRegexReverse
Prompt and search backwards for a regular expression

TCC says: Invalid item name "ListFindRegexReverse"
--------------------

In the detailed help to "ListFindRegexReverse" the help says

ListBack = Key
--------

This version will be accepted by the TCC.

---------------

By the "General Input Key":

The help says:

Backspace directive

Default: Backspace

On other appearances in the help, the name for the backspace key is "Bksp", which is the name for use in the tcmd.ini.

---------------

Best regards,
-Urmel-
 

rconn

Administrator
Staff member
May 14, 2008
10,415
95
#2
Urmel wrote:

> I have found the following inaccuracies in the TC help (v.9.02.152):
>
> The help contains by the "Key Mapping Directives":
>
> LIST Keys (Overview)
>
> ListFindRegexReverse
> Prompt and search backwards for a regular expression
>
> TCC says: Invalid item name "ListFindRegexReverse"
> --------------------
>
> In the detailed help to "ListFindRegexReverse" the help says
>
> ListBack = Key
> --------
>
> This version will be accepted by the TCC.
ListFindReverse and ListFindRegexReverse are obsolete (and no longer
supported), as both forward & backward searching are now done in the
same dialog. I've removed them from the help file.

ListBack means something different (return to the previous file).

Rex Conn
JP Software
 
Jun 3, 2008
9
0
57
Switzerland
#3
ListFindReverse and ListFindRegexReverse are obsolete (and no longer
supported),
Thanks for this info.

I've removed them from the help file.
I think in the help file for the next build?

I would be grateful if you could ALL directives list/describe in the help
file. It's imho not always clear, which directive is in connection to
which menu entry in the option dialog (e.g FuzzyCD and Extended Directory
Search).

Best regards,
-Urmel-
 

rconn

Administrator
Staff member
May 14, 2008
10,415
95
#4
Urmel wrote:

>
> I would be grateful if you could ALL directives list/describe in the help
> file. It's imho not always clear, which directive is in connection to
> which menu entry in the option dialog (e.g FuzzyCD and Extended Directory
> Search).
The directives were removed from the help file because we do not support
manual entry. All of the .INI directives except the key directives
(which are still documented) can be (and should be) set from OPTION.

Rex Conn
JP Software
 
#5
Rex Conn wrote:


> The directives were removed from the help file because we do not support
> manual entry. All of the .INI directives except the key directives
> (which are still documented) can be (and should be) set from OPTION.
>
However, you still support the OPTION //directive=value syntax for changing
an option on the fly in a batch file or from the command line. How is a new
user, (or an old user with an imperfect memory), to know the directive
names?

-- Howard
----- Original Message -----
From: "JP Software Forums" <[email protected]>; "rconn"
<>
To: <[email protected]>
Sent: Saturday, October 25, 2008 8:31 PM
Subject: RE: [Support-t-576] Re: Two small inaccuracies in the TC help



> Urmel wrote:
>
>
> ---Quote---
>>
>> I would be grateful if you could ALL directives list/describe in the help
>> file. It's imho not always clear, which directive is in connection to
>> which menu entry in the option dialog (e.g FuzzyCD and Extended Directory
>> Search).
> ---End Quote---
> The directives were removed from the help file because we do not support
> manual entry. All of the .INI directives except the key directives
> (which are still documented) can be (and should be) set from OPTION.
>
> Rex Conn
> JP Software
>
>
>
>
 

rconn

Administrator
Staff member
May 14, 2008
10,415
95
#6
Howard Goldstein wrote:

> Rex Conn wrote:
>
>
> Quote:
> > The directives were removed from the help file because we do not support
> > manual entry. All of the .INI directives except the key directives
> > (which are still documented) can be (and should be) set from OPTION.
> >
>
> However, you still support the OPTION //directive=value syntax for changing
> an option on the fly in a batch file or from the command line. How is a new
> user, (or an old user with an imperfect memory), to know the directive
> names?
The OPTION //... syntax is for backwards compatibility; I doubt that
even 1% of TCC users will ever use it. I don't want either new or old
users to know the directive names!

Having the .INI directives in the help file was a constant support
headache; upwards of half of all our support calls/questions used to be
because users had mangled their .INI files with manual edits. Since
everything was moved to OPTION and the individual directives removed
from the help, the configuration problems have dropped to near zero.

Rex Conn
JP Software
 
Jun 3, 2008
9
0
57
Switzerland
#7
The directives were removed from the help file because we do not support
manual entry. All of the .INI directives except the key directives
(which are still documented) can be (and should be) set from OPTION.
Ok, I see that I must change my usualness. Exclusive working in the console will more and more be replaced with a mixed way (console and gui). I don't like this, but this trend will overrun me...

But I can very good understand your argument regarding the support calls.

-Urs- aka Urmel