Am 15.10.2015 um 12:11 schrieb Johannes Schindelin: > > This is all technically sound. From a usability perspective I would wish > more for a way to exclude or filter the lines by a pattern. Why not do both? The only thing that is unfortunate is that the "/" already is a command. Which would point to either a solution along the lines of "s<range>" being the split-by-line and "s/" being the split-by-regex? Or is this an argument for introducing yet another interaction mode entered when "s" fails to split further -- with simple "/" and "<range>" being the options in that mode. Regards, Sven Helmberger -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html