Re: Return value of shell-command ?

cgw> I've been looking at this piece of code (from package-admin.el) cgw> (if (shell-command (concat "gunzip -c " filename " | tar xvf -") cgw> buf) 0 1) cgw> cgw> and it seems to me that "shell-command" always returns 't. The cgw> documentation for shell-command doesn't really say anything about cgw> the return value. cgw> cgw> I've tested on both WinNT and Linux and get the same behavior: cgw> Hmmm.... I've had problems on NT with the VC package which traced back to not getting return codes from invoked processes (when you VC runs 'rcsdiff --brief' it never sees a return code indicating that there were differences.) Could this be related? I had assumed that this was an issue in subprocess stuff on NT, but you're getting it on Linux as well.... Matt. -- /\/\att Stupple TIBCO, London Internet - http://www.tibco.com/ matts(a)tibco.com +44(0)1712956053 Intranet - http://tekuk01/~matts/ "This summer I went swimming, this summer I might have drowned - But I held my breath, kicked my feet and moved my arms around." -- ER