pier

So right now the preview window of the clipboard allows you to see enough to know what's in the entry, but it's not so great for consultation.

For example what I often do is that I copy bits of code that I only want to use as reference, but since reading those in clipboard preview is difficult (small text, broken lines, etc) I'm forced to paste the contents somewhere else.

So my feature request would be to be able to customize the preview window (larger space, larger text) or simply make it bigger by default.

4 hours ago, deanishe said:

I think you'd be better off with a script that you can run as needed rather than having Hazel check every single file in node_modules every time something changes.

Would adding the alfred:ignore tag to a folder make Alfred ignore all the files and subfolders too?

Sorry for reviving an old thread but this is the first Google result on the matter.

Would be awesome if there was a way to define a dynamic ignore. For example I'd like to ignore all node_modules folders which are created on every new JS project.

AFAIK there is not really a way to do that in Spotlight either, but it would be awesome if Alfred could solve this.

Thanks all for your support and the nice conversation.

1 minute ago, deanishe said:

 

Not at all. You do it exactly like I just described (using Language = /bin/bash).

 

If you can run it from a shell, you can run it from Alfred (with some caveats due to the stripped-down environment).

 

Alfred doesn't have built-in support for any language (apart from a bit of AppleScript). It just runs whichever program you point it at using precisely the same mechanism as child_process in Node.

 

Um I'm not following you. We are talking about Nodekit, right?

Yes I could just node whatever.js but the problem of distributing workflows that use node would still persist.

On a side note. Is there a way of showing a message to the user from the workflow and inform Node is needed?

3 minutes ago, deanishe said:

 

Why not give it a try then and find out? I'm sure a lot of people would be interested to know if it works.

How could I?

AFAIK this would have to be compiled with Alfred's code.

Just now, deanishe said:

 

Did I say Vue is awesome? I think I said Vue is awesome.

 

Vue is awesome.

It is indeed.

We used React in 2016 and this year we are moving all our new projects to Vue.

2 minutes ago, deanishe said:

The only "issue" with Node is that it isn't installed by default on macOS and it's far too big to include in a workflow.

 

If Nodekit is small enough to bundle, you're already good to go.

Yes, that was what I was suggesting.

1 minute ago, vitor said:

I don’t see how that sentence relates to the post you quoted.

Because @deanishe basically said "I don't like JS" and I simply insisted that Nodekit would solve the problems stated earlier about using the Node API from scripts in Alfred.

5 minutes ago, deanishe said:

 

Meh. I only find Electron etc. interesting because of the GUI aspect. For me, JavaScript is part of the price you pay, not a selling point.

 

The only time I willingly choose to use JavaScript is when AppleScript is the other option.

 

Everyone draws the line in a different place, and for me, weak typing is on the wrong side of it. I like my languages to throw an error if I try to add an integer to a string.

 

Sure, but it would solve many of the issues about trying to make Alfred work with Node.

1 minute ago, deanishe said:

JS is 21 years old. The same as Ruby and PHP, and just a bit younger than Python.

You are of course technically correct, but I feel since Node and NPM entered the scene we are in a new JS renaissance that it's still trying to trying to define itself. I don't mean the language itself but the whole development process. Maybe I'm delusional, but I think (I hope) we should reach a maturity plateau in a couple of years.

Hey guys I just found this: https://nodekit.io/ relevant to the discussion about Node.

It's a cross platform Node replacement that uses the JS engine provided by the OS so it provides a very lightweight implementation of the Node API. The motivation page gives a bit more of insight.

3 hours ago, vitor said:

If I could easily transform an Electron app to a Cocoa Webview one¹, I would.

If your app doesn't use Node you use this https://github.com/francoislaberge/shrinkray (macOS only)

2 hours ago, deanishe said:

JavaScript as a whole has a cultural problem, imo.

JS is in a teenager phase like PHP was 15-20 years ago. Hopefully it will mature and learn from its mistakes if Web Assembly doesn't kill it...

2 hours ago, vitor said:

 

Node.js’ pkg installer alone is seven times the size of the Alfred dmg/twice the size of Alfred.app. Not to mention the amount of technical work that would require to integrate it with Alfred and keep it apart from the node on the system (if any) and (insert a bunch of other limitations and disadvantages).

Yes I'm aware of that. I'm not suggesting Node should come bundled with Alfred by default. Workflows could define a Node dependency so that Alfred could install it for the user.

As for the technical work I really can't say how intricate it would be but other projects like Electron have already solved that.

2 hours ago, deanishe said:

Alfred doesn't provide a way to distribute any workflows, let alone ones that depend on languages that aren't a standard part of macOS.

But Alfred does define the workflow specifications. Hence if a workflow could say "hey I need Node", Alfred could in principle download it for the Alfred user.

Thanks @deanishe

It would be awesome if Alfred provided an easy to distribute workflows that use Node instead.

I'm wondering what kind of features are available in the JS engine used by Alfred.

Can we use ES6, async/await, fetch(), etc?

Hi everyone!

Is it possible to customise the list of actions that appear after pressing TAB?

I mean this menu: http://i.imgur.com/FZRFJeV.png

 

Sorry to revive such an old thread.

I understand Andrew's points.

But, if it's possible to do the filtering via a script on a workflow for advanced users, why not add a more advanced filter UI in the File Filter workflow object?

Right now it's only possible to filter by file type. It would be very handy to be able to filter with names. For example to exclude "node_modules" folders.

Hi everyone

I've created a workflow for easy access to Google Apps (Gmail, Docs, Sheets, Calendar, etc). See Github for the full list.

https://github.com/PierBover/AlfredWorkflowGoogleApps

Enjoy

So I'm following this tutorial to make my first python workflow.

Right now I only want to type a keyword, invoke a python script, and get anything in the Alfred results.

So I have created my workflow, created an input script filter with /bin/bash code

python my_file.py

In my_file.py (which is in the workflow directory) I have this

# encoding: utf-8

import sys
from workflow import Workflow, ICON_WEB, web

def main(wf):
    wf.add_item(title = 'something')
    wf.send_feedback()

Edit: I forgot to say that I downloaded the latest workflow module from deanishe and copied it in my workflow folder too

Hi

Sorry to bring up an old post.

I'm using the workflow solution to search only for folders, but I think it would be a better solution to be able to dismiss files in the default search results.
 

90% of the times I search for folders and not files. Pressing 'space' twice is the fastest shortcut of all and having to use a different shortcut for the general case is counterintuitive to me. It would make more sense to be able to search only folders by default and files with a special command.

I understand my case is not necessarily the general user case, but having a "Show only folders" checkbox in the "Default results" shouldn't be too difficult to implement.

In other words, is it possible to create a workflow that instead of using a keyword grabs some info from a data file, and then inserts results in the default searches?