To make a concrete UI suggestion, I think the file menu could be changed to:
```
New File
New File (with template) >...
Open Folder as Project...
Open File...
Open Selected File
Recent Files
```
... and the `Properties` entry expanded to a sub menu:
```
Properties > Current File
Properties >
This is *the* major reason why I personally don't use geany :cry: I love the
new fancy "open folder" concept where the folder just magically is shown as a
complete file tree, but Geany only allows me to open single files or a project
file by default. It just feels clumsy and inflexible, in
> Yes, this is a long standing issue. Having a separate session file would fix
> this.
Yeah, there are discussions going back to 2013 on the Geany devel ML, eg
https://www.mail-archive.com/devel@lists.geany.org/msg01278.html was the first
that searching for "session file" found, but no actual
> the file list and project config are the same file so it's simply not
> possible to check it into VCS.
Yes, this is a long and standing issue. Having a separate session file would
fix this. Conceivably other project settings would fit there too, not just
session info.
--
You are receiving
> The current really lightweight "named sessions" feature Geany has is really
> good in many cases, so it should be kept (but renamed)
There are many project specific settings besides sessions.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or
@kugel-
> I think projects in Geany need a complete rethinking and rework ...
Agreed.
I don't think Geany does projects, and the feature it has thats called
"projects" is misnamed. That causes people to expect something like all the
other IDEs "projects" features. The current really
> Projects are currently rather poor. Annoying to set up and they don't offer
> truly useful features that justify setting them up. This is why so many
> project plugins exist, but they rather add more features to the project
> instead of making the setup easier. But those plugins cross the
TL;DR: I think projects in Geany need a complete rethinking and rework
I agree with the principle here. Geany wants to be fast and small but with
powerful features. So I agree that we should ship a bare minimum feature-set to
turn a "drive-by git clone" into a (temporary) project, with some
> yes, but which plugin features will you choose to make core?
It's actually less "features" than even the builtin project support, let alone
plugins. You just run `geany some/dir` and it takes the directory passed to it
as the base path of the project, and the basename of the directory as the
@codebrainz yes, but __which__ plugin features will you choose to make core?
The fact that there is more than one says to me that there isn't agreement on
what those features should be, and then people like me don't have the project
file in the git directory but the one above, that also
Related to and/or duplicate of #450, #1171,
http://geany-users.466218.n3.nabble.com/Geany-Users-open-folder-td4025296.html
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
@chrisgraham I fully agree, and have been considering making a pull request to
do this, or least investigating how difficult it would be. Being able to change
into a source directory and type `geany .` and not have fiddle with
making/closing/opening projects would be super handy. SublimeText
There are three or four project plugins available for Geany which implement
various versions of the "one directory" paradigm. Perhaps you should check out
those.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Hi, I'm coming from TextMate 2 on Mac, and TextMate does a great job with
projects - by essentially making it invisible (frictionless).
You just open a folder, and that folder automatically becomes a project.
Geany could easily do something similar in my opinion. I don't know if the
GNOME file
14 matches
Mail list logo
