After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 764190 - Couldn't find the project I'm working on
Couldn't find the project I'm working on
Status: RESOLVED FIXED
Product: gnome-builder
Classification: Other
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: GNOME Builder Maintainers
GNOME Builder Maintainers
Depends on:
Blocks:
 
 
Reported: 2016-03-25 13:05 UTC by Jonh Wendell
Modified: 2016-05-05 10:23 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
context: allow projects in .local (1.39 KB, patch)
2016-05-05 10:22 UTC, Christian Hergert
committed Details | Review

Description Jonh Wendell 2016-03-25 13:05:47 UTC
I've been working on a project for a few days now. Every time I open builder I have to create a new project, because it's not listed in builder's initial page.

The project is not a git project [yet]. It's just a directory with a bunch of files (don't know if it's relevant).
Comment 1 sébastien lafargue 2016-03-25 13:22:59 UTC
currently, only autotools projects ( that is with at least a configure.ac file ) are show by the greeter
Comment 2 Jonh Wendell 2016-03-25 13:25:17 UTC
Right, but why close this as NOTABUG? At least it's a valid enhancement request.
Comment 3 Alexandre Franke 2016-03-25 13:46:09 UTC
The particular issue you reported is indeed not a bug, since it's just something that's not implemented (rather something that doesn't work and that should be working already).

If you want a specific type of projects to be recognized, you should open a bug report about it. For reference we already have bug #743280 for Meson and bug #751761 for cmake.
Comment 4 Alexandre Franke 2016-03-25 13:47:07 UTC
By the way the greeter as a button that allows you to add projects that are not in the list.
Comment 5 Jonh Wendell 2016-03-25 13:52:57 UTC
That's exactly what this bug report is about.

The button you mentioned (New), which creates a new project, doesn't make it persistent. Every time I open builder I have to press that button, navigate to the directory where my project lives and create it.

Regarding the project being attached to a build system: Can't I just have a project which is a simple directory with a bunch of files in it?
Comment 6 Alexandre Franke 2016-03-25 13:57:03 UTC
(In reply to Jonh Wendell from comment #5)
> The button you mentioned (New), which creates a new project, doesn't make it
> persistent. Every time I open builder I have to press that button, navigate
> to the directory where my project lives and create it.

Ah. That works for me, so there's indeed a bug showing up for you.

> Regarding the project being attached to a build system: Can't I just have a
> project which is a simple directory with a bunch of files in it?

Yes, you can. I just misunderstood what your report was about. Maybe the title could be rephrased to reflect on the actual issue?
Comment 7 Jonh Wendell 2016-03-25 13:58:26 UTC
I'm using master branch from git
Comment 8 Akshaya Kakkilaya 2016-03-25 14:13:47 UTC
I just tried opening an empty folder from "New". The empty folder shows up under "Recent Projects" when I restart Builder.

The folder will not appear under recents if:
1) it is outside the user's home directory
2) it is a hidden folder(dot preceded)
3) it is under Downloads/
Comment 9 Akshaya Kakkilaya 2016-03-25 14:20:58 UTC
refer bug #750818
Comment 10 Jonh Wendell 2016-03-25 14:31:38 UTC
A-ha! That's the reason: It's inside a hidden folder!

Why this behavior? For the context: I'm working on a gnome Shell extension,
which lives inside ~/.local/share/gnome-shell...
Comment 11 Akshaya Kakkilaya 2016-03-25 14:59:35 UTC
(In reply to Jonh Wendell from comment #10)

I need to make a correction. The folder will not be listed under recents if it's relative path within home directory is dot preceded. 

> Why this behavior? For the context: I'm working on a gnome Shell extension,
> which lives inside ~/.local/share/gnome-shell...

This condition is applied so that opening files within .local, .cache or .config does not list them as projects. see bug #750818.
Comment 12 Christian Hergert 2016-05-05 10:22:20 UTC
Created attachment 327334 [details] [review]
context: allow projects in .local

We often get bug reports on irc/bugzilla about created projects being
ignored. It is usually related to creating gnome-shell extensions in the
location that gnome-shell reads them from.

Might as well just allow creating projects in .local.
Comment 13 Christian Hergert 2016-05-05 10:23:24 UTC
Also pushed to stable branch for 3.20.4.

Attachment 327334 [details] pushed as 0fb5a58 - context: allow projects in .local