fix chat

[spider.git] / cmd / Commands_en.hlp

diff --git a/cmd/Commands_en.hlp b/cmd/Commands_en.hlp
index 6a5131980a17849bd3052ad3d15f1083397bc58e..b5c10c19255ce7c6e87176c4072e3c1e194d2472 100644 (file)
--- a/cmd/Commands_en.hlp
+++ b/cmd/Commands_en.hlp
@@ -378,6 +378,7 @@ in the system. It is also aliased to SHOW/COMMAND.
 === 9^DBCREATE <name>^Create a database entry
 === 9^DBCREATE <name> chain <name> [<name>..]^Create a chained database entry
 === 9^DBCREATE <name> remote <node>^Create a remote database entry
 === 9^DBCREATE <name>^Create a database entry
 === 9^DBCREATE <name> chain <name> [<name>..]^Create a chained database entry
 === 9^DBCREATE <name> remote <node>^Create a remote database entry

+=== 9^DBCREATE <name> cmd <dxspider command>^make a local command available as a DB

 DBCREATE allows you to define a database in the system. It doesn't actually
 create anything, just defines it.
 
 DBCREATE allows you to define a database in the system. It doesn't actually
 create anything, just defines it.
 


@@ -430,6 +431,16 @@ to allow
 
 to work as they may be used to.
 
 
 to work as they may be used to.
 

+You can also make local commands available as 'pseudo' databases. You
+can therefore make spider special commands available as a database. I
+imagine that this will be primarily useful for remote access from 
+legacy nodes. For example:-
+
+  DBCREATE dxqsl cmd show/dxqsl
+
+You also use one of these databases in a chain. This may be useful 
+locally. 
+

 See DBIMPORT for the importing of existing AK1A format data to databases.
 See DBSHOW for generic database enquiry
  
 See DBIMPORT for the importing of existing AK1A format data to databases.
 See DBSHOW for generic database enquiry
  


@@ -1410,7 +1421,7 @@ of a DX announcement (there is just enough room). Some user programs
 cannot cope with this. The Spotter's CQ is on the RHS of the 
 time, the Spotted's CQ is on the LHS.
 
 cannot cope with this. The Spotter's CQ is on the RHS of the 
 time, the Spotted's CQ is on the LHS.
 

-Conflicts with: SHOW/DXGRID, SHOW/DXITU, SHOW/USSTATE
+Conflicts with: SET/DXGRID, SET/DXITU, SHOW/USSTATE

 
 Do a STAT/USER to see which flags you have set if you are confused.  
 
 
 Do a STAT/USER to see which flags you have set if you are confused.  
 


@@ -1421,7 +1432,7 @@ of a DX announcement (there is just enough room). Some user programs
 cannot cope with this. The Spotter's ITU is on the RHS of the 
 time, the Spotted's ITU is on the LHS.
 
 cannot cope with this. The Spotter's ITU is on the RHS of the 
 time, the Spotted's ITU is on the LHS.
 

-Conflicts with: SHOW/DXGRID, SHOW/DXCQ, SHOW/USSTATE
+Conflicts with: SET/DXGRID, SET/DXCQ, SHOW/USSTATE

 
 Do a STAT/USER to see which flags you have set if you are confused.  
 
 
 Do a STAT/USER to see which flags you have set if you are confused.  
 


@@ -1433,7 +1444,7 @@ of a DX announcement (there is just enough room). Some user programs
 cannot cope with this. You can use this command to reset (or set)
 this feature.
 
 cannot cope with this. You can use this command to reset (or set)
 this feature.
 

-Conflicts with: SHOW/DXCQ, SHOW/DXITU
+Conflicts with: SET/DXCQ, SET/DXITU

 
 Do a STAT/USER to see which flags you have set if you are confused.  
 
 
 Do a STAT/USER to see which flags you have set if you are confused.  
 


@@ -1707,7 +1718,7 @@ information from SET/DXGRID.
 Some user programs cannot cope with this. You can use this command 
 to reset (or set) this feature.
 
 Some user programs cannot cope with this. You can use this command 
 to reset (or set) this feature.
 

-Conflicts with: SHOW/DXCQ, SHOW/DXITU
+Conflicts with: SET/DXCQ, SET/DXITU

 
 Do a STAT/USER to see which flags you have set if you are confused.  
 
 
 Do a STAT/USER to see which flags you have set if you are confused.  
 


@@ -1766,6 +1777,14 @@ Show all the nodes connected to this node.
 This command shows information on all the active connections known to
 the node. This command gives slightly more information than WHO.
 
 This command shows information on all the active connections known to
 the node. This command gives slightly more information than WHO.
 

+=== 0^SHOW/CONTEST <year and month>^Show all the contests for a month
+Show all known contests which are maintained at http://www.sk3bg.se/contest/
+for a particular month or year. The format is reasonably flexible.
+For example:-
+  
+  SH/CONTEST sep2003
+  SH/CONTEST 03 march
+

 === 0^SHOW/DATE [<prefix>|<callsign>]^Show the local time 
 This is very nearly the same as SHOW/TIME, the only difference the format
 of the date string if no arguments are given.
 === 0^SHOW/DATE [<prefix>|<callsign>]^Show the local time 
 This is very nearly the same as SHOW/TIME, the only difference the format
 of the date string if no arguments are given.


@@ -2095,6 +2114,25 @@ is provided for users of this software by http://www.qrz.com
 
 See also SHOW/WM7D for an alternative.
 
 
 See also SHOW/WM7D for an alternative.
 

+=== 0^SHOW/DXQSL <callsign>^Show any QSL info gathered from spots
+The node collects information from the comment fields in spots (things
+like 'VIA EA7WA' or 'QSL-G1TLH') and stores these in a database.
+
+This command allows you to interrogate that database and if the callsign
+is found will display the manager(s) that people have spotted. This 
+information is NOT reliable, but it is normally reasonably accurate if
+it is spotted enough times.
+
+For example:-
+
+  sh/dxqsl 4k9w
+
+You can check the raw input spots yourself with:-
+
+  sh/dx 4k9w qsl
+
+This gives you more background information.
+

 === 9^SHOW/REGISTERED [<prefix>]^Show the registered users
 
 === 0^SHOW/ROUTE <callsign> ...^Show the route to the callsign
 === 9^SHOW/REGISTERED [<prefix>]^Show the registered users
 
 === 0^SHOW/ROUTE <callsign> ...^Show the route to the callsign