zsh-workers
 help / color / mirror / code / Atom feed
From: "Jun T." <takimoto-j@kba.biglobe.ne.jp>
To: zsh-workers@zsh.org
Subject: Re: PATCH: key bindings, fixes, docs, tests for vi stuff
Date: Sat, 22 Nov 2014 00:20:25 +0900	[thread overview]
Message-ID: <AA05CB16-67A9-4476-ADC5-6186C76CFCE3@kba.biglobe.ne.jp> (raw)
In-Reply-To: <15511.1416528068@thecus.kiddle.eu>

2014/11/21 09:01, Oliver Kiddle <okiddle@yahoo.co.uk> wrote:

> On 18 Nov, "Jun T." wrote:
>> Apparently 'daw' is not working.
> 
> With this patch, that test failure should now be fixed.

Yes, it has been fixed.
But now I get another failure on my Mac:

*** 1,2 ****
! BUFFER: X `one`X $(echo two)X" three "X$'four'XfiveX${six:-6}
  CURSOR: 0
--- 1,2 ----
! BUFFER: X `one`X $(echo two)X" three "X$'four'fiveX${six:-6}
  CURSOR: 0
Test ./X02zlevi.ztst failed: output differs from expected as shown above for:
  zletest $'  `one`  $(echo two) " three " $\'four\'\C-v\tfive ${six:-6}\e' \
      vaaom{a,b,c,d,e,f}v \`{a,b,c,d,e,f}rX
Was testing: all argument for different arguments

This is due to that ^V is interpreted as the 'lnext' control character
by the slave tty. 
Yet another ad hoc workaround is to modify line 37 of Test/comptest to

stty 38400 columns 80 rows 24 tabs werase undef lnext undef

Here, 'lnext undef' can be replaced by '-iexten'.
Surprisingly (at least to me), 'werase undef' can also be replaced by
'-icanon' for the tests including '^W' to succeed:

stty 38400 columns 80 rows 24 tabs -icanon -iexten

'bindkey -r "\e~"' is still required for the test 'swap case on a blank line'
to succeed.

Jun


      parent reply	other threads:[~2014-11-21 15:20 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-17 21:36 Oliver Kiddle
2014-11-18  8:04 ` Jun T.
2014-11-19  8:48   ` Oliver Kiddle
2014-11-19 15:35     ` Ray Andrews
2014-11-21  0:01   ` Oliver Kiddle
2014-11-21  0:49     ` Bart Schaefer
2014-11-21  1:10       ` Ray Andrews
2014-11-21  5:53         ` Bart Schaefer
2014-11-21 10:35       ` Oliver Kiddle
2014-11-22  6:59         ` Bart Schaefer
2014-12-12 16:47           ` Oliver Kiddle
2014-11-21  1:15     ` Ray Andrews
2014-11-21  2:20       ` Mikael Magnusson
2014-11-21  2:38         ` Ray Andrews
2014-11-21  6:23           ` Bart Schaefer
2014-11-21 17:28             ` trouble with debugging binary Ray Andrews
2014-11-22  4:45               ` Bart Schaefer
2014-11-22  5:27                 ` Ray Andrews
2014-11-22  5:43                 ` Bart Schaefer
2014-11-22 16:49                   ` Ray Andrews
2014-11-22 22:35                     ` Bart Schaefer
2014-11-23  7:58                     ` Lawrence Velázquez
2014-11-23 16:22                       ` Ray Andrews
2014-11-23 18:12                         ` Mikael Magnusson
2014-11-23 18:42                           ` Ray Andrews
2014-11-23 19:01                             ` Mikael Magnusson
2014-11-23 22:30                               ` Ray Andrews
2014-11-21 15:20     ` Jun T. [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AA05CB16-67A9-4476-ADC5-6186C76CFCE3@kba.biglobe.ne.jp \
    --to=takimoto-j@kba.biglobe.ne.jp \
    --cc=zsh-workers@zsh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).