Both sides previous revisionPrevious revision | |
bboard [2025/03/04 19:50] – clean up, added FORWARD and BACK descriptions peteyboy | bboard [2025/03/14 20:04] (current) – turns out you can't change the editor to nano :( Fixed the 'change default editor' section peteyboy |
---|
==== 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> | </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. |
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. |