bboard
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
bboard [2021/03/08 07:08] – [Post a message/reply] hc9 | bboard [2022/08/11 16:49] – Added more accessible section, re-sectioned changing editor sections peteyboy | ||
---|---|---|---|
Line 131: | Line 131: | ||
===== Customizing bboard(1) ===== | ===== Customizing bboard(1) ===== | ||
- | * For bboard options, check the "bboard" | + | * For bboard options, check the '' |
+ | ==== How to Use new SCAN and KILL Commands ==== | ||
- | ==== Change default editor to a better pico ==== | + | * "(N)ew SCAN" |
+ | * "(n)ew SCAN" | ||
+ | |||
+ | The purpose of the kill list is to " | ||
+ | to scan with the '' | ||
+ | |||
+ | To remove a previously killed board from the list and start scanning it for new posts again, '' | ||
+ | |||
+ | |||
+ | ==== Change default editor | ||
+ | |||
+ | === Chang 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 // | + | To do this, instead of setting up your // |
<file config ~$USER/ | <file config ~$USER/ | ||
Line 145: | Line 157: | ||
</ | </ | ||
- | ==== 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 // | 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 // | ||
- | <file vim ~$USER/ | ||
- | | + | <file vim ~$USER/ |
+ | " | ||
set textwidth=78 | set textwidth=78 | ||
- | " set RH margin guide:" | + | |
set guidewidth=79 | set guidewidth=79 | ||
- | " set elvis spellcheck stuff:" | + | |
set spell | set spell | ||
set spelldict=/ | set spelldict=/ | ||
Line 161: | Line 173: | ||
<file config ~$USER/ | <file config ~$USER/ | ||
- | |||
# set editor to vi (will use elvis(1) editor): | # set editor to vi (will use elvis(1) editor): | ||
EDITOR=vi | EDITOR=vi | ||
Line 168: | Line 179: | ||
</ | </ | ||
- | 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 '' |
If you have problems with screen colors (black-on-black), | If you have problems with screen colors (black-on-black), | ||
Line 176: | Line 187: | ||
color normal white | color normal white | ||
</ | </ | ||
- | ==== 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 //' | ||
- | |||
- | When finished editing your bboard(1) post use //' | ||
- | ==== 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 // | If you've never used a Vi-style editor you may wish to run the // | ||
Line 189: | Line 196: | ||
If you decide to practice with elvis(1), the //': | If you decide to practice with elvis(1), the //': | ||
+ | |||
+ | |||
+ | == 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 //' | ||
+ | |||
+ | When finished editing your bboard(1) post use //' | ||
+ | |||
+ | If you find the spellchecker is frequently flagging words inappropriately you can create a personal word list, for example '' | ||
+ | |||
+ | <file vim ~$USER/ | ||
+ | " " personal word list: | ||
+ | wordfile .mywords | ||
+ | </ | ||
+ | |||
+ | The words in your personal word file do not need to be sorted however all lowercase words are treated as case-insensitive; | ||
+ | |||
+ | |||
+ | ==== Make bboard More Accessible ==== | ||
+ | You may have luck with the settings below in your // | ||
+ | |||
+ | <file config ~$USER/ | ||
+ | | ||
+ | | ||
+ | | ||
+ | | ||
+ | </ | ||
---- | ---- | ||
[[http:// | [[http:// |
bboard.txt · Last modified: 2024/09/02 22:56 by hc9