get rid of warning

[spider.git] / cmd / Commands_en.hlp

diff --git a/cmd/Commands_en.hlp b/cmd/Commands_en.hlp
index b0b21c66824886e18efdf78a1853c2e1ca123b3a..41d6313b625d5ee1f3d9d4f91040cf4d5869155c 100644 (file)
--- a/cmd/Commands_en.hlp
+++ b/cmd/Commands_en.hlp
@@ -1135,7 +1135,7 @@ need to create any directories you want to put stuff in beforehand as well.
 It is likely that you will want to run these commands in a crontab type 
 situation. You would do that something like:-
 
 It is likely that you will want to run these commands in a crontab type 
 situation. You would do that something like:-
 

-  0 0 * * * run_cmd('save /tmp/dxstats echo "DXStat Table", "sh/dxstats"')
+  0 0 * * * run_cmd('save /tmp/dxstats "echo DXStat Table", "sh/dxstats"')

 
 Note that you still enclose each command with (") characters but you must
 enclose the entire save command in (') characters. 
 
 Note that you still enclose each command with (") characters but you must
 enclose the entire save command in (') characters. 


@@ -1153,7 +1153,9 @@ an individual callsign or to one of the 'bulletin' addresses.
 
 SEND <call> on its own acts as though you had typed SEND PRIVATE, that is
 it will mark the message as personal and send it to the cluster node that
 
 SEND <call> on its own acts as though you had typed SEND PRIVATE, that is
 it will mark the message as personal and send it to the cluster node that

-that callsign is connected to.
+that callsign is connected to. If the <call> you have specified is in fact
+a known bulletin category on your node (eg: ALL) then the message should
+automatically become a bulletin.

 
 You can have more than one callsign in all of the SEND commands.
 
 
 You can have more than one callsign in all of the SEND commands.
 


@@ -1167,6 +1169,51 @@ receive a read receipt when they have read the message.
 SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak)
 SP is an alias for SEND PRIVATE
 
 SB is an alias for SEND NOPRIVATE (or send a bulletin in BBS speak)
 SP is an alias for SEND PRIVATE
 

+The system will ask you for a subject. Conventionally this should be 
+no longer than 29 characters for compatibility. Most modern cluster
+software should accept more.
+
+You will now be prompted to start entering your text. 
+
+You finish the message by entering '/EX' on a new line. For instance:
+
+  ...
+  bye then Jim
+  73 Dirk
+  /ex
+
+If you have started a message and you don't want to keep it then you
+can abandon the message with '/ABORT' on a new line, like:-
+
+  line 1
+  line 2
+  oh I just can't be bothered with this
+  /abort
+
+If you abort the message it will NOT be sent.
+
+When you are entering the text of your message, most normal output (such
+as DX announcements and so on are suppressed and stored for latter display
+(upto 20 such lines are stored, as new ones come along, so the oldest
+lines are dropped).
+
+Also, you can enter normal commands commands (and get the output 
+immediately) whilst in the middle of a message. You do this by typing
+the command preceeded by a '/' character on a new line, so:-
+
+  /dx g1tlh 144010 strong signal
+
+Will issue a dx annoucement to the rest of the cluster. 
+
+Also, you can add the output of a command to your message by preceeding 
+the command with '//', thus :-
+
+  //sh/vhftable
+
+This will show YOU the output from SH/VHFTABLE and also store it in the
+message. 
+
+You can carry on with the message until you are ready to send it. 

 === 0^SET/ADDRESS <your address>^Record your postal address
 
 === 0^SET/ANNOUNCE^Allow announce messages to come out on your terminal
 === 0^SET/ADDRESS <your address>^Record your postal address
 
 === 0^SET/ANNOUNCE^Allow announce messages to come out on your terminal


@@ -2045,6 +2092,15 @@ To leave talk mode type:
    
    /EX
 
    
    /EX
 

+If you are in 'Talk' mode, there is an extention to the '/' command which
+allows you to send the output to all the people you are talking to. You do 
+with the '//' command. For example:-
+
+  //sh/hftable
+
+will send the hftable as you have it to all the people you are currently 
+talking to.
+

 === 0^TYPE <filearea>/<name>^Look at the contents of a file in one of the fileareas
 Type out the contents of a file in a filearea. So, for example, in 
 filearea 'bulletins' you want to look at file 'arld051' you would 
 === 0^TYPE <filearea>/<name>^Look at the contents of a file in one of the fileareas
 Type out the contents of a file in a filearea. So, for example, in 
 filearea 'bulletins' you want to look at file 'arld051' you would