zsh-users
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-users@zsh.org
Subject: Re: Idiom for booleans
Date: Sun, 14 Aug 2011 18:11:08 -0700	[thread overview]
Message-ID: <110814181108.ZM20034@torch.brasslantern.com> (raw)
In-Reply-To: <CAELbujqBkE_zUG9M2+DS4mv=TxxKT=Rq4vH2fhXsbJ235B4nAA@mail.gmail.com>

On Aug 12, 10:26pm, Micah Elliott wrote:
} Subject: Re: Idiom for booleans
}
} > On Aug 12,  5:24pm, Micah Elliott wrote:
} > }
} > }   % (( 0 ))
} > }   ((: command not found
} 
} > This has to be something in your configuration.  Try it with zsh -f ?
} 
}   . /etc/zsh_command_not_found
} 
} That's a pretty handy utility (that I would expect to be popular), but
} for now I'm going to live without it. I see it's a problem on the last
} few Ubuntu releases, and I can't believe other people aren't seeing
} the problem.

I've had a Ubuntu laptop for a couple of years now and never noticed
this utility (not that I'd have used it if I had) so it's not all that
surprising to me that it isn't a widespread problem.

Ironically, the very first line of the precmd function defined by
/etc/zsh_command_not_found begins with

   (($?)) && ...

Obviously this implementation predates zsh introducing its own hook for
command-not-found.  It could have been done correctly, though, by the
simple expedient of

   (($? == 127)) && ...


  reply	other threads:[~2011-08-15  1:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-13  0:24 Micah Elliott
2011-08-13  3:09 ` Bart Schaefer
2011-08-13  5:26   ` Micah Elliott
2011-08-15  1:11     ` Bart Schaefer [this message]
2011-08-15  8:28       ` Julien Nicoulaud
     [not found]   ` <CAELbujqBkE_zUG9M2+DS4mv=TxxKT=Rq4vH2fhXsbJ235B4nAA__26422.7002081045$1313213450$gmane$org@mail.gmail.com>
2011-08-13 10:37     ` Štěpán Němec

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=110814181108.ZM20034@torch.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=zsh-users@zsh.org \
    /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).