Graham Percival <gra...@percival-music.ca> writes: > On Tue, Jul 03, 2012 at 04:50:13PM +0200, David Kastrup wrote: >> Graham Percival <gra...@percival-music.ca> writes: >> >> > Good luck. >> >> My personal take on this is not to bother but disable use of the >> readline module if unavailable. git cl does not ask for interactive >> input often enough to make that worth the trouble. > > oh, that's a good thought! If the user supplied the relevant > config information in a text file, and git-cl just automatically > created a new issue if it couldn't find the old one (or better, if > git-cl wrote the issue number into ~/.git/config and used that one > instead of trying to rediscover it), then there'd be no need to > ask the user for anything at all.
Well, it can still ask using stdin: that just means that you'll have to backspace over errors destructively. And it does already start EDITOR for the initial description (rather than readline), so it is not like we are talking about multiline editing here. -- David Kastrup _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
