Re: Proposal: Project settings split

On 11-10-31 04:50 PM, Lex Trotman wrote:
> Hi All,
>
> One area of Geany has been annoying me for some time.
>
> At the moment project settings mix session related settings and truely
> project settings.  The session settings are really user specific
> whilst the project settings are project related.  This means that if
> the project file is in VCS it keeps updating as the session settings
> change.  You can turn session settings off, but then you lose that
> functionality.
>
> The proposal is to separate these, with the session settings stored in
> the user config directory under a projects subdir and the project
> settings stored wherever the user wants.  The options ~/projects or in
> the tree would be available as they are now.
>
> To prevent the config dir getting too cluttered the session files can
> be kept only as long as the project remains in the recent projects
> list. (maybe needs a separate length setting, currently uses
> file_prefs.mru_length)
>
> I will have some time next week, so this thread is to get ideas or
> objections sorted before then.
>

I like the idea of having workspaces/profiles, so that on startup (with 
option to not ask again) and then later through a menu, you can choose 
one of your profiles to load the settings like, indentation, long-line 
marker, colour scheme, etc.

Re: Proposal: Project settings split

On 1 November 2011 11:49, Matthew Brush <mbrush@...> wrote:
> On 11-10-31 04:50 PM, Lex Trotman wrote:
>>
>> Hi All,
>>
>> One area of Geany has been annoying me for some time.
>>
>> At the moment project settings mix session related settings and truely
>> project settings.  The session settings are really user specific
>> whilst the project settings are project related.  This means that if
>> the project file is in VCS it keeps updating as the session settings
>> change.  You can turn session settings off, but then you lose that
>> functionality.
>>
>> The proposal is to separate these, with the session settings stored in
>> the user config directory under a projects subdir and the project
>> settings stored wherever the user wants.  The options ~/projects or in
>> the tree would be available as they are now.
>>
>> To prevent the config dir getting too cluttered the session files can
>> be kept only as long as the project remains in the recent projects
>> list. (maybe needs a separate length setting, currently uses
>> file_prefs.mru_length)
>>
>> I will have some time next week, so this thread is to get ideas or
>> objections sorted before then.
>>
>
> I like the idea of having workspaces/profiles, so that on startup (with
> option to not ask again) and then later through a menu, you can choose one

Re: Geany-Plugins 0.21.1 released

On Mon, 31 Oct 2011 21:34:32 +0100
Dominic Hopf <dmaphy@...> wrote:

> Am Montag, den 31.10.2011, 12:09 +0100 schrieb Frank Lanitz:
> > Hi all, 
> > 
> > Due a little issue with source tarball of 0.21-release of
> > Geany-Plugins 0.21.1 has been released which fixes an issue of non
> > working waf-build system from inside the source tarball. 
> 
> This implies that distro packages using autotools to build to not need
> to update, do they?

Yes. In fact only geanylatex/docs has been effected. 

Cheers, 
Frank 

--

-- 
http://frank.uvena.de/en/

On Mon, 31 Oct 2011 21:34:32 +0100
Dominic Hopf <dmaphy@...> wrote:

> Am Montag, den 31.10.2011, 12:09 +0100 schrieb Frank Lanitz:
> > Hi all, 
> > 
> > Due a little issue with source tarball of 0.21-release of
> > Geany-Plugins 0.21.1 has been released which fixes an issue of non

Re: [RFC] Geany Plugin Names

Am 29.10.2011 08:09, schrieb Lex Trotman:
>
> Although in my, probably poorly informed, opinion, gproject seems to
> encompass most of geanyprj
>

Did anyone heck if geanyprj even works (as intended)? IIUC it's largely 
unmaintained since a very long time. If it turns out broken it should 
just be dropped.

Best regards.

Re: [RFC] Geany Plugin Names

On Tue, Nov 1, 2011 at 09:46, Thomas Martitz
<thomas.martitz@...> wrote:
> Am 29.10.2011 08:09, schrieb Lex Trotman:
>>
>> Although in my, probably poorly informed, opinion, gproject seems to
>> encompass most of geanyprj
>>
>
> Did anyone heck if geanyprj even works (as intended)? IIUC it's largely
> unmaintained since a very long time. If it turns out broken it should just
> be dropped.

Unfortunately I have to admit that GeanyPRJ is indeed quite broken and
lags the whole interface when enabled on a recent build of Geany.

