User Tools

Site Tools

Trace:
bboard

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
bboard [2024/09/02 22:56] – ' hc9bboard [2025/03/22 02:54] (current) – added bbvi configuration info zilog
Line 131: Line 131:
 ^ ''(Q)UIT'' | QUIT the BBOARD | ^ ''(Q)UIT'' | QUIT the BBOARD |
  
-===== Customizing bboard(1) =====  
- 
-* For bboard options, check the ''bboard'' man page via the **man bboard** command at the shell prompt.* 
  
 ==== How to Use new SCAN and KILL Commands ==== ==== How to Use new SCAN and KILL Commands ====
Line 144: Line 141:
  
 To remove a previously killed board from the list and start scanning it for new posts again, ''(G)OTO'' the killed board and press ''K'' again to remove it from your kill list. To remove a previously killed board from the list and start scanning it for new posts again, ''(G)OTO'' the killed board and press ''K'' again to remove it from your kill list.
 +
 +==== How to Search ====
 +
 +Two search options for BBOARD
 +  * "(S)earch"--that is, the ''S'' command-- scans the current BBOARD for the KEYWORD
 +  * "(s)earch"--that is, the ''s'' command-- scans all boards for the KEYWORD
 +
 + Your prompts upon finding a match may look like this:
 +
 +   <HELPDESK.27-May-22>[ <ENTER> to CONT, (J)UMP or (Q)UIT ] 
 +
 +  * CONT continues the search to the next post containing KEYWORD, except that it's scanning thread by thread, if the search hits on a post, the next hits will be posts in the same thread before it checks other threads for posts with KEYWORD
 +    * While navigating through posts, your prompt may be ''[ SCROLL (F)ORWARD, (B)ACKWARD - (Q)UIT ]''
 +      * FORWARD scrolls towards the end of the post (same as hitting space bar)
 +      * BACKWARD scrolls towards the end of the post (same as hitting space bar)
 +      * QUIT quits displaying the current post and returns to your search
 +  * JUMP interrupts the current search and step through the rest of the current thread. Other posts in the same thread may not contain the target KEYWORD, but you might want to read follow-up posts anyway. At the end of the thread, you may continue the KEYWORD search
 +    * During a JUMP, the options change to this: ''[ <ENTER> follow thread, (R)EPLY, (F)LAG or (Q)UIT ]''
 +      * <ENTER> continues following the thread (you are still in search)
 +      * REPLY lets you reply
 +      * FLAG does something
 +      * QUIT //returns to your KEYWORD search//, you'll see ''% Returning to SEARCH on 'KEYWORD'''
 +    * Note: JUMP in the middle of a search ends up having the same behavior as continue: both "find" posts containing KEYWORD in the same thread as your current hit.
 +  * QUIT ends the search.
 +
 +
 +===== Customizing bboard(1) ===== 
 +
 +* For bboard options, check the ''bboard'' man page via the **man bboard** command at the shell prompt.*
  
 ==== Change default editor ==== ==== Change default editor ====
  
-=== Change to a better pico ====+From the man page:
  
-If you want to use an editor with in-program help and simple interface like the default //pico//, but slightly more powerful than the default **bboard** editor, you may wish to instead set your editor to //nano//, which is the default editor integrated into the Alpine mail program. It's the same as //pico//, but has additional commands, like regex searching.+       bboard uses a single configuration file, called .bboardrc to honour  
 +       the EDITOR environment variable.  Currently 'tty', 'pico', and 'vi'  
 +       modes are available. 
 +         examples: 
 +         EDITOR=tty         #sets 'tty' mode for stdin 
 +         EDITOR=vi          #sets 'vi' mode 
 +         EDITOR=pico        #sets 'pico' mode  (DEFAULT)
  
-To do this, instead of setting up your //.bboardrc// as above, set it as follows (you can do this with ''nano ~/.bboardrc''!):+ 
 +To change to a different editor option, as above, set your //.bboardrc//  as follows (you can do this with ''vi ~/.bboardrc''!):
  
 <file config ~$USER/.bboardrc> <file config ~$USER/.bboardrc>
-  # set editor to nano: +  # set editor to vi: 
-  EDITOR=nano+  EDITOR=vi
 </file> </file>
  
