From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7241 invoked by alias); 30 May 2015 22:42:44 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: X-Seq: 20239 Received: (qmail 5532 invoked from network); 30 May 2015 22:42:42 -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=WIlgiNtKyja5XBVr84Aa7ru5cwnN6Mx6L/WU5bkn/7o=; b=UwtcwyWIIwXKfBgCvyCRcVMmFiqDj3y9hwLhk+Jl2uMAPlNypaGLkCvY0UAWiAyWAg EfOoRdjeo2jIvvQPWZsQFChLLl+5hyJoLCKTmgP39JjjwSqwRn6qhrWA0bk06Lu/FdB2 KifERYE25yYgyv0i0t5utN6zmimrAaqW2yUfrIAaCR7jO9yHBMVFCiuzRZKS/X7b56kw F+N2++LJZgjlwYwbACOpBjiNGNgX4J8kEHb86p0KHNeRo35D1MXaBsxy3vVJNQiHRQsp 9Ef/GFgxihdGVrPjmjCdFUKx4qEvSAIENrlVqcRFokWefQc147+N3ML0wbIcx9HUM7Lv 5YPg== X-Gm-Message-State: ALoCoQnBteFhk18viF77+VGbIrw4xvw0QnPCfMmxG8iMzge8avsjAKeVXfMeBpgayPm6wV06aHI2 X-Received: by 10.60.123.83 with SMTP id ly19mr12360654oeb.13.1433025759930; Sat, 30 May 2015 15:42:39 -0700 (PDT) From: Bart Schaefer Message-Id: <150530154236.ZM17511@torch.brasslantern.com> Date: Sat, 30 May 2015 15:42:36 -0700 In-Reply-To: <150529171657.ZM15077@torch.brasslantern.com> Comments: In reply to Bart Schaefer "Re: Finding the first history event of the current instance" (May 29, 5:16pm) References: <87r3q7nzkr.fsf@gmail.com> <150529171657.ZM15077@torch.brasslantern.com> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-users@zsh.org Subject: Re: Finding the first history event of the current instance MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On May 29, 5:16pm, Bart Schaefer wrote: } Subject: Re: Finding the first history event of the current instance } } On May 23, 4:22pm, Christian Neukirchen wrote: } } } } How can I list *only* the history lines that I typed into the current } } session? } } Or there's this patch. I didn't add an option for listing only the } NON-local history, but it should be pretty obvious how to do so. Hmm, except I've just realized that lines read from $HISTFILE are taken to be local to the current shell when they are loaded at startup, We would need to filter for the HIST_OLD flag instead of HIST_FOREIGN to get just those lines entered interactively, and I'm not sure how that interacts with INC_APPEND_HISTORY -- do the events become "old" as soon as they are appended to the file? The options -N (new), -O (old), and -F (foreign) are all currently unused by "fc" if we wanted to add multiple filterings. Anyway, sorry, but the patch as it stands does not actually solve the original problem.