On 08/11/2011 21:11, Lex Trotman wrote:
[...]
Unfortunately this is a requirement for any overriding scheme like
stubs, if all the settings are written to the users project file no
settings will be read from the stub file.
No, what I would do is:
* Read the user config file content
* Append
On Sat, Nov 12, 2011 at 3:26 AM, Nick Treleaven
nick.trelea...@btinternet.com wrote:
On 08/11/2011 21:11, Lex Trotman wrote:
[...]
Unfortunately this is a requirement for any overriding scheme like
stubs, if all the settings are written to the users project file no
settings will be read
On Wed, 9 Nov 2011 08:11:45 +1100
Lex Trotman ele...@gmail.com wrote:
The simple solution is to add only save if changed as a new feature
in stash so its easy to use for the settings that need it.
If that's the easy solution... Our instance will not know if another
instance has changed
On Thu, Nov 10, 2011 at 7:45 AM, Dimitar Zhekov
dimitar.zhe...@gmail.com wrote:
On Wed, 9 Nov 2011 08:11:45 +1100
Lex Trotman ele...@gmail.com wrote:
The simple solution is to add only save if changed as a new feature
in stash so its easy to use for the settings that need it.
If that's the
On 04/11/2011 21:31, Lex Trotman wrote:
[...]
I see that 'based on' could be useful for making subprojects, and could be
added to my proposal.
As I see it, this is the same as your proposal, just that we have an
explicit pointer from the project file to the stub project file so
they don't
[...]
Unfortunately this is a requirement for any overriding scheme like
stubs, if all the settings are written to the users project file no
settings will be read from the stub file.
No, what I would do is:
* Read the user config file content
* Append the content of the VCS file
* Pass
Am 03.11.2011 15:45, schrieb Nick Treleaven:
My solution:
A foo.geanystub project file goes in version control. It is never
written to. It should be prepared by manually editing a copy of a
local project file.
On opening a foo.geanystub file, Geany creates foo.geany in the same
path then
(There was no reply-to list address set for Thomas's mail (weird), so
I'm now sending this to the list - possibly a Thunderbird issue).
On 04/11/2011 09:56, Thomas Martitz wrote:
Am 03.11.2011 15:45, schrieb Nick Treleaven:
My solution:
A foo.geanystub project file goes in version control.
On 04/11/2011 15:22, Nick Treleaven wrote:
That solution seems awkward to me. Especially the creation part where
you need to copy, then hand-edit.
Normally you don't need to touch such project files at all, but you
require not only that, but also that the people know which parts to take
out.
[...]
I see that 'based on' could be useful for making subprojects, and could be
added to my proposal.
As I see it, this is the same as your proposal, just that we have an
explicit pointer from the project file to the stub project file so
they don't *have* to be in the same directory and we
Hi,
I think I can improve on Lex's recent proposal to split up project
settings into two files, one for version control and one for local changes.
The problems with that are:
* How do we decide which settings are in each - e.g. build menu commands
- a project might want to override the make
On 4 November 2011 01:45, Nick Treleaven nick.trelea...@btinternet.com wrote:
Hi,
I think I can improve on Lex's recent proposal to split up project settings
into two files, one for version control and one for local changes.
The problems with that are:
* How do we decide which settings are
12 matches
Mail list logo
