intro (1747B)
1 2 INTRODUCTION 3 by hhvn 4 5 1. Navigating around 6 Each menu has a set of commands, shown in blue. If you need more detail about 7 the commands type 'h' and then enter. Any command that has "<arg>" in it's 8 description is able of taking an argument: to do so first type the command, 9 then the argument, and hit enter. Most commands that take arguments should 10 also give you a prompt if you don't give it an argument - however there may 11 be some that are overlooked, so you are best not to wait for a prompt. 12 Any command marked in red is guaranteed to fail if run. (e,g, 'x' will not 13 work if you are on the last reply). 14 15 2. Writing 16 Attempt to limit each line you write to 80 characters. The row of equals 17 symbols can be used to judge this by eye. The line-editing is an unfortunate 18 downside to using raw tcp connexions, a sophisticated editor like vi and it's 19 derivatives require direct access to the tty - stdin and stdout are seen as 20 plain files by server. A workaround is to type your post out in an editor as 21 you usually would, and paste it into the bbs. 22 23 3. Tips/tricks 24 The *s* command doesn't require you to type out the entire board name, the 25 first character should suffice (unless there are boards with names that begin 26 with the same character). To view the first message in the thread, the sub-id 27 isn't necessary, eg: 'r 1' will work like 'r 1.0'. Pressing enter with no 28 command will work like the 'x' command, except if you are on the last reply, 29 where it will instead act like 'a'. 30 31 hbbs is licensed under the ISC 32 code: git://haydenvh.com/hbbs 33 gopher://haydenvh.com/1/git/o/hbbs