On Mon, Dec 15, 2003 at 10:39:51AM +, Angus Leeming wrote:
> On Monday 15 December 2003 10:34 am, Andre Poenitz wrote:
> > > I do think that somethng should be done, however. Moving forward with
> > > a flawed design is a bad idea IMO.
> >
> > I don't have a strong opinion here as I never used
On Monday 15 December 2003 10:34 am, Andre Poenitz wrote:
> > I do think that somethng should be done, however. Moving forward with
> > a flawed design is a bad idea IMO.
>
> I don't have a strong opinion here as I never used that feature myself.
That's because Branches are a new feature. I can se
On Sun, Dec 14, 2003 at 04:50:42PM +, Angus Leeming wrote:
> The branches code enable the user to create a custom color for each
> branch. That is, new colors are defined for a particular buffer.
> However, these colors are stored in the system-wide lcolors variable.
> That's a design flaw.
Martin Vermeer wrote:
>> The branches code enable the user to create a custom color for each
>> branch. That is, new colors are defined for a particular buffer.
>> However, these colors are stored in the system-wide lcolors
>> variable. That's a design flaw.
>>
>> It seems to me that there are two
On Sun, Dec 14, 2003 at 04:50:42PM +, Angus Leeming spake thusly:
> The branches code enable the user to create a custom color for each
> branch. That is, new colors are defined for a particular buffer.
> However, these colors are stored in the system-wide lcolors variable.
> That's a desi
The branches code enable the user to create a custom color for each
branch. That is, new colors are defined for a particular buffer.
However, these colors are stored in the system-wide lcolors variable.
That's a design flaw.
It seems to me that there are two possible solutions.
1. Add an LColor
