From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4790 invoked by alias); 23 Dec 2015 00:54:02 -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: 37421 Received: (qmail 1392 invoked from network); 23 Dec 2015 00:53:58 -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=-1.9 required=5.0 tests=BAYES_00,T_DKIM_INVALID autolearn=ham autolearn_force=no version=3.4.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brasslantern-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:date:in-reply-to:comments:references:to:subject :mime-version:content-type; bh=t7Gsywq/ONdW21EmbGyWoFgi+TjR2cCWfmC81Kl+Xhc=; b=R0AgkVyeFaWD2IcjFn1UU2RFBgxxEVCY56KU3kEQJXCet3L6bDpKU6Naa9DUyRNWyZ GLGXy7o6NebMhir1cYCLBc9EG69mQ4VCF6Vit+8NbeB3pBWaHO6VbhtI+4BOI3J8/plo SpVa7n5CAXOtGObUs+U+d3JWmvbg1E8gSYES63pwGjcHShb87Nmea1CuB8m1sh3qafmT 8TwFIAy7/sUiQrdkSmvkba9DAAMkbq63tI/VrXhcYAytfRHPBB0BMycs5+SoU9i5aRhV v8h/58JtTUBR4cTPwlntxwmmQc6wvevWpoGr0BAz56gjjT0vUhntyz+j9MIrzWPnme5D VcKA== 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=t7Gsywq/ONdW21EmbGyWoFgi+TjR2cCWfmC81Kl+Xhc=; b=IVTiyZmeM0slqQocnxpqDPeWM2Am6HeRldciCFJ8GKdfL3JjTt1xamTOpt18ApeFVF ew2HKlZvDBHPvetctv1B+T+Kfw7xuzO8Af0Sn+wBDCgfE03r1NeuUGx9tsdBVNpjhURY Mwm0mVqmWsPU32pmBKObHx4Oju5KnTipw1d1hyBuKILPOLos1dFOiFdN9uIt1RmyGyHu gseUEFsejaeKD26UmUUdXiS0oGmq16NUgnvep6TbPW6XSrAJm0ckWm6+1JSSE0fSxn0b cV72HuK8v2x5yk03qZtDy+gQUlzpaGdCiTz2ityRJzf3N14nWtgbgkZtMbvK1bAilSxX MNVg== X-Gm-Message-State: ALoCoQmUAuw1LJrf59ZejsHEM+RSo4OrrE2HD0XjKD3z2qeFj3Zar7S1cXjT7/nn1RODsEW5Ivb+rP1mnfA49kwd4lQ18Rskcw== X-Received: by 10.98.74.5 with SMTP id x5mr12380172pfa.102.1450832036040; Tue, 22 Dec 2015 16:53:56 -0800 (PST) From: Bart Schaefer Message-Id: <151222165433.ZM28846@torch.brasslantern.com> Date: Tue, 22 Dec 2015 16:54:33 -0800 In-Reply-To: <20151222181420.GA21368@ofb.net> Comments: In reply to frederik@ofb.net "Re: question about saving history and error reporting" (Dec 22, 10:14am) References: <1450718785.14170.ezmlm@zsh.org> <20151221203800.GB23389@ofb.net> <151221125450.ZM21081@torch.brasslantern.com> <20151222181420.GA21368@ofb.net> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-workers@zsh.org Subject: Re: question about saving history and error reporting MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Dec 22, 10:14am, frederik@ofb.net wrote: } } For me, if the history can't be written, it would be convenient to } know about the errors that are being generated immediately, so that I } can fix the problem. Are there many situations where the history can't } be written due to a problem which is transient? The most common reason in the case of inc_append_history could be that multiple shells are updating the file at the same time. There are also things like home directories on remote filesystems that are temporarily unreachable. Really it's not the responsibility of the shell history mechanism to alert you about system-wide failure conditions like a full disk, and I wouldn't want to encourage anyone to rely on it for that. } Are there other cases where Zsh hides errors that occur during its } operation? That's a rather wide-open question. The (programmed in shell code) completion system deliberately suppresses all sorts of errors that might occur during generating the possible matching words, because they're irrelevant to updating the command line and displaying them would mess up screen for ZLE. Within the C code, I would not be surprised if there are other implicit actions for which displaying an error state is considered unnecessarily verbose, but I can't tell you of any offhand.