nul character ^@ (set-mark-command) binding ignored

nul character ^@ (set-mark-command) binding ignored

[Rodger Anderson]

I'm having problems with the nul character, ^@, which is normally
bound to set-mark-command.  It appears that the nul character is being
ignored.

I've verified that I *can* send the nul character via cat -v.  With my
current keyboard in an xterm, I can use shift-control-2 (control-@) or
control-spacebar.

I've verified that the set-mark-command works by setting it to another
character via the bindkey command: bindkey "^Z" set-mark-command.

I can bind ^@ to other commands, but they don't get executed either
when I press control-spacebar.

This is with version 2.5.03.  My OS is HP-UX 9.05 on 9000/715.

Version 2.3.1 works as expected.

This seems like a rather strange problem, as I've not seen any mention
of it on zsh-users mailing list before.  Doesn't anyone else have this
problem?

Rodger Anderson

Re: nul character ^@ (set-mark-command) binding ignored

[Philip Kizer]

Rodger Anderson <rodger@hpbs2245.boi.hp.com> wrote:
>I can bind ^@ to other commands, but they don't get executed either
>when I press control-spacebar.

Did you try, for instance:

  bindkey '\000' down-case-word


I just tested this with shells back to 2.5.0 and up to 2.6b10.


Good luck,
philip

____________________________________________________________ Philip Kizer ___
Texas A&M CIS Operating Systems Group, Unix ( 409.862.4120 ) pckizer@tamu.edu

"Relying on the government to protect your privacy is like asking a peeping
tom to install your window blinds." -John Perry Barlow, EFF co-founder

Re: nul character ^@ (set-mark-command) binding ignored

[Rodger Anderson]

> Did you try, for instance:
> 
>   bindkey '\000' down-case-word

Ok, just tried it.  It does not work.  The command shows up in the
list:

  bindkey | head -1
  "^@"    down-case-word

but nothing happens when I send that character.  It is as if something
somewhere along the input chain is swallowing up that particular
character.  It would seem to be in the zsh chain, as when I run the
command cat -v and press control-space a few times:

  cat -v

  ^@^@^@

In another experiment, I tried to use ^V to escape the ^@ and put the
nul character into the command: no go.  The control-V escapes whatever
character I type *after* the control-@.  If I type control-V,
control-space, then carriage-return, I get ^M on the command line.
The nul character is just swallowed up and ignored.

I'm wondering if it is something with the way zsh interacts with the
HP-UX tty driver?  Doesn't anyone else running HP-UX 9.05 experience
this problem?

Here is the output of stty -g:

502:5:b50:3b:0:3:1c:8:7:4:a:0:1e:502:5:b50:8000003b:3:1c:8:7:4:a:0:1e:ff:ff:ff:4:a:1a:11:13:0:0:1a:ff:0:30:50

If you run the stty command with this as an argument (on HP-UX, at
least), you will end up with the same exact stty settings that I have.
If someone else running HP-UX 9.05 (and doesn't have this problem)
could run stty -g and send me the results, then I could try those
settings and see if problem goes away.

Rodger

Re: nul character ^@ (set-mark-command) binding ignored

[Rodger Anderson]

> Did you try, for instance:
> 
>   bindkey '\000' down-case-word

Ok, just tried it.  It does not work.  The command shows up in the
list:

  bindkey | head -1
  "^@"    down-case-word

but nothing happens when I send that character.  It is as if something
somewhere along the input chain is swallowing up that particular
character.  It would seem to be in the zsh chain, as when I run the
command cat -v and press control-space a few times:

  cat -v

  ^@^@^@

In another experiment, I tried to use ^V to escape the ^@ and put the
nul character into the command: no go.  The control-V escapes whatever
character I type *after* the control-@.  If I type control-V,
control-space, then carriage-return, I get ^M on the command line.
The nul character is just swallowed up and ignored.

I'm wondering if it is something with the way zsh interacts with the
HP-UX tty driver?  Doesn't anyone else running HP-UX 9.05 experience
this problem?

Here is the output of stty -g:

502:5:b50:3b:0:3:1c:8:7:4:a:0:1e:502:5:b50:8000003b:3:1c:8:7:4:a:0:1e:ff:ff:ff:4:a:1a:11:13:0:0:1a:ff:0:30:50

If you run the stty command with this as an argument (on HP-UX, at
least), you will end up with the same exact stty settings that I have.
If someone else running HP-UX 9.05 (and doesn't have this problem)
could run stty -g and send me the results, then I could try those
settings and see if problem goes away.

Rodger