What happens if user supplies two directories on command line, where both contain a project?

Previously, the project/folder would be opened/created, files added, then the next project/folder would be opened/created (closing the previous), etc. This is problematic when opening multiple files with shell globs that could refer to folders. So I'm changed the feature to use a command-line flag.

IMHO opening a project just by specifying it's directory might be confusing. If I'd want to open a project, I'd pass it's project file as argument (which already works well).

Thank you for reminding me that I need to update the manual.

The intent is to add folder handling. The mechanism is via projects. (Other editors/IDEs have been reported to behave similarly.) This is useful when combined with a plugin that displays folder contents in the sidebar. Otherwise, it's not very useful and can just be ignored.

As for passing directory on command line, much more intuitive behaviour (again just my own opinion) would be to open all files in the directory.

This behavior would also have problems with shell globs. Many folders have thousands of files, and Geany would appear to be frozen/crashed/broken while loading so many files. The current Geany behavior is to drop folders in some cases (currently, initial startup and socket behavior do not match; I've added changes to address this).

Creating a new project could be quite a surprise, especially for users who don't usually use projects.

Switching to using a command-line flag should resolve this. From the menu, there are clues that Projects are involved.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.