From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8805 invoked by alias); 12 Nov 2016 17:10:11 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 39926 Received: (qmail 12870 invoked from network); 12 Nov 2016 17:10:11 -0000 X-Qmail-Scanner-Diagnostics: from mail-ua0-f177.google.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1. Clear:RC:0(209.85.217.177):SA:0(-0.0/5.0):. Processed in 1.321917 secs); 12 Nov 2016 17:10:11 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-0.0 required=5.0 tests=RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_PASS,T_DKIM_INVALID autolearn=unavailable autolearn_force=no version=3.4.1 X-Envelope-From: schaefer@brasslantern.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at _netblocks.google.com designates 209.85.217.177 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brasslantern-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:date:to:subject:mime-version; bh=QJfBhZHK9r4PLYUgTMzaWikdYfWe7YJGRiJlAhKYJmY=; b=N/G8hmUKZJ+utDAXbDMgCT+aT+ZxujdD0ve6Rl3SUPM0VgEULq6+hyTUVui7wzXSq1 RJK9FBzt+RNlsw9cJxMf7OMbkmdDH3xpK6+HFBsvewR5UP9QUD7vjBRfFFLCRuNq+xm0 L1qsbadtOiUuKdVjXdlysqmaztKsi9DZFALblo333oAnaaus+Q0iU8VURagxss5x6Jw1 0iHybLUyuG/20zhx+0BK0Y0bASnTdhH6wwAXMnbEGvg4gsyV1BFPSQVnn1WQFUOueFxl VRIhvNZr7VJSHncNCVtJGAaYhm/wDJ+ZlXfm2S5v1KoKAf5wHS6C56EjQCvEMAQTmAAl D4Pg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:message-id:date:to:subject:mime-version; bh=QJfBhZHK9r4PLYUgTMzaWikdYfWe7YJGRiJlAhKYJmY=; b=li1hc+GvbFRNZUa+V1C3kiYucdaRQvRdD2XUyCMkZ71D6rs+MZfavohP4A4oEvbH5h PCnzdNuVscU/J2fZ7F9+oEaqwJXYO1BVgo2MkxVxD/9SLORGyV6j2GytIkEF7utmICH8 XCS3ThSk5Tc569rE8bP8n8Er/dtX7RejevKg8kPr9Dz0+D72PP6eTD8+Fcej1GEhRqWG tMN4OugCL7Jn5CpOlL8j9vNAAB4R73q/a2GKMqH9MFVo5N5ZEcHymQOdAoIaKEFG4DBF 0P7QILM8iFaT3WB2XgUXZcVj0hbdvSsmxEF/oG1nfizViLlyDez3FZQBnJOIHN/Ev9Fk ZlIQ== X-Gm-Message-State: ABUngvffZGFmaDK4kyaAfZtp4svnN+GE2AYfhw9RftLWJbrBA0mnoE3//pt7CXDctEtx8A== X-Received: by 10.159.36.179 with SMTP id 48mr5490878uar.80.1478970191666; Sat, 12 Nov 2016 09:03:11 -0800 (PST) From: Bart Schaefer Message-Id: <161112090315.ZM1146@torch.brasslantern.com> Date: Sat, 12 Nov 2016 09:03:15 -0800 X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-workers@zsh.org Subject: Bad effect of error in zle-line-pre-redraw MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii If you happen to introduce an error into zle-line-pre-redraw, your shell is pretty badly wrecked -- ZLE resets itself after every character typed. Stupid minimal example: torch% zle-line-pre-redraw() { : ${bad_subscript[missing-bracket} } torch% zle -N zle-line-pre-redraw torch% e zle-line-pre-redraw: invalid subscript torch% e torch% c zle-line-pre-redraw: invalid subscript torch% c torch% h zle-line-pre-redraw: invalid subscript torch% h torch% o zle-line-pre-redraw: invalid subscript torch% o torch% Why the missing bracket isn't a syntax error at parse time rather than an evaluation error at run time is left as an exercise; e.g. ksh complains when defining the function. Other hook functions (zle-history-line-set, etc.) don't have this side- effect.