From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22323 invoked by alias); 12 Aug 2015 16:04:40 -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: 36129 Received: (qmail 15085 invoked from network); 12 Aug 2015 16:04:38 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H2 autolearn=ham autolearn_force=no version=3.4.0 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:in-reply-to:comments :references:to:subject:mime-version:content-type; bh=B+rAK2rAS64BV19LL8th+cr+n02uv19lJM9JmEjtre0=; b=EIaY/kyoxiALDWx05Hs/UidcZAOLVvXpifCa6sfJlgU4fx43g5maxCFZvMXx08ojyM NASh29N+k7AztXdkAZiNIfZbE5FKVGoq7xCEkwznJH3QaZ/y//WRqHGMixGXCKBTD3+B BvU9dwQ2K2PRveIMRnnOF9yQl0UxO4ad7qapVkmbNYdSaFBBh2KsExABY3o8hcQ16Uyw qv04Vnq5R63KDjQ9E8nExTBit9reNDtKgK5vJfU2FR67klzk/zEPhLFe1FLh2gWo5oSR mH2WzsfmZzpzLFrqrX8ZxbvwOs4nXYyXCwaeapB75lR6qcmcVLt8QIl9uAeqDme1NH5x z+lA== X-Gm-Message-State: ALoCoQmGRL9XnJz6QYT25VyTTWAkqyuiTinB7ojX9R5ARUYFlZnZZosfzSMbwUY9Mi93ufhbsOGy X-Received: by 10.60.177.73 with SMTP id co9mr30555291oec.5.1439395475869; Wed, 12 Aug 2015 09:04:35 -0700 (PDT) From: Bart Schaefer Message-Id: <150812090432.ZM348@torch.brasslantern.com> Date: Wed, 12 Aug 2015 09:04:32 -0700 In-Reply-To: <3787.1439389607@thecus.kiddle.eu> Comments: In reply to Oliver Kiddle "PATCH: get-line shouldn't set histline" (Aug 12, 4:26pm) References: <3787.1439389607@thecus.kiddle.eu> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: Zsh workers Subject: Re: PATCH: get-line shouldn't set histline MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Aug 12, 4:26pm, Oliver Kiddle wrote: } } The get-line widget is meant to insert the line from the buffer stack } into the current line. Changing histline without setting the line to } correspond to the text stored for the history entry results in undo } information that doesn't make sense. } } Can anyone see how the change might cause a problem for normal } get-line usage? I can't think of a way this would cause a problem, but I hardly ever use get-line.