Todd Lewis

@lentinj , I've geen investigating issues around supporting bracketed paste, and I'm coming up short on a fundamental question. There is no supported way for termcap/terminfo to indicate whether a...

If you're still interested, have a look at the [bracketed-paste](https://github.com/vigna/ne/tree/bracketed-paste) branch. `ne` has several things that you may want to act differently with bracketed paste besides `AutoIndent`. As it is,...

I've been warming to that approach as well: give a "probably what you want" sane default, and an easy way to customize with macros. I especially like the options you...

The bracketed-paste branch has been completely reworked to use macros as described above. Please give it a test drive at your convenience. (Still needs more doc updates I suppose.) If...

I've merged the `bracketed-paste` branch into master. If a user doesn't change the defaults, about the only difference she might notice is that pastes from the system clipboard no longer...

Probably off the other way, i.e. the _old_ range was `0x000..0x1ff`, and the two new `NE_KEY_BPASTE_BEGIN` and `NE_KEY_BPASTE_END` key codes were supposed to be `0x200` and `0x201` respectively. The fix...

Those `NE_KEY_BPASTE_BEGIN` and `NE_KEY_BPASTE_END` constants are fixed now; also fixed a refresh issue during macro execution, and a misplaced parenthesis in the `assert_buffer()` macro.

Mac much?

This is still happening on 2.6.6. Is there a way to get it to say _what_ is different? `Entry of github[xxxxxxxxxxxxxxxxx] contains conflicting changes - conflict resolution may lose data!`...

Mildly interesting related side note: The releases folders do not contain the `*.src.rpm` from which the individual binary rpms a built. Apparently it's treated as a build artifact and discarded,...