Re: [nail-devel] Line editing capabilities
Brought to you by:
gritter
From: Steffen D. N. <sd...@gm...> - 2013-07-19 14:04:46
|
Hi list, ||| * basic line editing capabilities ||| * history ||| * tab completion for commands / folders. [.] | WANT_EDITLINE=0 WANT_EDITLINE_READLINE=0 | In user.conf, to be turned on explicitly. The latter requires [.] | NAIL_HISTFILE [.] | prompt | The prompt is now passed through an escape sequence expander [.] |Give me yet another week to do testing in respect to signals and |interruption, do some more cleanup, and integrate the mentioned |hetio code for the case when we don't have editline/readline. |Then even the less brave ones may give it a shot. Sorry, but this won't suffice, i need more time. The hetio code doesn't deal with multibyte and visual character width, so i have to reinvent the wheel. I think i can make it until tomorrow evening, but this will be a first working version, not the promised thing for the less brave. If you have updated last weekend then simply don't update until i notify the list that i'm done. There is one bug in the code you have, then, and that is that we install a SIGCONT handler. Luckily :) that doesn't matter in command line mode because i think i have placed the _reset_on_stop=0 just before the readline_input() (lex.c:commands()), so that we won't jump at all. It's a plain bug in compose mode. (What happens is that a siglongjmp(3) is performed but the SIGCONT signal handler runs *afterwards*, and updates the screen; it seems that both of editline(3) and readline(3) are forgiving here, *however*.) All of that (and more) is already tweaked on *next*, but the fallback builtin editor simply isn't ready for anything. Because some of you really use the *next* branch actually i will add yet another branch for speculative working, named *crawl*. You know, i do (mis)use the Sourceforge repo as a backup media and thus push quite often, which results in an unusable *next*. To overcome this i've decided to add *crawl* and only update *next* when we have a quite stable situation, as, e.g., last sunday. Or say, at least nothing completely non-working, as the builtin fallback editor is right now. So long and ciao, --steffen |