saor47 Posted April 21 Share Posted April 21 When I put `"type": "file:skipcheck"` in script filter results and pass its argument to the file buffer, the `//` in the string is automatically altered to `/`, which makes urls invalid. Link to comment
Andrew Posted April 21 Share Posted April 21 @saor47 The "file:skipcheck" is simply to tell Alfred not to check if a file exists before presenting to the user. This doesn't alter the argument passed out. Also, the File Buffer is for files only, not URLs, so it's not clear what you're trying to achieve. Could you please provide a small example workflow, and a bit more of a description, that'd be helpful! Cheers, Andrew Link to comment
saor47 Posted April 22 Author Share Posted April 22 Hello. I understand the file buffer is meant for files, but since it‘s possible to skip the file check, I figured I could also collect text strings with it, in order to i.e. concatenate multiple strings, or open multiple urls altogether. But the urls passed into file buffer then become “https:/xxx“. Link to comment
Andrew Posted April 22 Share Posted April 22 @saor47 To clarify my previous reply, you're instructing Alfred that you're passing a file path back as the argument, but telling him to skip the validation. Quote If you would like Alfred to skip this check because you are certain the files you are returning exist, use "type": "file:skipcheck". If you're forcibly passing back a URL instead of a file as the argument, the behaviour becomes undefined / unsupported. Cheers, Andrew [moving to Workflow Questions] Link to comment
saor47 Posted April 22 Author Share Posted April 22 Well, by setting `"type": "file:skipcheck"`, I’m able to collect URLs in the file buffer and send them to actions that accept multiple strings, which pretty much meets my needs. But the double slashes in the strings are all replaced with single ones. I suppose this wouldn’t affect file paths since there’re normally no double slashes in file paths. But if this could be fixed then the file buffer will also work for URLs (even though it wasn’t designed to do so). zeitlings 1 Link to comment
vitor Posted April 22 Share Posted April 22 One approach you can take is to make it so pressing ↩ appends the line to a file (tell the connection to not close on actioning) and then on ⌘↩ read the File Contents (there’s an Automation Task for that), split it on newlines, then Action in Alfred and Send to Trash (another Automation Task) the file. Link to comment
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now