I'm on version 5.2, on Win 10. When I alt-space or toggle zazu to make the window visible, it's a white window with nothing in it. It acts as it should in losing focus and disappearing, and alt-space to toggle away. But, there is never anything drawn. I've uninstalled and reinstalled, restarted pc as well.
App Environment: production
App Version: 0.5.2
Electron Version: 1.3.14
Node Version: 6.5.0
Chrome Version: 52.0.2743.82
App Version: 0.5.2
Electron Version: 1.3.14
Node Version: 6.5.0
Chrome Version: 52.0.2743.82
@mahdix hi!
That seems to have taken care of it.
Unfortuntely this is a common problem with issues related to
npm install that is hard to detect. We could possibly try and slow it down and only npm install one plugin at a time… or possibly have a Wipe Zazu Data button that does what you just did.
Hi TTT, I'm working on some alternative fallback search options for a project I'm working on NHSbuntu. I've initially gone for the super-easy option of simply forking tinytacoteam/zazu-fallback and essentially over-riding some of the searches , and adding my own. Ideally I'd like this to play nicely with the main zazu-fallback repo. I've looked at the other search plugins, but these all seem to use API searches. I live in the UK NHS (National Health Service) and we are essentially 'pre-API' in terms of technology, all searches are done vie query string on the URL. Any advice?
cc @pacharanero
I think there may be a other people who would want to build little 'suites' of custom searches like I did, in which case it might be helpful to make it clear in the README.md that it's possible to install more than one 'fallback'. Or perhaps have a 'custom search suite template' repo that people can fork and customise.
I've gotta say, though - awesome work on Zazu, and also for the neat way Zazu pulls in plugins from GitHub
@pacharanero if you are okay with copy/pasta you could just define your custom searches in the zazu config:
we're building a custom Ubuntu distro for NHS (National Health Service) workers
so we can package Zazu in that. (we'll have to create a PPA for it I think)
@Netanel1244 yes, in theory any of the systems through which your credit card number passes when you type it, could misuse it. Clipboard managers are one example, but we also have to trust our operating system (Windows 10 sends all your keystrokes to Microsoft, for example) and our web browsers, not to mention the e-commerce website itself. To some extent using an open source clipboard manager such as Zazu is safer (than using a closed source one) because we can inspect the code at https://github.com/tinytacoteam/zazu-clipboard and verify that it doesn't send information to another party.
You're right to have privacy concerns in general though - anyone who doesn't think about privacy these days is clearly not awake!
@Netanel1244 exactly zazu plugins do have access to your clipboard. The clipboard manager itself however does not store anything it thinks is “sensitive”. Often password managers like 1password or lastpass mark the clipboard with metadata that the clipboard manager can use to ignore it, so it’s never stored in plain text.
@anonfunc it was created to be github specific, but I’d be open to doing other git sources like gitlab or bitbucket. Not npm though. You could theoretically put a npm package that does everything on npm and just have the github part just interface with it if you wanted to get around my arbitrary restriction haha
@anonfunc ^^
it does find everything else though
@cfontes It needs to be in one of these directories:
https://github.com/tinytacoteam/zazu-file-finder/blob/master/directories.js#L67-L69
Which it sounds like you put a symlink in /usr/bin so that should be fine. It also needs to be executable:
https://github.com/tinytacoteam/zazu-file-finder/blob/master/lib/file.js#L45-L47
So I’m not sure symlinks work
I receive the following message when I toggle it Zazu requires plugins to work!
