X-Git-Url: http://dxcluster.net/gitweb/gitweb.cgi?a=blobdiff_plain;f=cmd%2FCommands_en.hlp;h=498f3ad26e5073e1cd10c9d04a90d156d24287de;hb=918827ec5a9023edeb2ce0140692566591af0af8;hp=61734e449470224b6986bf0a280f51073e069003;hpb=bad1ddf774c205e1cf0e012860d06481abbbb400;p=spider.git diff --git a/cmd/Commands_en.hlp b/cmd/Commands_en.hlp index 61734e44..498f3ad2 100644 --- a/cmd/Commands_en.hlp +++ b/cmd/Commands_en.hlp @@ -34,6 +34,25 @@ DX cluster . This process creates a new 'client' process which will use the script in /spider/connect/ to effect the 'chat' exchange necessary to traverse the network(s) to logon to the cluster . +=== 9^CATCH All|[ ...]^Mark a message as sent +=== 9^UNCATCH All|[msgno> ...]^Unmark a message as sent +When you send messages the fact that you have forwarded it to another node +is remembered so that it isn't sent again. When you have a new partner +node and you add their callsign to your /spider/msg/forward.pl file, all +outstanding non-private messages will be forwarded to them. This may well +be ALL the non-private messages. You can prevent this by using these +commmands:- + + catch GB7DJK all + catch GB7DJK 300 301 302 303 + +and to undo what you have just done:- + + uncatch GB7DJK all + uncatch GB7DJK 300 301 302 303 + +which will arrange for them to be forward candidates again. + === 9^DEBUG^Set the cluster program into debug mode Executing this command will only have an effect if you are running the cluster in debug mode i.e. @@ -44,14 +63,31 @@ It will interrupt the cluster just after the debug command has finished. === 0^DIRECTORY^List messages === 0^DIRECTORY ALL^List all messages === 0^DIRECTORY OWN^List your own messages -=== 0^DIRECTORY NEW^List your own new messages -List the messages in the messages directory. +=== 0^DIRECTORY NEW^List all new messages +=== 0^DIRECTORY TO ^List all messages to +=== 0^DIRECTORY FROM ^List all messages from +=== 0^DIRECTORY SUBJECT ^List all messages with in subject +=== 0^DIRECTORY ^List last messages +=== 0^DIRECTORY -^List messages message message +List the messages in the messages directory. If there is a 'p' one space after the message number then it is a -personal message. +personal message. If there is a '-' between the message number and the +'p' then this indicates that the message has been read. + +You can use shell escape characters such as '*' and '?' in the +fields. + +You can combine some of the various directory commands together eg:- + + DIR TO G1TLH 5 +or + DIR SUBJECT IOTA 200-250 -If there is a - after the message number then this indicates that the -message has been read. +You can abbreviate all the commands to one letter and use ak1a syntax:- + + DIR/T G1* 10 + DIR/S QSL 10-100 5 === 5^DIRECTORY-^ Sysops can see all users' messages. @@ -136,7 +172,13 @@ cluster and be returned. You can get rid of any message to or originating from your callsign using this command. You can remove more than one message at a time. -=== 5^KILL-^ +=== 5^KILL -^Remove a range of messages from the system +=== 5^KILL FROM ^Remove all messages from a callsign +=== 5^KILL TO ^Remove all messages to a callsign +=== 5^KILL FULL [ [/]^Ask for the latest spots and WWV @@ -336,13 +378,29 @@ day - - days days ago info - any spots containing in the info or remarks -spotter - any spots spotted by +by - any spots spotted by (spotter is the + same). + +qsl - this automatically looks for any qsl info on the call + held in the spot database. + +iota [] - If the iota island number is missing it will look for + the string iota and anything which looks like an iota + island number. If you specify then it will look for + that island. + +qra [] - this will look for the specific locator if you specify + one or else anything that looks like a locator. e.g. SH/DX 9m0 SH/DX on 20m info iota SH/DX 9a on vhf day 30 + SH/DX rf1p qsl + SH/DX iota + SH/DX iota eu-064 + SH/DX qra jn86 === 0^SHOW/DXCC ^Interrogate the spot database by country This command takes the (which can be a full or partial @@ -355,7 +413,7 @@ e.g. SH/DXCC G SH/DXCC W on 20m info iota -=== 0^SHOW/FILES []^List the contents of a filearea +=== 0^SHOW/FILES [ []]^List the contents of a filearea SHOW/FILES on its own will show you a list of the various fileareas available on the system. To see the contents of a particular file area type:- @@ -363,6 +421,10 @@ area type:- where is the name of the filearea you want to see the contents of. +You can also use shell globbing characters like '*' and '?' in a +string to see a selection of files in a filearea eg:- + SH/FILES bulletins arld* + See also TYPE - to see the contents of a file. === 0^SHOW/PREFIX ^Interrogate the prefix database @@ -441,7 +503,12 @@ filearea 'bulletins' you want to look at file 'arld051' you would enter:- TYPE bulletins/arld051 -See also SHOW/FILES to see what fileareas are available and a list of content +See also SHOW/FILES to see what fileareas are available and a +list of content. + +=== 0^WHO^Show who is physically connected +This is a quick listing that shows which callsigns are connected and +what sort of connection they have === 0^WX ^Send a weather message to local users === 0^WX FULL ^Send a weather message to all cluster users