need help creating an autovoice

[Sir_Fz]

so how should it be ? $flnick == [lsearch $firstletter] ?

If we're to believe the manual, the syntax is as follows: lsearch ?options? list pattern ...and the index of the first element matching is returned or -1 if it was not found..so something like this should do the trick:

Code: Select all

if {[lsearch -exact $firstletter $flnick]>-1} {found} {not}

didn't get the "{found} {not}" part.

also in your final post:
if {[botisop $chan] && [string match \[a-z\]* $nick]} {
doesn't this mean if one of the cases is available the bot does the voicing.

shouldn't it be if {[botisop $chan] || [string match \[a-z\]* $nick]} {
so the bot only voices when both cases are available ?

[strikelight]

didn't get the "{found} {not}" part.

the {found} is where you put the code you want to handle the case where a match is found, the {not} is where you put the code you want to handle the case where a match is NOT found.

also in your final post:
if {[botisop $chan] && [string match \[a-z\]* $nick]} {
doesn't this mean if one of the cases is available the bot does the voicing.
shouldn't it be if {[botisop $chan] || [string match \[a-z\]* $nick]} {
so the bot only voices when both cases are available ?

Um, "||" is the logical OR , and "&&" is the logical "AND".. So "&&" is infact what he wanted.

I highly suggest you go through the suninet eggdrop tcl tutorial.

[user]

some of the other nicks I want it to voice begin with different brackets...

Your creation of the variable and comparison would work, but you have an extra { in there screwing things up.

I'd just include the braces in the character range passed to 'string match' in the existing code like this:
\[a-z\{\}\]*
Then it would match anything starting with a lowercase letter OR a brace...just add the chars you want between the brackets ([]) and escape the ones that needs it. (check the manual if in doubt)

[BlackRaven]

Thanks for all the great advice user, I appreciate it tremendously

BR

[Sir_Fz]

[snip]
the {found} is where you put the code you want to handle the case where a match is found, the {not} is where you put the code you want to handle the case where a match is NOT found.

Um, "||" is the logical OR , and "&&" is the logical "AND".. So "&&" is infact what he wanted.

I highly suggest you go through the suninet eggdrop tcl tutorial.

well I didn't get much of the found not... would you please give me an example, because if commands usualy are if {bla} {do} so how come you're telling me if {command} {found} {not} ... it confuses me.
can you please give an example ?

also some example about the "|| or" and the "&& and" , using them in lots of cases but not figuring out how they function.

thank you

[strikelight]

[snip]
the {found} is where you put the code you want to handle the case where a match is found, the {not} is where you put the code you want to handle the case where a match is NOT found.

Um, "||" is the logical OR , and "&&" is the logical "AND".. So "&&" is infact what he wanted.

I highly suggest you go through the suninet eggdrop tcl tutorial.

well I didn't get much of the found not... would you please give me an example, because if commands usualy are if {bla} {do} so how come you're telling me if {command} {found} {not} ... it confuses me.
can you please give an example ?

also some example about the "|| or" and the "&& and" , using them in lots of cases but not figuring out how they function.

thank you

The forum is polluted with examples, as is the suninet site that was posted in my last reply in this thread...

However.. Staying with the example from this thread:

Code: Select all

if {[botisop $chan] && [string match \[a-z\]* $nick]} { 
  # Here is what is meant by "found"....
  putlog "The bot is opped in $chan -AND- The first letter of the nick "$nick" is a lowercase letter"
} {
  # Here is what is meant by "not found"
  putlog "Either the bot is not opped in $chan -OR- The first letter of the nick "$nick" is NOT a lowercase letter"
}

Now, many times you'll see an 'else' in the middle of that code between the } and the { , which is perfectly acceptable, but unnecessary.

For more examples, again, I emplore you to read through various threads on this forum, and also visit various tcl tutorial sites, such as the mentioned suninet.nl site.

[Sir_Fz]

ok, that's what confused me. I always use the "else" between the two } {.

I'll be reading the manuals

thank you

[Dedan]

ok,
lets say you want to return the first 3 letters of a word.
what is the simplest way to do that?

Code: Select all

set word "eggdrop"

proc get:first:3letters { stuff } {
  global word
  set first3letters [ ?? [split $word] ??]
}

[user]

string range string first last

[Dedan]

cool,
thanks user

[caesar]

if it's a string then do as user sugested, but when is a list use lrange.

[Dedan]

Code: Select all

set word "eggdrop" 

proc get:first:3letters { stuff } { 
  global word 
  set first3letters [string trimright $word 2]
  # returns egg
  set firstletter [string trimright $word 0]
  # returns e

  also, how can i check to see if $firstletter is a number?
  is there a command, or do you "have" to use regexp
} 

[user]

'string trim' doesn't do what you said in your comments. I recommend reading the entire 'string' manual page

Check out: string is, string index, string range, string match

[Sir_Fz]

most networks do not allow the first letter to be a number.

if on yours' its allowed then regexp would be the best solution.

[user]

regexp SUCKS (so slow compared to most string commands that perform such tasks...it's only needed for really complex patterns that would require lots of other commands)

Here's an example (matching a number as the first char in a string):

% set a 0abcdefghijklmnopqrstuvwxyz
0abcdefghijklmnopqrstuvwxyz
% time [list regexp {[0-9]+.*} $a] 100000
10 microseconds per iteration
% time [list string match {[0-9]*} $a] 100000
2 microseconds per iteration