Variable naming conventions and how to use Help file (newbie) - TCL

Richard Owlett <rowlett@atlascomm.net> wrote:

> My original question was "What variable naming convention is typically
> used?" Or, "How do I avoid collisions of variable names and tcl keywords?"

There are no "tcl keywords" as such. Command names and variable names
do not collide; they are in separate categories.

> That led to exploring the help system which comes with ActiveStates
> ActiveTcl. It seems to be exhaustive. But search functionality leaves me
> lost. It will list pages where desired term appears. *BUT*, there seems
> to be no way to find just where term is used in a page that may be over
> 3000 words long.

What OS are you using? I have no problem searching through a page of
text on my Windows system at work.

In article <aranders-317F01.22074307072007@news.isp.giganews.com>,
Alan Anderson <aranders@insightbb.com> wrote:
>Richard Owlett <rowlett@atlascomm.net> wrote:
>
>> My original question was "What variable naming convention is typically
>> used?" Or, "How do I avoid collisions of variable names and tcl keywords?"
>
>There are no "tcl keywords" as such. Command names and variable names
>do not collide; they are in separate categories.

Alan Anderson wrote:
> Richard Owlett <rowlett@atlascomm.net> wrote:
>
>
>>My original question was "What variable naming convention is typically
>>used?" Or, "How do I avoid collisions of variable names and tcl keywords?"
>
>
> There are no "tcl keywords" as such. Command names and variable names
> do not collide; they are in separate categories.

OK. So
set puts "this is weird"
puts $puts
is perfectly legitimate, if bordering on unreadable.

>
>
>>That led to exploring the help system which comes with ActiveStates
>>ActiveTcl. It seems to be exhaustive. But search functionality leaves me
>>lost. It will list pages where desired term appears. *BUT*, there seems
>>to be no way to find just where term is used in a page that may be over
>>3000 words long.
>
>
> What OS are you using? I have no problem searching through a page of
> text on my Windows system at work.

WindowsXP Pro.

Its a previously unnoticed "feature" of Windows Help system (in this
case display of *.chm files). Once you get to a "help page", there is
never a means to search within the page.

The issue is now moot as I came across http://www.tcl.tk/man/ and its
link to Core Documentation in html. Its the same information accessed in
two different ways. So I'll use either/both as needed.

Thanks

Cameron Laird wrote:

> In article <aranders-317F01.22074307072007@news.isp.giganews.com>,
> Alan Anderson <aranders@insightbb.com> wrote:
>
>>Richard Owlett <rowlett@atlascomm.net> wrote:
>>
>>
>>>My original question was "What variable naming convention is typically
>>>used?" Or, "How do I avoid collisions of variable names and tcl keywords?"
>>
>>There are no "tcl keywords" as such. Command names and variable names
>>do not collide; they are in separate categories.
>
> .
> .
> .
> ... and it's not even uncommon to encounter stylish code
> which depends on this, in the sense that "$button" or
> "$list" make frequent appearances in small procedures.

OY VEH!

"Richard Owlett" <rowlett@atlascomm.net> wrote in message
news:1391qtpj4m0p610@news.supernews.com...

> Its a previously unnoticed "feature" of Windows Help system (in this
> case display of *.chm files). Once you get to a "help page", there
> is never a means to search within the page.

Sure there is... Once you arrive at a specific page in the CHM file...

- Click in the right-hand pane (the content pane)
- Press Ctrl+F to open a standard "Find" dialog
- Type your search string there...

Jeff

Richard Owlett <rowlett@atlascomm.net> wrote:

> Its a previously unnoticed "feature" of Windows Help system (in this
> case display of *.chm files). Once you get to a "help page", there is
> never a means to search within the page.

That's neither a feature nor a bug. It's an operator error. Just use a
reasonably standard control-F to invoke the Find dialog.

> The issue is now moot as I came across http://www.tcl.tk/man/ and its
> link to Core Documentation in html. Its the same information accessed in
> two different ways. So I'll use either/both as needed.

I tend to use the Tcler's Wiki more often than the local help, myself.

Jeff Godfrey wrote:
> "Richard Owlett" <rowlett@atlascomm.net> wrote in message
> news:1391qtpj4m0p610@news.supernews.com...
>
>
>>Its a previously unnoticed "feature" of Windows Help system (in this
>>case display of *.chm files). Once you get to a "help page", there
>>is never a means to search within the page.
>
>
> Sure there is... Once you arrive at a specific page in the CHM file...
>
> - Click in the right-hand pane (the content pane)
> - Press Ctrl+F to open a standard "Find" dialog
> - Type your search string there...
>
> Jeff
>
>

Now you're going tell me that that has been around since Windows ran on
top of DOS in 640k ;/
Live-n-learn

Jeff Godfrey wrote:
> "Richard Owlett" <rowlett@atlascomm.net> wrote in message
> news:1391qtpj4m0p610@news.supernews.com...
>
>> Its a previously unnoticed "feature" of Windows Help system (in this
>> case display of *.chm files). Once you get to a "help page", there
>> is never a means to search within the page.
>
> Sure there is... Once you arrive at a specific page in the CHM file...
>
> - Click in the right-hand pane (the content pane)
> - Press Ctrl+F to open a standard "Find" dialog
> - Type your search string there...
>
> Jeff
>
>
One problem I have with the chm file (with tcl 8.4.12) is that my editor
(ultra-edit) does not open the with the tcl key word or a search for
that word, when I highlight a word and press F1. With the old .hlp files
of 8.3, this worked very well.

Peter

pwel...@zonnet.nl wrote:
> One problem I have with the chm file (with tcl 8.4.12) is that my editor
> (ultra-edit) does not open the with the tcl key word or a search for
> that word, when I highlight a word and press F1. With the old .hlp files
> of 8.3, this worked very well.

You can also use http://www.tcl.tk/man/tcl8.4/TclCmd/<cmd>.htm
(remember to replace <cmd> with the command name!) directly, and those
pages are trivially searchable using numerous online services...

Donal.