Date: Wed, 23 May 2012 22:32:29 +0200 From: magnum <john.magnum@...hmail.com> To: john-dev@...ts.openwall.com Subject: Re: Fwd: bash auto-completion for john On 05/23/2012 02:06 AM, Frank Dittrich wrote: > I removed the logic to try finding completions using --platform=LIST. > > Instead, I just list > --platform=N --platform=LIST > as possible completions for --platform= (only if --platform= is a valid > option according to the usage output) and > --device=N --device=LIST > as possible completions for for --device= > I should suppress this for CUDA builds, as CUDA doesn't support > --device=LIST. Currently, I don't check whether it is a CUDA build, > since I don't know what --list=build-info shows in this case. The build line will reflect a target in Makefile, so a CUDA build will show up as /^Build: .*-cuda$/ while an OpenCL build is /^Build: .*-opencl$/ and a CUDA+OpenCL build is /^Build: .*-gpu$/ (btw I can't picture a reason to build CUDA only, maybe the -cuda targets will become obsolete?). > Instead, I use a workaround (check whether --platform= is a valid option). I committed this. However, it seems to have the following glitch: ../run/john -dev[TAB][TAB] becomes: ../run/john --device=--device= and a similar behavior for -platform. This is with a -gpu build. magnum
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.