From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23936 invoked by alias); 15 Mar 2015 01:38:12 -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: 20011 Received: (qmail 18528 invoked from network); 15 Mar 2015 01:38:10 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) 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 autolearn=ham version=3.3.2 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=nfykuerg34IVgVhHW4k1UhBDgjMgSfDVzP9gnoUYKRw=; b=VFvVlt/s+gwO//3/XaJ+8cvi/eREoRjocFn+1rnr9bQulRASNk8vcJEX6Mtp28juP+ FnmxEWqfOjJN6/T4PQZUhviyny6ioUQ+ClTHnDY261++rw6sLt24jP/LRnve4SXB4FAT 0FroyAat7ODapuot5DDvg6jkRiUhAzITWktr6HTBDNJ61aPpI9Oi/4ietHS1/DXz8Y17 bhHbmQykovI7/ba5bxw2HnmVNCu9xQxWTViKLIqKl9eTP7s6LY0BNSz3H3KyjLRGUlSr Ptw4kjvG33ZNJYFJZF3DXcji9HA9IwZffT7igXVYIc9O1O53v+ArxOfiiKJl7bX2KmMS S+mQ== X-Gm-Message-State: ALoCoQkF3tZX2uZLi6QnmdDyAL7Ajm5uEh+HcYxmOeNnDzc2FUvncuCk4z/JjfJBy9OlP19w3R1a X-Received: by 10.202.46.138 with SMTP id u132mr40595843oiu.19.1426383485909; Sat, 14 Mar 2015 18:38:05 -0700 (PDT) From: Bart Schaefer Message-Id: <150314183802.ZM26315@torch.brasslantern.com> Date: Sat, 14 Mar 2015 18:38:02 -0700 In-Reply-To: <20150314234403.GA2795@localhost.localdomain> Comments: In reply to Han Pingtian "How to get 'fc' context?" (Mar 15, 7:44am) References: <20150314234403.GA2795@localhost.localdomain> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-user Subject: Re: How to get 'fc' context? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Mar 15, 7:44am, Han Pingtian wrote: } } How can we get the 'fc' context, please? I don't think there is an "fc context" in the way you seem to mean. "fc" either invokes an external editor, in which case the shell is not involved at all, or it feeds the history directly back to the interpreter again, in which case it's not doing anything that would have a context. The reason you get "toplevel file" is because "fc -e" has copied the history event to a file and then invoked "source" on the file. What exactly are you trying to accomplish with this?