Re: editors and spell checking?

My pico is edition 5.0 plus.
Pico is more flexible, speaking personally.
nano, again speaking personally makes odd choices, like going to the end 
of a a document.
The recent nano on the Ubuntu setup for dreamhost no longer even uses the 
control t for spell checking.
Personal preferences are the soul of personal computing laughs.



On Wed, 3 Apr 2024, [email protected] wrote:

> Pico and nano are basically the same editor, just a later version, (you know, 
> pico is version 1.0, nano is version 2.0).
>
> The way to run aspell or spell is exactly the same regardless of the name of 
> the editor in this case.
>
> ctrl-t asks you what program to run, type spell or aspell, depending on what 
> you have installed, and you're all done.
>
> That's all there is to it.
>
> And, just for reference, Nano uses the same exact keystrokes as pico, I know, 
> because I used pico for years before it got switched to nano, and I've not 
> changed a single thing in how I use the program, and it still does everything 
> exactly the same as it did before.
>
> No difference.
>
>
> On 4/2/2024 11:25 PM, Karen Lewellen wrote:
>>  apparently?
>>  There is more to this  solution, at least where the speller is concerned.
>>  the editor in lynx in use is pico..cannot fault them there, I prefer it to
>>  nano as well.
>>  Alpine in their setup is using aspell for spell checking, so they want to
>>  add this on the  editor line.
>>  Pico runs fine by itself when added to the editor line in  the lynx
>>  options menu.  but it does not seem to provide   things like
>>  alternative words, or look up or anything as if a speller was in
>>  use...meaning something  else is required.
>>  Apparently adding the line as it appears in the alpine setup screen is not
>>  working either.
>>  Does pico need a configuration file to run with a spell checker?
>>  thanks,
>>  Karen
>> 
>>
>>  On Tue, 2 Apr 2024, Tim Chase wrote:
>> 
>> >  Replying inline
>> > 
>> >  On 2024-04-02 15:33, Karen Lewellen wrote:
>> > >  I am helping someone resolve an issue, they have access to lynx, but 
>> > >  the
>> > >  editor field is blank.
>> > >  They are using Ubuntu.
>> > 
>> >  If they're already comfortable with a preferred editor, you can
>> >  tell Lynx to use that on the command-line with the "-editor" option:
>> > 
>> >   $ lynx -editor=/usr/bin/nano http://example.com
>> > 
>> >  They might even have configured their system to use "sensible-editor"
>> >  in which case
>> > 
>> >   $ lynx -editor=/usr/bin/sensible-editor http://example.com
>> > 
>> >  should invoke their preferred editor.
>> > 
>> >  Alternatively, you can use "o" to go to the lynx options, check the
>> >  "Save options to disk" checkbox, set the Editor value in there, and
>> >  save the options.
>> > 
>> >  Strangely, lynx doesn't honor the common method of setting either
>> >  the $EDITOR or $VISUAL environment variable.
>> > 
>> > >  In alpine for example there is a field for editor, and one for spell
>> > >  checking, I admit to thinking they worked together as in are software
>> > >  dependent.
>> > 
>> >  They can be the same thing or they can be different tools.  Some
>> >  editors have spell-check support, some don't; so you might want an
>> >  external spell-checker.
>> > 
>> > >  Does lynx work the same?  meaning does there need to be one field
>> > >  for the editor and one for spell checker?
>> > 
>> >  I don't think lynx has anything spell-checking-related, just
>> >  editor-related.  However, if they use an editor with built-in
>> >  spell-checking, that would do the trick.
>> > 
>> > >  or is it enough to make sure the chosen editor is configured
>> > >  to use the desired spell checker.  meaning adding the editor will
>> > >  allow for spell checking as well?
>> > 
>> >  I believe this is the case.  I know that vim and emacs both have
>> >  support for spell-checking.  And nano does too if you enable it and
>> >  add a spell-checking package:
>> > 
>> >   $ sudo apt-get install spell
>> > 
>> >  With the spell-checker installed, you should be able to use control+t
>> >  in nano to spell-check the file.
>> > 
>> >  Hopefully that helps,
>> > 
>> >  -tim
>> > 
>> > 
>> > 
>> > 
>> > 
>> > 
>> > 
>> 
>