Does Gproject index a whole tree so that symbol and calltip
autocomplete work? I can't seem to find how to enable that, so I guess
not... :(

Harold

Re: Geany-Plugins 0.21.1 released

Am 01.11.2011 07:24, schrieb Frank Lanitz:
> On Mon, 31 Oct 2011 21:34:32 +0100
> Dominic Hopf <dmaphy@...> wrote:
> 
>> Am Montag, den 31.10.2011, 12:09 +0100 schrieb Frank Lanitz:
>>> Hi all, 
>>>
>>> Due a little issue with source tarball of 0.21-release of
>>> Geany-Plugins 0.21.1 has been released which fixes an issue of non
>>> working waf-build system from inside the source tarball. 
>>
>> This implies that distro packages using autotools to build to not need
>> to update, do they?
> 
> Yes. In fact only geanylatex/docs has been effected. 

Well, wasn't 100% honest. I did change a string on updatechecker per
accident - was intended to do post 0.21.x-tree. However, this is not
forcing to build up a new set of packages.

Cheers,
Frank

Re: [RFC] Geany Plugin Names

On 1 November 2011 20:04, Harold Aling <geany@...> wrote:
> On Tue, Nov 1, 2011 at 09:46, Thomas Martitz
> <thomas.martitz@...> wrote:
>> Am 29.10.2011 08:09, schrieb Lex Trotman:
>>>
>>> Although in my, probably poorly informed, opinion, gproject seems to
>>> encompass most of geanyprj
>>>
>>
>> Did anyone heck if geanyprj even works (as intended)? IIUC it's largely
>> unmaintained since a very long time. If it turns out broken it should just
>> be dropped.
>
> Unfortunately I have to admit that GeanyPRJ is indeed quite broken and
> lags the whole interface when enabled on a recent build of Geany.

Dunno about lags, more frags, see attached traceback :)

Cheers
Lex

>
> Does Gproject index a whole tree so that symbol and calltip
> autocomplete work? I can't seem to find how to enable that, so I guess
> not... :(
>
>
> Harold
> _______________________________________________
> Geany-devel mailing list

Re: [RFC] Geany Plugin Names

On Tue, Nov 1, 2011 at 10:04, Harold Aling <geany@...> wrote:
> On Tue, Nov 1, 2011 at 09:46, Thomas Martitz
> <thomas.martitz@...> wrote:
>> Am 29.10.2011 08:09, schrieb Lex Trotman:
>>>
>>> Although in my, probably poorly informed, opinion, gproject seems to
>>> encompass most of geanyprj
>>>
>>
>> Did anyone heck if geanyprj even works (as intended)? IIUC it's largely
>> unmaintained since a very long time. If it turns out broken it should just
>> be dropped.
>
> Unfortunately I have to admit that GeanyPRJ is indeed quite broken and
> lags the whole interface when enabled on a recent build of Geany.
>
> Does Gproject index a whole tree so that symbol and calltip
> autocomplete work? I can't seem to find how to enable that, so I guess
> not... :(

Yes, it should. There's "generate tags for all project files" option
under GProject tab of project properties for that (off by default
because it's too slow for tens-of-thousand file projects I use
GProject for). I hope it works alright, I haven't tested it for quite
some time now but unless there was some change in Geany, it should
work fine.

Cheers,
Jiri

Re: Proposal: Project settings split

On 31/10/2011 23:50, Lex Trotman wrote:
> Hi All,
>
> One area of Geany has been annoying me for some time.
>
> At the moment project settings mix session related settings and truely
> project settings.  The session settings are really user specific
> whilst the project settings are project related.  This means that if
> the project file is in VCS it keeps updating as the session settings
> change.  You can turn session settings off, but then you lose that
> functionality.
>
> The proposal is to separate these, with the session settings stored in
> the user config directory under a projects subdir and the project
> settings stored wherever the user wants.  The options ~/projects or in
> the tree would be available as they are now.

IIUC the functionality would be the same but with different storage?

If so I'm not sure this would be worthwhile complexity. A starting 
project file could be hand edited and put in version control, for people 
to copy into their projects directory, i.e. not use the VC file itself.

Re: Geany Plugins SVN Commit URLs

On Sun, Oct 30, 2011 at 23:25, Matthew Brush <mbrush <at> codebrainz.ca> wrote:
> On 11-10-30 03:03 PM, Frank Lanitz wrote:
>>
>> On Sun, 30 Oct 2011 02:15:33 -0700
>> Matthew Brush<mbrush <at> codebrainz.ca>  wrote:
>>
>>> Hi,
>>>
>>> I haven't heard too much about the Git conversion of Geany Plugins,
>>> but I wanted to offer a suggestion that might improve the commit
>>> messages compared to Geany's.  In the Geany's Git repository there's
>>> links back to the SVN repository in the commit messages (the links
>>> are broken BTW). I was wondering if it would be better to have these
>>> links point to a place we have more control over, for example using a
>>> Geany commit, instead of this in the commit message:
>>>
>>> git-svn-id:
>>> https://geany.svn.sourceforge.net/svnroot/geany/trunk <at> 5970
>>> ea778897-0a13-0410-b9d1-a72fbfd435f5
>>>
>>> We could have something like this:
>>>
>>> git-svn-id:
>>> [ea778897-0a13-0410-b9d1-a72fbfd435f5]
>>> (http://svn.geany.org/svnroot/geany/trunk?rev=5970)
>>>
>>> That way we could make the links work and be able to move the old SVN
>>> repository without breaking all the links in the commit message. I
>>> guess we'd need a little redirect script or something on geany.org.
>>> Note also the use of Markdown link syntax, which might render better