Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: PATCH: suggestion for new condition
- X-seq: zsh-workers 5074
- From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxx>
- To: Sven Wischnowsky <wischnow@xxxxxxxxxxxxxxxxxxxxxxx>, zsh-workers@xxxxxxxxxxxxxx
- Subject: Re: PATCH: suggestion for new condition
- Date: Wed, 27 Jan 1999 22:01:31 -0800
- In-reply-to: <199901270751.IAA29022@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm
- References: <199901270751.IAA29022@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
On Jan 27, 8:51am, Sven Wischnowsky wrote:
} Subject: Re: PATCH: suggestion for new condition
}
} > } The patch below implements the `(t)' flag. `${(t)param}' will expand
} > } to a string describing the type of parameter. When param is unset, it
} > } will expand to `-'
} >
} > Why? Why not have it expand to nothing? In any case "-" is a bad choice,
} > because in certain contexts it could be misinterpreted as an option.
}
} Blink. Yes, you are right, I was just thinking about Peter's mail and
} didn't like to use a space. Of course, an empty string is the better
} solution.
OK, cool, now dumb question number two: Why does ${(t)param} ignore the
setting of the `nounset' option?
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Messages sorted by:
Reverse Date,
Date,
Thread,
Author