From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23882 invoked by alias); 5 Oct 2016 18:36:00 -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: 39576 Received: (qmail 29795 invoked from network); 5 Oct 2016 18:35:59 -0000 X-Qmail-Scanner-Diagnostics: from mail-pa0-f44.google.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1. Clear:RC:0(209.85.220.44):SA:0(0.0/5.0):. Processed in 0.566029 secs); 05 Oct 2016 18:35:59 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=T_DKIM_INVALID autolearn=unavailable autolearn_force=no version=3.4.1 X-Envelope-From: schaefer@brasslantern.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: none (ns1.primenet.com.au: domain at brasslantern.com does not designate permitted sender hosts) 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; bh=s0CjZnhnWw7Hshdt5w7UaIl3H8Mr3IFiMNJMDoJD+o8=; b=pAuLUVs+m18jKRP9mYW8EGcv9TTHYnQhIsHWWslAKztkOR3QpR/0Vyaydu2GvaxXHC XoF8vSM2udsAgG9fD6Uya0P4ITJqBfUKCQ7IGd1mQGM7vMOs7yZel9cEa9uA7RzlmpPW wva9fJyuG3jUsEMYPID++t0Tr/7j18tZ1xnVEd6/4QiHrMq1cI4aHDVW+fkFGvTeRQIR Svd7IiGQO8yJfYiA30RYVd5wyvTPlW61jrw4oEsr4qfXTgFobM1KPRXXYtO247LjbUgb 1AlZAfkvewTEWsflSFiou3qqRg/59VPqtCWHzNyrz9bd2Twk+HEpOl1eU26l6Cb/7dPs losA== 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; bh=s0CjZnhnWw7Hshdt5w7UaIl3H8Mr3IFiMNJMDoJD+o8=; b=YUmk0OPEPmJR1wlyVf/PtZhizoAFIfMjq0mAgIQQcUw5mRVbWJwnU2LG0EXq+wp3fZ 2eRRc9ABTiBigLCURB/drx8rUQP2OSwKokTbDnqO2B/ITCYduNoVLzOKP1tH7hUCkNKM wnC+6QKZIJt80QrLg88FsMRwyYmmA2tue+eEBY7bcXxTIWccyUwecpXLkygDkexLHlck qvxXh3YPQmbpseOIzEx1Alb0+DpdywqUTPPEs2HJoKeowadwlHga+5RtMVsbUL6uQ1wZ qZ6MHV6GA6yRYTiWKk4pZf4SVrmxVWZvlnm2LW+TSzCQb6wHaAbupSf+NiEYhY7l0Z2F mAYw== X-Gm-Message-State: AA6/9RlEprRTS6KziO0wzi+ozsznVM8teFP5JJGznhtnQH+feIyR6ISFeCKWKPG0f/cO9A== X-Received: by 10.66.175.203 with SMTP id cc11mr15638781pac.102.1475692240426; Wed, 05 Oct 2016 11:30:40 -0700 (PDT) From: Bart Schaefer Message-Id: <161005113109.ZM12765@torch.brasslantern.com> Date: Wed, 5 Oct 2016 11:31:09 -0700 In-Reply-To: Comments: In reply to Sebastian Gniazdowski "Re: Where to start debugging zle recursive-edit? / Ctrl-C" (Oct 5, 12:27pm) References: <160924133140.ZM29034@torch.brasslantern.com> <160930134446.ZM17118@torch.brasslantern.com> <161004231456.ZM10640@torch.brasslantern.com> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: Zsh hackers list Subject: Re: Where to start debugging zle recursive-edit? / Ctrl-C MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Oct 5, 12:27pm, Sebastian Gniazdowski wrote: } } > } Wrapper around recursive-edit would solve Ctrl-C problems, or you } > } meant something about rescheduling? } > } > I meant something about scheduling. } } Hmm, could you reveal? This was proposed before we'd identified the problem with the signal queue getting too deep, so may not be helpful any more; but the idea is that since ^C returns you to the caller of recursive-edit, this means precmd is not run. So if you need to reset something that is normally handled in precmd, you should include that part of precmd in the wrapper, calling it after "zle .recursive-edit" returns. } I thought about trapping INT when detected that } in .recursive-edit, but directly that's "Ctrl-C problems" stuff trap 'zle && zle .send-break' INT # might be helpful with localtraps } > Either open a named pipe file (mknod p filename), or use the zsh/tcp } > module as in the example that appears in the documentation. } } That are rather heavy-implementation things Is having a named pipe file really that much heavier than having the shared text file plus that external flocking app to synchronize the access to it?