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

[Chris Allegretta]

Keeping on-list in case future folks run into the same issue.

Hmm, I installed the brew suite and ^space still works in 2.2.6.  Now
it's going to have to be something more subtle.  Can you let me know:

output of: brew info ncurses
Version of OS X you're using?
Any special keyboard type selected?

On 11/24/13, The Kabal <address@hidden> wrote:
> Hello,
>
> No worries about the timing, glad to have you look into it.
>
> $TERM is xterm-256color. I'm using iTerm, but since you asked, I tested in
> regular Terminal.app as well, and get the same behavior I reported (2.0.6
> goes to the next word, 2.2.6 gives 'unknown command').
>
> Homebrew (http://brew.sh/) uses a recipe (
> https://github.com/Homebrew/homebrew-dupes/blob/master/nano.rb ) ,
> downloads 2.2.6, and then compiles it from source.
>
> This might help further, the brew info for the package:
>
> $ brew info nano
> nano: stable 2.2.6
> http://www.nano-editor.org/
> /usr/local/Cellar/nano/2.2.6 (42 files, 492K) *
> From: https://github.com/homebrew/homebrew-dupes/commits/master/nano.rb
> ==> Dependencies
> Required: homebrew/dupes/ncurses ✔
>
> I'm happy to send anything else that will help repro the bug.
>
> Thanks,
> Patrick
>
>
> On Sat, Nov 23, 2013 at 10:16 PM, Chris Allegretta <address@hidden> wrote:
>
>> ...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
>> >>
>> >
>>
>