zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@csr.com>
To: zsh-workers@sunsite.dk
Subject: Re: PATCH: add zle-line-finish special widget
Date: Fri, 23 Jan 2009 09:37:49 +0000	[thread overview]
Message-ID: <20090123093749.1e6be9fe@news01> (raw)
In-Reply-To: <m37i4m3kwk.fsf@klanderman.net>

On Thu, 22 Jan 2009 19:50:51 -0500
Greg Klanderman <gak@klanderman.net> wrote:
> >>>>> Bart Schaefer <schaefer@brasslantern.com> writes:
> 
> > Refreshing my memory of the code a bit, I'm coming
> > to the conclusion that the test should be:
> 
> >     if (done && !exit_pending && !errflag &&
> >     	(initthingy = rthingy_nocreate("zle-line-finish"))) {
> 
> > At the very least it should check (done && !exit_pending), even if
> > it ignores the state of errflag.
> 
> Either of those should be OK by me.. would you like me to
> test one or the other a bit and re-submit the patch?

That what probably be sensible

> >>>>> Peter Stephenson <p.w.stephenson@ntlworld.com> writes:
> 
> > I don't know if this is correct or not---it really depends what
> > zle-line-finish is designed to do.  If it's a catch-all tidy up, it
> > probably *should* run and then you probably should set errflag to 0
> > after saving the surrounding value.
> 
> Right.. for my current use case it doesn't really matter whether it
> runs in the error case or not.  I'm not sure which semantics is best
> in general.  If one wanted to use it for some cleanup, or messing with
> font colors or whatever, you might want it to run always.

For now it sounds like you should leave it as it is.

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
Cambridge, CB4 0WZ, UK                          Tel: +44 (0)1223 692070


  reply	other threads:[~2009-01-23  9:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <18789.30656.261463.382208@gargle.gargle.HOWL>
     [not found] ` <20090110095231.GA61601@redoubt.spodhuis.org>
     [not found]   ` <m33afq97gg.fsf@klanderman.net>
     [not found]     ` <20090111025418.GA7272@redoubt.spodhuis.org>
     [not found]       ` <m3tz857mkm.fsf@klanderman.net>
     [not found]         ` <090111110748.ZM12349@torch.brasslantern.com>
     [not found]           ` <m3r63975pd.fsf@klanderman.net>
     [not found]             ` <m3ocyd70aj.fsf@klanderman.net>
     [not found]               ` <090111193317.ZM12655@torch.brasslantern.com>
2009-01-12  4:00                 ` some way to inherit kill ring in su'd shell? Greg Klanderman
2009-01-12  5:33                   ` Bart Schaefer
2009-01-12 19:33                     ` Greg Klanderman
2009-01-12 23:55                       ` Richard Hartmann
2009-01-16 23:54                   ` PATCH: add zle-line-finish special widget Greg Klanderman
2009-01-17 17:48                     ` Peter Stephenson
2009-01-17 18:08                     ` Bart Schaefer
2009-01-23  0:50                       ` Greg Klanderman
2009-01-23  9:37                         ` Peter Stephenson [this message]
2009-01-28  4:38                           ` Greg Klanderman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090123093749.1e6be9fe@news01 \
    --to=pws@csr.com \
    --cc=zsh-workers@sunsite.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).