From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17113 invoked by alias); 10 Jul 2015 09:34:45 -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: 35759 Received: (qmail 18768 invoked from network); 10 Jul 2015 09:34:43 -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=-6.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_HI, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_PASS autolearn=ham autolearn_force=no version=3.4.0 X-AuditID: cbfec7f4-f79c56d0000012ee-a7-559f91af99ce Date: Fri, 10 Jul 2015 10:34:36 +0100 From: Peter Stephenson To: Zsh workers Subject: Re: Undo is also confused with narrow-to-region Message-id: <20150710103436.1f51f3fb@pwslap01u.europe.root.pri> In-reply-to: <17928.1436367453@thecus.kiddle.eu> References: <8242.1435937191@thecus.kiddle.eu> <20150706093957.33d9cb25@pwslap01u.europe.root.pri> <4900.1436183185@thecus.kiddle.eu> <20150706202554.02d6c73a@ntlworld.com> <17928.1436367453@thecus.kiddle.eu> Organization: Samsung Cambridge Solution Centre X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.0; i386-redhat-linux-gnu) MIME-version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrKLMWRmVeSWpSXmKPExsVy+t/xa7rrJ84PNTi0m8/iYPNDJgdGj1UH PzAFMEZx2aSk5mSWpRbp2yVwZaw4f4Kt4ANbxd8Td5kbGI+xdjFyckgImEiseXcYyhaTuHBv PVsXIxeHkMBSRokZW/8xQTgzmCQa996AcrYxStycv58ZpIVFQFXi0azfTCA2m4ChxNRNsxlB bBGg+JwTp8DGCgtYSPx7+BAszitgL/Ht7WY2EJtTwEBiw7r7UEPnMkm0PJ7DApLgF9CXuPr3 ExPETfYSM6+cgWoWlPgx+R5YDbOAlsTmbU2sELa8xOY1b8EOEhJQl7hxdzf7BEahWUhaZiFp mYWkZQEj8ypG0dTS5ILipPRcQ73ixNzi0rx0veT83E2MkMD9soNx8TGrQ4wCHIxKPLwBbPND hVgTy4orcw8xSnAwK4nwJrYAhXhTEiurUovy44tKc1KLDzFKc7AoifPO3fU+REggPbEkNTs1 tSC1CCbLxMEp1cAY2Cnl+7k+87uDx/rsO18uXdRoyzX2vuWtf1P36hWz4zt17mdncTOG5oeb 9a06IXgqsKqD/WP5D8P8kuKNpzy2Liusjjpy+eOWHztnrvm+etKLvJW/24tVv9yV00m+aK+m e8uYWaNAptnbImbn1h6LMxlBorczBK4zTNg5v/KdScs+/22sx64psRRnJBpqMRcVJwIAldJH rVgCAAA= On Wed, 8 Jul 2015 16:57:33 +0200 Oliver Kiddle wrote: > > UNDO_LIMIT_NO > > Thanks. Trying to apply this in read-from-minibuffer, I found that it > was necessary to add a split-undo in after the BUFFER etc were setup, > otherwise it was possible to do one initial undo. Coming back to this after the last commit... perhaps recursive-edit should start a new undo anyway? You'd have thought it was somewhat illogical to turn up in the middle of an edit. (You might have thought it was logical to force an undo limit at that point, too. Could be options.) However, I suppose you now have full control, so it doesn't matter so much. Also, there's an inconsistency with the variable name here... > -integer changeno=$UNDO_CHANGE_NO > +integer savelim=$UNDO_LIMIT_NO changeno=$UNDO_CHANGE_NO >... > + UNDO_LIMIT_NO=save_limit pws