-=== Changing the default editor to vi ===+=== How to set up a better bboard editing experience ===
  
 Many SDF users find the lack of word-wrap and spell-checking when posting in bboard(1) frustrating. If a Vi editor is acceptable, some rudimentary auto-wrapping and spell-checking can be accomplished in //bboard(1)// with the following configuration files in your HOME (~$USER/) directory: Many SDF users find the lack of word-wrap and spell-checking when posting in bboard(1) frustrating. If a Vi editor is acceptable, some rudimentary auto-wrapping and spell-checking can be accomplished in //bboard(1)// with the following configuration files in your HOME (~$USER/) directory:
  
-<file vim ~$USER/.exrc>+<file txt ~$USER/.exrc> 
 +  " " set normal color white: 
 +  color normal white 
 +  " " set miss-spelled words red: 
 +  color spell red
   " " set auto-wrap width:   " " set auto-wrap width:
   set textwidth=78   set textwidth=78
Line 172: Line 209:
   set spellautoload   set spellautoload
 </file> </file>
 +
 +Note that ''~/.elvisrc'' can also be used to configure ''bbvi''.
  
 <file config ~$USER/.bboardrc> <file config ~$USER/.bboardrc>
Line 189: Line 228:
 </file> </file>
  
-== Learning to use Vi-style Editors: ==+=== Learning to use Vi-style Editors ===
  
 If you've never used a Vi-style editor you may wish to run the //vilearn(1)// command within your SDF shell session to get some practice. The Vi editor is //*modal*// - entering a Vi command such as //'i'// puts the editor in 'input' mode; pressing the //Esc// key puts the editor it back in 'command' mode. Within Vi, typing ':viusage' should display a summary of most Vi commands. If you've never used a Vi-style editor you may wish to run the //vilearn(1)// command within your SDF shell session to get some practice. The Vi editor is //*modal*// - entering a Vi command such as //'i'// puts the editor in 'input' mode; pressing the //Esc// key puts the editor it back in 'command' mode. Within Vi, typing ':viusage' should display a summary of most Vi commands.
Line 197: Line 236:
 If you decide to practice with elvis(1), the //':help'// command should provide an info(1)-like documentation environment (use //':q'// to close it). Keep in mind that this :help documentation is not available within bboard(1) as elvis(1) is run in a restricted command mode. More extensive elvis(1) documentation is on the main SDF hosts at ///usr/pkg/share/doc/elvis/elvis.html// . If you decide to practice with elvis(1), the //':help'// command should provide an info(1)-like documentation environment (use //':q'// to close it). Keep in mind that this :help documentation is not available within bboard(1) as elvis(1) is run in a restricted command mode. More extensive elvis(1) documentation is on the main SDF hosts at ///usr/pkg/share/doc/elvis/elvis.html// .
  
-== Running Spell-check on a bboard(1) Post in vi ==+=== Running Spell-check on a bboard(1) Post in vi ===
  
 Words deemed misspelled by the elvis(1) editor should appear in a different color. To spell-check the entire post, first move to position 1,1 with //'1G'// (or use the arrow keys, or //'h,j,k,l'// keys to navigate) then use //'gs'// to move to the first misspelled word. If spelling suggestions are available they'll appear numbered at the bottom of editing screen; to select, use //'#gs'//, where "#" is suggested word number. If no spelling suggestions are available, look the word up elsewhere, use //'cw'+[corrected word]+ESC// to correct, then //'gs'// to move to next misspelled word. Words deemed misspelled by the elvis(1) editor should appear in a different color. To spell-check the entire post, first move to position 1,1 with //'1G'// (or use the arrow keys, or //'h,j,k,l'// keys to navigate) then use //'gs'// to move to the first misspelled word. If spelling suggestions are available they'll appear numbered at the bottom of editing screen; to select, use //'#gs'//, where "#" is suggested word number. If no spelling suggestions are available, look the word up elsewhere, use //'cw'+[corrected word]+ESC// to correct, then //'gs'// to move to next misspelled word.
Line 212: Line 251:
 The words in your personal word file do not need to be sorted however all lowercase words are treated as case-insensitive; use uppercase if the distinction matters.  The wordfile words will be treated as "correct" by the spellchecker. The words in your personal word file do not need to be sorted however all lowercase words are treated as case-insensitive; use uppercase if the distinction matters.  The wordfile words will be treated as "correct" by the spellchecker.
  
-==== Make  bboard More Accessible ====+==== Make bboard More Accessible ====
  
 You may have luck with the settings below in your //.bboardrc//: You may have luck with the settings below in your //.bboardrc//:
bboard.1725317791.txt.gz · Last modified: 2024/09/02 22:56 by hc9