From: Oliver Kiddle <okiddle@yahoo.co.uk>
To: zsh-workers@sunsite.dk
Cc: Haakon Riiser <haakon.riiser@fys.uio.no>
Subject: Re: Updated _acroread completer
Date: Mon, 25 Apr 2005 09:43:27 +0200 [thread overview]
Message-ID: <7344.1114415007@trentino.groupinfra.com> (raw)
In-Reply-To: <20050415111158.GA1709@s>
On 15 Apr, Haakon Riiser wrote:
> I have now tried the non-local variable trick, and it works just
> like I expected. I also noticed that the zsh completion system
> has a set of caching functions (_store_cache, _retrieve_cache and
> _cache_invalid). These functions apparently store data on disk,
I never use those and don't really like them. I prefer completion to be
slow the first time I complete something than for it to be out-of-date.
> # The output of acroread -version cannot be piped to stdout for some reason, so
> # the version number must be read from ACROREAD-PREFIX/Reader/AcroVersion.
> # Since acroread might have been started via a wrapper script, the only
> # failsafe way of determining ACROREAD-PREFIX is to look at the output of
> # acroread -help.
Unfortunately, this doesn't work on the system I tried it on, using
Adobe's rpm. /usr/bin/acroread is a symbolic like to
/usr/local/Adobe/Acrobat7.0/bin/acroread. Handling that involves using ls
to get the symlink destination.
Is acroread always a script? The following works well (and very quickly)
on any system I have access to:
grep '^ver=' =acroread
>From a completion function, we can use $commands[$words[1]] instead
of =acroread.
Oliver
next prev parent reply other threads:[~2005-04-25 7:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-14 13:47 Haakon Riiser
2005-04-15 11:11 ` Haakon Riiser
2005-04-25 7:43 ` Oliver Kiddle [this message]
2005-04-25 8:41 ` Haakon Riiser
2005-04-25 8:54 ` Oliver Kiddle
2005-04-25 8:58 ` Haakon Riiser
2005-04-25 9:39 ` Peter Stephenson
2005-04-25 13:00 ` Haakon Riiser
2005-04-25 13:36 ` Peter Stephenson
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=7344.1114415007@trentino.groupinfra.com \
--to=okiddle@yahoo.co.uk \
--cc=haakon.riiser@fys.uio.no \
--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).