Alfred-Chris Posted October 11 Share Posted October 11 Hi I am using the work flow "recent files". But when I enter rf and acivate recent files, I only shows very random old files from 2014 and not files I recently opened. I deleted and reinstalled the workflow, but it didn't help. Is anyone using the workflow successfully and could help me debug this? Link to comment
Alfred-Chris Posted October 11 Author Share Posted October 11 Ok, I think I might need to adjust the path to FD FD is installed in > /opt/homebrew/Cellar/fd/10.2.0/bin When I adjust the path I get a permission error in the debugging. Do you think I am on the right track and can someone help me how to fix this? > [14:16:39.228] Recent Files[Script Filter] Queuing argument '(null)' > [14:16:39.260] Recent Files[Script Filter] Script with argv '(null)' finished > [14:16:39.265] ERROR: Recent Files[Script Filter] Code 1: Traceback (most recent call last): > File "/Users/xx/Seafile/CK/IT/Alfred_Settings/Alfred.alfredpreferences/workflows/user.workflow.2BEB7D96-987A-4A57-8168-E51EBA83B0F3/./recent_files", line 350, in <module> > program.run() > File "/Users/xx/Seafile/CK/IT/Alfred_Settings/Alfred.alfredpreferences/workflows/user.workflow.2BEB7D96-987A-4A57-8168-E51EBA83B0F3/./recent_files", line 333, in run > files = self.find_recent_files() > ^^^^^^^^^^^^^^^^^^^^^^^^ > File "/Users/ck/Seafile/CK/IT/Alfred_Settings/Alfred.alfredpreferences/workflows/user.workflow.2BEB7D96-987A-4A57-8168-E51EBA83B0F3/./recent_files", line 248, in find_recent_files > result = subprocess.Popen( > ^^^^^^^^^^^^^^^^^ > File "/opt/homebrew/Cellar/python@3.12/3.12.6/Frameworks/Python.framework/Versions/3.12/lib/python3.12/subprocess.py", line 1026, in __init__ > self._execute_child(args, executable, preexec_fn, close_fds, > File "/opt/homebrew/Cellar/python@3.12/3.12.6/Frameworks/Python.framework/Versions/3.12/lib/python3.12/subprocess.py", line 1955, in _execute_child > raise child_exception_type(errno_num, err_msg, err_filename) > PermissionError: [Errno 13] Permission denied: '/opt/homebrew/Cellar/fd/10.2.0/bin' Link to comment
FireFingers21 Posted October 12 Share Posted October 12 @Alfred-Chris Did you try reinstalling fd as well? I was able to get the workflow working immediately without touching any of the configuration options. Link to comment
Alfred-Chris Posted October 14 Author Share Posted October 14 On 10/12/2024 at 7:28 AM, FireFingers21 said: @Alfred-Chris Did you try reinstalling fd as well? I was able to get the workflow working immediately without touching any of the configuration options. Thanks FireFingers Did you install fd with brew as well? Link to comment
FireFingers21 Posted October 14 Share Posted October 14 1 hour ago, Alfred-Chris said: Did you install fd with brew as well? Yes I did. I originally used the Gallery's Dependencies feature, but installing it from the Terminal with brew install fd worked too. Link to comment
Alfred-Chris Posted October 14 Author Share Posted October 14 Thanks for letting me know Can you tell me how this line looks like in your workflow configuration? Link to comment
vitor Posted October 14 Share Posted October 14 It’s not likely that the installation of fd is the problem. It was already in your PATH and the workflow worked, it just wasn’t giving you the information you thought was relevant. If fd were the problem it would have failed instead like it did the first time you changed it. You should leave the setting be like it was. I recommend you contact the developer on GitHub by opening a new issue (but I’ll ping them here just in case: @jy-gh) and explain the issue in detail, including the full debugger output and information on the files you see and the ones you expected to see. From the description, the cause of what you’re seeing is bound to be either a logic error in the workflow, a misconfiguration, or some misunderstanding. For example, maybe you last remember opening those files in 2014 (or that’s the year they were created) but some process on your machine modified them recently and thus the workflow would be working as expected (changing a modification date does not require editing the contents). Those files are likely to hold the key to the next step. Start by doing a right-click → Get Info on them and make sure the Modified date really is what you think it should be, and mention that in the report. Link to comment
Alfred-Chris Posted October 14 Author Share Posted October 14 Thanks Vitor! I will do that Link to comment
jy-gh Posted October 16 Share Posted October 16 I have reached out to @Alfred-Chris to see if I can help troubleshoot this. (The @ notice really helped, thank you @vitor!) @vitor and @FireFingers21 -- thank you both for helping with this. Alfred's community is so helpful and willing to pitch it, it's a pleasure being a part of it. - jy-gh vitor 1 Link to comment
Alfred-Chris Posted October 16 Author Share Posted October 16 Hi jy-gh Thanks for your message. Sorry but just in this minute I files an issue report in github. Your message and my issue report must have "crossed". I am seeing your message and will get back to you there. 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