bin/170651: On 9.0-RELEASE#0 and master sh(1) gobbles high bit at first

[Mark Linimon]

The following reply was made to PR bin/170651; it has been noted by GNATS.

From: Mark Linimon <linimon at lonesome.com>
To: bug-followup at FreeBSD.org
Cc:  
Subject: Re: bin/170651: On 9.0-RELEASE#0 and master sh(1) gobbles high bit
 at first
Date: Sun, 19 Aug 2012 15:06:20 -0500

 ----- Forwarded message from "Steffen \"Daode\" Nurpmeso" <sdaoden at gmail.com> -----
 
 Date: Sun, 19 Aug 2012 21:08:11 +0200
 From: "Steffen \"Daode\" Nurpmeso" <sdaoden at gmail.com>
 To: freebsd-bugs at FreeBSD.org
 Cc: 
 Subject: Re: bin/170651: On 9.0-RELEASE#0 and master sh(1) gobbles high bit
 	at first
 User-Agent: S-nail <12.5 7/5/10;s-nail-9-g517ac44-dirty>
 
 Yet another update.
 I've #defined DEBUG_READ in libedit and actually found my problem.
 The reason why the german umlauts don't appear is that they actually
 result in "ed-unassigned" errors because of the input-to-command map.
 
 I'm using multi-platform multi-shell init scripts which i've just
 recently updated to be compatible to some pretty ancient
 Bourne-compatible shell, and now it turns out that the plain
 FreeBSD /bin/sh is classified as "NONE" type at all, so that no
 set command is used to configure shell behaviour upon startup.  I
 didn't think about this before, hmm.
 
 Anyway, once the login shell starts, it's a vanilla shell, but
 with emacs mode enabled, or at least this is what the '$ set -o'
 says which then also turns over all the ED_UNASSIGNED to ED_INSERT
 commands.  If nobody jumps into this here i'll try to figure out
 why, how and where that actually happens and fix it, maybe next week.
 Ciao,
 
 --steffen
 _______________________________________________
 freebsd-bugs at freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
 To unsubscribe, send any mail to "freebsd-bugs-unsubscribe at freebsd.org"
 
 ----- End forwarded message -----