Re: Bidi support

[Stefan Monnier]

> I already did.  I have a source tree where the bidi code is merged
> with the current trunk, and I merge them as needed all the time.

Good, thank you.

>> Agreed.  The more I think about it, the more I think we need to open
>> a new branch for "what will become emacs-24".  Kind of like what we did
>> with the emacs-unicode branch.  I think bidi should be one of the first
>> features to install on that branch.

> Why not the other way around: make a branch for Emacs 23.x, and leave
> Emacs 24 on the trunk?  I think Yidong suggested that, and I think
> it's a better idea.

Sure.  I tend to forget about CVS's idea that one of the branches is
deemed special.  So yes, "open a new branch for emacw-24" here would
mean "create a new CVS branch for Emacs-23.2 and use the trunk for
Emacs-24".
[ I'm eagerly waiting to switch over to a system where
  branches are easier to use. ]

> We never left the mainline of our development on a branch before.

Actually we did for emacs-unicode ;-)
Not that it matters, tho.

>> I think it will stay unstable for too long, so it's not good enough for
>> the current trunk (which I'd like to keep for shorter-term changes).

> I guess that's a NO, but please note that this code, however unstable,
> is never executed unless the user flips a variable.  So I don't see
> how it can destabilize the default configuration by being
> dead ballast.

I know, but somehow having such experimental code there makes me uneasy.


        Stefan