On Sat, Aug 7, 2010 at 01:42, Lex Trotman wrote:
>>
>> I'm a bit worried about having too many special cases (like doing
>> something else when the project file is outside the base directory,
>> especially when it only fixes some problems but introduces another
>> ones) and possibly doing unexpect
>
> I'm a bit worried about having too many special cases (like doing
> something else when the project file is outside the base directory,
> especially when it only fixes some problems but introduces another
> ones) and possibly doing unexpected things (users probably don't
> expect that files sta
On Thu, Aug 5, 2010 at 13:50, Lex Trotman wrote:
> On 5 August 2010 21:20, Jiří Techet wrote:
Sure, I had this in mind - but the patch is completely independent of
where the project file is located. So for instance if you have:
~/foo.geany
and project directory is in: ~/p
Hi,
> On Thu, Aug 5, 2010 at 04:48, Lex Trotman wrote:
>> If I understand correctly this patch depends on the project file being
>> in the project tree, but that is not the Geany default. Some people
>> don't like storing the project file in the project tree because it
>> contains an individual
On 5 August 2010 21:20, Jiří Techet wrote:
>>> Sure, I had this in mind - but the patch is completely independent of
>>> where the project file is located. So for instance if you have:
>>>
>>> ~/foo.geany
>>> and project directory is in: ~/projects/foo
>>> then foo.geany refers to files as: ./proj
>> Sure, I had this in mind - but the patch is completely independent of
>> where the project file is located. So for instance if you have:
>>
>> ~/foo.geany
>> and project directory is in: ~/projects/foo
>> then foo.geany refers to files as: ./projects/foo
>
>
> But then how does it work when I mo
Am 05.08.2010 11:28, schrieb Lex Trotman:
Maybe the paths in foo.geany should be relative to the project base
directory, not the project file, then if you move the project you only
have to correct the base directory and it will all work again.
Cheers
Lex
I also think that'd make probably
On 5 August 2010 19:13, Jiří Techet wrote:
> On Thu, Aug 5, 2010 at 04:48, Lex Trotman wrote:
>> On 5 August 2010 09:59, Jiří Techet wrote:
>>>
>>> Right now projects cannot be moved to other directories without
>>> losing the base directory setting of the project and the list
>>> of open files.
On Thu, Aug 5, 2010 at 04:48, Lex Trotman wrote:
> On 5 August 2010 09:59, Jiří Techet wrote:
>>
>> Right now projects cannot be moved to other directories without
>> losing the base directory setting of the project and the list
>> of open files. This makes the project totally unportable to diffe
On 5 August 2010 09:59, Jiří Techet wrote:
>
> Right now projects cannot be moved to other directories without
> losing the base directory setting of the project and the list
> of open files. This makes the project totally unportable to different
> machines because even if the directory structure
Right now projects cannot be moved to other directories without
losing the base directory setting of the project and the list
of open files. This makes the project totally unportable to different
machines because even if the directory structure under your home is
identical, the user name can be di
11 matches
Mail list logo
