Re: [Help-nano] nano differences from 2.0.6 to 2.2.6

[Chris Allegretta]

...or a week later.  Apologies for that.

Hmm, having finally figured how to get gcc and the command line tools
on my mac again, compiling nano from source, I find that 2.2.6 does
just what I'd expect when I hit ^Space, no ket bindings needed...

Couple questions here to see what's going on
Whats your $TERM set to?
Are you using the std mac Terminal program?
Is this homebrew version you're using just a binary, a source build
tool like Fink, the official nano source, or something else?

On 11/16/13, Chris Allegretta <address@hidden> wrote:
> Hey Patrick, that sounds like a bug.  I'll take a look on my mac
> tonight or tomorrow.  Thanks for the report!
>
> On 11/15/13, The Kabal <address@hidden> wrote:
>> Hello!
>>
>> In nano 2.0.6 (as shipped with OS X), Control-Space seems to default to
>> "move cursor to next word". However, when I install the homebrew version
>> of
>> 2.2.6, it appears to not be setup to do so.
>>
>> No worries, I thought, and pulled up the documentation, and found that
>> the
>> nanorc setting for that would seem to be "nextword". So I try a nanorc
>> with
>> a setting:
>>
>> bind ^Space nextword all
>>
>> But launching homebrew's nano 2.2.6 gives me 'Could not map name
>> "nextword"
>> to a function'.
>>
>> How do I get the same behavior in 2.2.6, that I had in 2.0.6, where
>> Control-space will move the cursor to the next word?
>>
>> Thanks for an awesome editor!
>> Patrick
>>
>