bindkey and 8 bit characters

bindkey and 8 bit characters

[Carl Johnson]

Hi all,
I'm trying to get zsh to understand meta characters so that i can do stuff like ...

bindkey -s '\M-v' 'vi *.{h,cpp}\n'

I know that X is getting the event because i can map meta-key plus up-arrow to
scroll up a line in an xterm, and i know zsh can display meta characters because...

print '\M-v'

prints what i expect...

this is the output of stty...

speed 9600 baud; 24 rows; 80 columns;
eucw 1:1:0:0, scrw 1:1:0:0:
intr = ^C; quit = ^\; erase = ^H; kill = ^U; eof = ^D; eol = ^@
eol2 = ^@; start = ^Q; stop = ^S; susp = ^Z; dsusp = ^Y; reprint = ^R
discard = ^O; werase = ^W; lnext = ^V
-parenb -parodd cs8 -cstopb hupcl cread -clocal -parext
-ignbrk brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl -iuclc
ixon -ixany ixoff imaxbel
isig icanon -xcase echo echoe echok -echonl -noflsh
-tostop echoctl -echoprt echoke -flusho -pending iexten
opost -olcuc onlcr -ocrnl -onocr -onlret -ofill -ofdel

i've set the XTerm resource...

*eightBitInput: true

and set the zsh option...

PRINT_EIGHT_BIT

I'm using zsh 4.2.6 (powerpc-ibm-aix5.3.0.0).

Anyone got any clues?
Cheers,
c


Disclaimer:

1. The contents of this email and its attachments are confidential and privileged. Any unauthorised use, or passing on, of the information to others who are not authorised is expressly prohibited. If you receive this email in error, please advise us and then delete the email with any attachments.

2. Before opening or using attachments, check them for viruses and defects. The contents of this email and its attachments may become scrambled, truncated or altered in transmission. Please advise us of any anomalies.

3. Racing & Wagering WA's liability  is limited to resupplying the email and attached files or the cost of having them resupplied.

4. The views represented in this email are those of the author and do not necessarily represent those of Racing & Wagering WA unless this is clearly indicated.

Re: bindkey and 8 bit characters

[Peter Stephenson]

"Carl Johnson" wrote:
> 
> Hi all,
> I'm trying to get zsh to understand meta characters so that i can do stuff =
> like ...
> 
> bindkey -s '\M-v' 'vi *.{h,cpp}\n'
> 
> I know that X is getting the event because i can map meta-key plus up-arrow
> to scroll up a line in an xterm, and i know zsh can display meta
> characters because...
> 
> print '\M-v'
> 
> prints what i expect...

It's still possible, even given what you've tried, that xterm isn't
sending the sequence you expect to the terminal.  What happens if you type
"read<Enter>" and then Meta-v, does anything show up on the terminal?
If not, xterm is probably still unconvinced about what to do with it.
If it does, you should be able to bind it, although it might not be an
ASCII v with the 8th bit set as you'd expect.

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
Cambridge, CB4 0WZ, UK                          Tel: +44 (0)1223 692070


.

RE: bindkey and 8 bit characters

[Carl Johnson]

Peter Stephenson wrote:
>"Carl Johnson" wrote:
>>
>> Hi all,
>> I'm trying to get zsh to understand meta characters so that i can do stuff =
>> like ...
>>
>> bindkey -s '\M-v' 'vi *.{h,cpp}\n'
>>
>> I know that X is getting the event because i can map meta-key plus up-arrow
>> to scroll up a line in an xterm, and i know zsh can display meta
>> characters because...
>>
>> print '\M-v'
>>
>> prints what i expect...
>
>It's still possible, even given what you've tried, that xterm isn't
>sending the sequence you expect to the terminal.  What happens if you type
>"read<Enter>" and then Meta-v, does anything show up on the terminal?

nope nothing.

>If not, xterm is probably still unconvinced about what to do with it.

ok, i'll go digging on google to see if i can find anything else
that xterm needs (other than eightBitInput: true).

thanks for the reply.
cheers,
c

Disclaimer:

1. The contents of this email and its attachments are confidential and privileged. Any unauthorised use, or passing on, of the information to others who are not authorised is expressly prohibited. If you receive this email in error, please advise us and then delete the email with any attachments.

2. Before opening or using attachments, check them for viruses and defects. The contents of this email and its attachments may become scrambled, truncated or altered in transmission. Please advise us of any anomalies.

3. Racing & Wagering WA's liability  is limited to resupplying the email and attached files or the cost of having them resupplied.

4. The views represented in this email are those of the author and do not necessarily represent those of Racing & Wagering WA unless this is clearly indicated.

RE: bindkey and 8 bit characters

[Carl Johnson]

Hi all,
Just in case anyone else ever hits this "problem", the solution was to...

xmodmap -e "keysym Alt_L = Meta_L Alt_L"
xmodmap -e "keysym Alt_R = Meta_R Alt_R"

Cheers,
c


-----Original Message-----
From: Carl Johnson [mailto:carl.johnson@rwwa.com.au]
Sent: Friday, 14 September 2007 11:56 AM
To: zsh-users@sunsite.dk
Subject: RE: bindkey and 8 bit characters



Peter Stephenson wrote:
>"Carl Johnson" wrote:
>>
>> Hi all,
>> I'm trying to get zsh to understand meta characters so that i can do stuff =
>> like ...
>>
>> bindkey -s '\M-v' 'vi *.{h,cpp}\n'
>>
>> I know that X is getting the event because i can map meta-key plus up-arrow
>> to scroll up a line in an xterm, and i know zsh can display meta
>> characters because...
>>
>> print '\M-v'
>>
>> prints what i expect...
>
>It's still possible, even given what you've tried, that xterm isn't
>sending the sequence you expect to the terminal.  What happens if you type
>"read<Enter>" and then Meta-v, does anything show up on the terminal?

nope nothing.

>If not, xterm is probably still unconvinced about what to do with it.

ok, i'll go digging on google to see if i can find anything else
that xterm needs (other than eightBitInput: true).

thanks for the reply.
cheers,
c

Disclaimer:

1. The contents of this email and its attachments are confidential and privileged. Any unauthorised use, or passing on, of the information to others who are not authorised is expressly prohibited. If you receive this email in error, please advise us and then delete the email with any attachments.

2. Before opening or using attachments, check them for viruses and defects. The contents of this email and its attachments may become scrambled, truncated or altered in transmission. Please advise us of any anomalies.

3. Racing & Wagering WA's liability  is limited to resupplying the email and attached files or the cost of having them resupplied.

4. The views represented in this email are those of the author and do not necessarily represent those of Racing & Wagering WA unless this is clearly indicated.