Re: readline dynamic library configuration for cygwin
> > Both support/shobj-conf and shlib-install have sections added for cygwin, > then shlib/Makefile.in and configure.in are updated to propogate the new > variables in shobj-conf. shlib/Makefile.in is also patched to pass > $(bindir) on to shlib-install, since cygwin needs to know both bindir and > libdir. Followup - this modification to my previous posting lets ./configure choose between -ltermcap vs -lcurses on cygwin, rather than assuming --with-curses. > --- readline-5.1-alpha1.orig/support/shobj-conf 2005-08-04 06:56:47.561375000 -0600 > +++ readline-5.1-alpha1/support/shobj-conf2005-08-06 15:03:02.389125000 - 0600 > -466,6 +468,23 > SHLIB_STATUS=unsupported > ;; > > +cygwin*) ... > + SHLIB_LIBS=-lcurses SHLIB_LIBS='$(TERMCAP_LIB)' -- Eric Blake ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
Re: stty settings override ~/.inputrc?
Chet Ramey <[EMAIL PROTECTED]> wrote: > Readline, beginning with version 5.0, reads the stty special character > settings and binds them to their readline equivalents each time > readline() is called. It reads ~/.inputrc once per `program'. Suggestion: when reading .inputrc, update the stty settings to match as closely as possible, so that re-reading the same stty settings for the next command won't change anything. That way, .inputrc wins (persistently) over the original stty settings, but later changes to stty settings still win over .inputrc. paul ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
Re: stty settings override ~/.inputrc?
Paul Jarc wrote: > Chet Ramey <[EMAIL PROTECTED]> wrote: > >>Readline, beginning with version 5.0, reads the stty special character >>settings and binds them to their readline equivalents each time >>readline() is called. It reads ~/.inputrc once per `program'. > > > Suggestion: when reading .inputrc, update the stty settings to match > as closely as possible, so that re-reading the same stty settings for > the next command won't change anything. That way, .inputrc wins > (persistently) over the original stty settings, but later changes to > stty settings still win over .inputrc. Readline should never change the user's persistent terminal settings without his knowledge. Users have a right to expect that changes will only be made by them calling `stty' or one of its siblings. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ( ``Discere est Dolere'' -- chet ) Live...Laugh...Love Chet Ramey, ITS, CWRU[EMAIL PROTECTED]http://tiswww.tis.case.edu/~chet/ ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
