From: Bart Schaefer <schaefer@brasslantern.com>
To: Clint Adams <schizo@debian.org>, zsh-workers@sunsite.dk
Cc: 355430-forwarded@bugs.debian.org, Jay Berkenbilt <qjb@debian.org>
Subject: Re: Bug#355430: zsh: acroread completion prints debugging information
Date: Sat, 25 Mar 2006 10:15:46 -0800 [thread overview]
Message-ID: <060325101546.ZM21762@torch.brasslantern.com> (raw)
In-Reply-To: <20060325151155.GA21370@scowler.net>
On Mar 25, 10:11am, Clint Adams wrote:
} Subject: Re: Bug#355430: zsh: acroread completion prints debugging informa
}
} > The way I found this was to do setopt -x before acroread TAB and to
} > see that the loads of extra output I got started after evaluating line
} > 7 of _acroread which shown here including the preceding comment:
} >
} > # Try extracting the version number directly from the executable.
} > # (This will fail if the executable is a wrapper script for acroread.)
} > local ver=${${${(f)"$(<$commands[$words[1]])"}:#^ver=*}##ver=}
The comment is misleading. The test above fails UNLESS the executable
is a shell script, not IF the executable is a shell script. I'm not
sure if the comment author meant to imply an extra script around the
Adobe-supplied default script, or if he got his semantics backwards.
} What's happening is that that line is being run as "local" without the
} argument. Why?
My only guess is that it has something to do with NULLGLOB and the junk
that would get spewed out by $(<$command[$words[1]]) in the event that
it really was reading directly from a binary executable.
next prev parent reply other threads:[~2006-03-25 18:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060305163923.12356.23913.reportbug@soup.q.ql.org>
[not found] ` <20060306020302.GA6489@scowler.net>
[not found] ` <20060325095217.2524443157.qww314159@soup.q.ql.org>
2006-03-25 15:11 ` Clint Adams
2006-03-25 18:15 ` Bart Schaefer [this message]
2006-03-25 18:34 ` Clint Adams
2006-03-26 7:01 ` Bart Schaefer
2006-03-26 15:12 ` Clint Adams
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=060325101546.ZM21762@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=355430-forwarded@bugs.debian.org \
--cc=qjb@debian.org \
--cc=schizo@debian.org \
--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).