Allan Rae <[EMAIL PROTECTED]> writes:
| On Fri, 18 Aug 2000, Juergen Vigna wrote:
|
| >
| > On 17-Aug-2000 Lars Gullik Bjønnes wrote:
| > >
| > > NEW_INSETS should be enabled at the same time, because:
| >
| > Well to answer you what I think: [...]
| > Why activate NEW_TABULAR and not NEW_INSETS: [...]
| >
| > So you see while the tabular-inset IS ready for prime-time most (it reads
| > all old code correct I tried this with various files and also the UserGuide!)
| > the other text inset still need lot's of work.
| [...]
| > My vote is 1.1.6 with ONLY NEW_TABULAR activated!
I think I'd be willing to do this for 1.1.6.
| I'm willing to compromise on my 1.1.6-with-no-NEW_ANYTHING by suggesting:
|
| ./configure --with-bleeding-edge=tabular \
| --with-bleeding-edge=insets
Hate it already... the fileformats will not be compatible.
| This makes it even easier for people to try the new stuff while still
| recognising that it may be buggy. Besides, having a --with-bleeding-edge
| option would be a fun and useful addition ;-)
No, not really.
Lgb
