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
Next revisionBoth sides next revision
bboard [2021/03/08 07:06] – [Post a message/reply] hc9bboard [2024/02/23 20:23] – [Some relevant bboards] mcornick
Line 5: Line 5:
 ===== Some relevant bboards ===== ===== Some relevant bboards =====
  
-  * To ask for help, use **''<HELPDESK>''** to have your query answered by another user +  * To ask for help **from another user**, use **''<HELPDESK>''** to have your query answered **by another user (admins do //NOT// read <HELPDESK>)** 
-  * All system notices are posted on **''<ANNOUNCE>''**+  * All system notices are posted on **''<ANNOUNCE>''** (read this first if something is wrong)
   * Current discussions about SDF-EU happen on **''<SDFEU>''**   * Current discussions about SDF-EU happen on **''<SDFEU>''**
-  * You can make requests for new software and discuss account issues at **''<REQUESTS>''**+  * You can make requests for new software and discuss account issues at **''<REQUESTS>''** (if your request is about your account and is confidential, better to **mail membership@sdf.org**)
   * **''<ARPA>''** and **''<META>''** boards are used for ARPA and MetaARPA related questions.   * **''<ARPA>''** and **''<META>''** boards are used for ARPA and MetaARPA related questions.
   * Member services (such as VPN or VOIP) have their own board for questions and support.   * Member services (such as VPN or VOIP) have their own board for questions and support.
Line 88: Line 88:
    REPLY to "Meetup at EuroBSDcon" ? (y/n)    REPLY to "Meetup at EuroBSDcon" ? (y/n)
    You have replied:    You have replied:
-   ------------------------------------------------------+   -----------------------------------------------------------
    I would love to!    I would love to!
 +   
    This BULLETIN contains 16 characters in 4 words of 2 lines.    This BULLETIN contains 16 characters in 4 words of 2 lines.
    -----------------------------------------------------------    -----------------------------------------------------------
-   POST your REPLY? (y/n) |+   POST your REPLY? (y/n)
  
 ==== ...and much more ==== ==== ...and much more ====
Line 130: Line 131:
 ===== Customizing bboard(1) =====  ===== Customizing bboard(1) ===== 
  
-* For bboard options, check the "bboard" man page via the **man bboard** command at the shell prompt.*+* 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 ====
  
-==== Change default editor to a better pico ====+  * "(N)ew SCAN"--that is, the ''N'' command-- scans the current BBOARD for NEW messages 
 +  * "(n)ew SCAN"--that is, the ''n'' command--scans all boards that are not on your kill list for new messages. 
 + 
 +The purpose of the kill list is to "unsubscribe" from boards you don't want  
 +to scan with the ''n'' command. Go to the board you want to ignore and type ''K'' to add it to your kill list. The next time you use "(n)ew SCAN", that board, along with any other ones already on your kill list, will not be scanned for new messages. 
 + 
 +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. 
 + 
 + 
 +==== Change default editor ==== 
 + 
 +=== Change to a better pico ====
  
 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. 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.
  
-To do this, instead of setting up your //.bboardrc// as above, set it as follows (you can do this with //nano ~/.bboardrc//!):+To do this, instead of setting up your //.bboardrc// as above, set it as follows (you can do this with ''nano ~/.bboardrc''!):
  
 <file config ~$USER/.bboardrc> <file config ~$USER/.bboardrc>
Line 144: Line 157:
 </file> </file>
  
-==== Changing the default editor to vi ====+=== Changing the default editor to vi ===
  
 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> 
  
-  " set auto-wrap width:"+<file vim ~$USER/.exrc> 
 +  " " set auto-wrap width:
   set textwidth=78   set textwidth=78
-  " set RH margin guide:"+  " " set RH margin guide:
   set guidewidth=79   set guidewidth=79
-  " set elvis spellcheck stuff:"+  " " set elvis spellcheck stuff:
   set spell   set spell
   set spelldict=/usr/share/dict/words   set spelldict=/usr/share/dict/words
Line 160: Line 173:
  
 <file config ~$USER/.bboardrc> <file config ~$USER/.bboardrc>
- 
   # set editor to vi (will use elvis(1) editor):   # set editor to vi (will use elvis(1) editor):
   EDITOR=vi   EDITOR=vi
Line 167: Line 179:
 </file> </file>
  
-Once these files are in place your bboard(1) post editing environment will be elvis(1) based (a Vi editor clone; see **man elvis**) and should display a highlighted right-hand margin guide at 79 characters over, with text wrapping at 78 characters over. Note that these //~/.exrc// settings may adversely affect other Vi-style editors like nvi(1) or vim(1).+Once these files are in place your bboard(1) post editing environment will be elvis(1) based (a Vi editor clone; see **man elvis**) and should display a highlighted right-hand margin guide at 79 characters over, with text wrapping at 78 characters over. Note that these //~/.exrc// settings may adversely affect other Vi-style editors like nvi(1) or vim(1). If you don't like the current color scheme alternatives are possible; type //:color// within ''bbvi'' to see current settings and appropriate syntax.
  
 If you have problems with screen colors (black-on-black), you can also add ''COLOR=NIL'' to your ''.bboardrc'' file, or update ''.elvisrc'' to include: If you have problems with screen colors (black-on-black), you can also add ''COLOR=NIL'' to your ''.bboardrc'' file, or update ''.elvisrc'' to include:
Line 175: Line 187:
         color normal white         color normal white
 </file> </file>
-==== Running Spell-check on a bboard(1) Post: ==== 
  
-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. 
  
-When finished editing your bboard(1) post use //'ZZ'// to quit. If you wish to cancel your post use //':q!'// to quit without saving. +== 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 188: Line 196:
  
 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 ==
 +
 +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.
 +
 +When finished editing your bboard(1) post use //'ZZ'// to quit. If you wish to cancel your post use //':q!'// to quit without saving.
 +
 +If you find the spellchecker is frequently flagging words inappropriately you can create a personal word list, for example ''~/.mywords'', then add the following to your ''~/.exrc'' file:
 +
 +<file vim ~$USER/.exrc>
 +" " personal word list:
 +wordfile .mywords
 +</file>
 +
 +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 ====
 +You may have luck with the settings below in your //.bboardrc//:
 +
 +<file config ~$USER/.bboardrc>
 + AUTOLIST=NIL
 + CHARTER=NIL
 + CLEAR=NIL
 + COLOR=NIL
 +</file>
  
 ---- ----
 [[http://sdf.org/?tutorials/bboard-tutorial | bboard tutorial]] - legacy link [[http://sdf.org/?tutorials/bboard-tutorial | bboard tutorial]] - legacy link
bboard.txt · Last modified: 2024/02/25 22:18 by hc9