Cool, thanks for working on this stuff. I meant to mention before but when you send patches could you please either:
a) send one patch for one change, ie don't split them up with so much granularity, eg man page change can be in the same diff file as the code. b) or if you prefer, give each set of patches a different prefix. I tend to want to save everything to disk then go look at it and apply it and it's hard when I end up with multiple files all called 0001* and 0002* and no indication of which 0001 goes with which 0002. Cheers On Fri, Dec 02, 2011 at 12:24:00AM -0500, Ben Boeckel wrote: > Hi, > > Another handful of features incoming[1]. Not all are ready[2], but some > are. The branches are as follows: > > dev/add-WORD-motions-to-status > Adds 'B', 'E', and 'W' motions to edit mode. Not sure of emacs > equivalents. > > dev/add-line-insert > Adds 'A' and 'I' bindings for vi in edit mode. Not sure of emacs > equivalents. > > dev/add-till-movement (SENT in another thread) > Adds 't' and 'T' motions to copy mode. I'm unsure of the emacs > equivalent bindings for these. Also contains bindings for 'x' > and 'X' in edit mode for vi. Again, not sure of emacs > equivalents. There's an extra commit that does the groundwork > for the 't' and 'T' bindings in edit mode, but there's no way to > get the target character without being silent or recursing in > the status line. > > dev/fix-vi-motion-targets (BUGGY) > Fixes 'e' and 'E' motions to have vi-like behavior if the > respective table is set for copy and edit modes. > > dev/use-format-tree-in-display (NEEDS DOCS) > Allow formatting like list-* commands in the statusline (client > and session formats globally) and display-message (which also > adds the window and pane formats). > > dev/features > Integration branch with all of the above merged in. This is what > I'm using on my development machines. > > I'd like to get testing for these besides my use. Also input from emacs > users as to what the equivalent bindings for some of the vi bindings > are. Also master is a bit behind. > > Fair warning: I rebase feature branches (especially since master grabs > the patches as slightly different sometimes and rebasing to resolve > what's been merged is easiest). There are also quite a few merge > conflicts among the branches because quite a few poke at edit mode > bindings. > > --Ben > > [1]http://git.benboeckel.net/patches/tmux.git/ > [2]There's some weird bugs with word motions in particular with the fix > to make it follow the vi convention of ending on the last character of a > word instead of the character after the word. There's also some > weirdness in the status line with word motions. > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure > contains a definitive record of customers, application performance, > security threats, fraudulent activity, and more. Splunk takes this > data and makes sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-novd2d > _______________________________________________ > tmux-users mailing list > tmux-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/tmux-users ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ tmux-users mailing list tmux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tmux-users
