On 5 November 2010 18:30, Jonathan Nieder <jrnie...@gmail.com> wrote:
[Sorry for not understanding what you were after.] > Sven Joachim wrote: > > | Now after reading #574396 I see that with the xterm resources > | > | xterm*metaSendsEscape: false > | xterm*eightBitInput: false > | > | and bash as shell meta-key combinations yield non-ASCII characters, This I do not understand. "metaSendsEscape" defaults to false, and it is precisely to obtain ASCII characters (e.g. Meta-p is sent as ESC P) that one sets eightBitInput to false. With these two settings false, only 7-bit ASCII characters are sent! (Setting either metaSendsEscape to true or eightBitInput to false has the result that only 7-bit ASCII is sent.) > I guess we can rely on people to keep the default of metaSendsEscape? Well, if they don't, they will have read the docs. > Or perhaps a note in README.Debian would be needed to warn people. > If you know what to do, please provide a patch. :) Otherwise, thoughts > welcome. What is wrong with patching xterm so that it defaults to eightBitInput being false rather than true, as other terminals do? I would like to see what Thomas Dickey thinks, in any case (Thomas, I hope you don't mind the Cc:; see http://bugs.debian.org/326200 for the rest of this thread.). -- http://rrt.sc3d.org -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlkti=x283c34kxiriz+6gen4gbw+îkrobym-3...@mail.gmail.com
