Managing Recent Projects

[Satheeshsk369]

When i open the flow editor inside the zig project flow . It takes around ~3.8MB of RAM.
And When i open the editor in home directory, It takes around ~60MB of RAM, which may be OK..
But When i open the editor in home directory and switched to the zig project i mentioned using recent projects, the memory added up to ~63.8MB of RAM.

I tested the same for few large files, and every files show ~ +60MB diff from opening on same directory to opening from home directory.

Feature Request:-

• Lazy Loading: Load only the current file or current project will be helpful
• Delete Recent Projects: I'm using yazi + flow to view the files in the terminal. But flow save each directory of viewing files as a recent project which i don't want. so giving the option to delete the recent project will help to manage it.
• Opening New Project: cli command like flow -p <dir> to manually open the project directory, instead of automatically recognizing it.
• List all file in the project: renaming command e -> l to list the files in current project, which what a recent files now doing.
• Recent Files: Get track of the files viewed or edited in a recent files (upto certain limit 50 or 100), irrespective of the current project.

[neurocyte]

I have converted this to a discussion to work out the details. We can create new feature request issues for individual actionable items.

Feature Request:-

• Lazy Loading: Load only the current file or current project will be helpful

It's not clear what exactly you mean by this. Flow only loads files or projects on demand. I suspect you mean that flow should not load the project file list in the background when a project is opened. This would mean that the file list is not instantly available when the user requests the project recent files list. As the list is loaded asyncronously I don't see what benefit you would get by not loading it.

• Delete Recent Projects: I'm using yazi + flow to view the files in the terminal. But flow save each directory of viewing files as a recent project which i don't want. so giving the option to delete the recent project will help to manage it.

Yes, close_project and delete_project commands are needed. I have started work on them, but it is still incomplete. You are welcome to add a feature request PR, or just wait for me to get around to it.

• Opening New Project: cli command like flow -p <dir> to manually open the project directory, instead of automatically recognizing it.

Nice idea. This could be very useful.

• List all file in the project: renaming command e -> l to list the files in current project, which what a recent files now doing.

No sure I understand this one. You want to rename the Open recent file command to List all files in project and change the keybinding? I'm not sure I see the point in that, but remember that you can change your keybindings locally to whatever you want.

• Recent Files: Get track of the files viewed or edited in a recent files (upto certain limit 50 or 100), irrespective of the current project.

I can see how a global recent files list might be useful. You're welcome to add a feature request PR.

[Satheeshsk369]

Opening the same projects in flow, by calling from project dir and the home dir the memory differs. I thought that flow memory influenced by where it is calling instead of what the projects it opened. It may be it loads all the recent projects. That's asking I'm asking for lazy loading to take only the current project into memory.

[neurocyte]

• Delete Recent Projects: I'm using yazi + flow to view the files in the terminal. But flow save each directory of viewing files as a recent project which i don't want. so giving the option to delete the recent project will help to manage it.

Yes, close_project and delete_project commands are needed. I have started work on them, but it is still incomplete. You are welcome to add a feature request PR, or just wait for me to get around to it.

close_project is now implemented. You can close an open project by pressing del in the recent projects list. You cannot close the currently project.

[neurocyte]

So, in this case no need a new cli args and global recent files. just remove the feature, adding new recent projects by calling flow without args.

So you want to open flow with no current project at all? That doesn't really make sense for flow. Many features require some concept of a current working directory. Perhaps you just want a mode where the current project is not saved if it doesn't already exist?

[neurocyte]

So, in this case no need a new cli args and global recent files. just remove the feature, adding new recent projects by calling flow without args.

I have added a --no-persist command line option to stop flow from saving the current project if it is new.

[Satheeshsk369]

That's Good 👍

[plyght]

@Satheeshsk369 @neurocyte Not sure if this is part of the original request, but a tree file manager would be nice!

[neurocyte]

You should start a new discussion for that.