Here is a cleanup fix
--
Kayvan A. Sylvan | Proud husband of | Father to my kids:
Sylvan Associates, Inc. | Laura Isabella Sylvan | Katherine Yelena (8/8/89)
http://sylvan.com/~kayvan | "crown of her husband" | Robin Gregory (2/28/92)
Index: src/ChangeLog
==
On Sun, Mar 21, 2004 at 07:53:13PM +0100, Alfredo Braunstein wrote:
> PS: I hope it doesn't mean you are stupid. I've spent more than two hours
> for some of the bugs I've fixed. ;-)
Did you spend more than 2 hours even trying to get some handle on the
problem though ?
john
--
"Spammers get ST
I want to Insert->File->ASCII as Lines, but this option is grayed out
along with "LyX Document" and "Ascii as paragraphs".
--
Kayvan A. Sylvan | Proud husband of | Father to my kids:
Sylvan Associates, Inc. | Laura Isabella Sylvan | Katherine Yelena (8/8/89)
http://sylvan.com/~k
I can create a math inset (C-m) but I can not navigate into it.
Trying to move the cursor in causes the cursor to bounce to the top of
the document.
--
Kayvan A. Sylvan | Proud husband of | Father to my kids:
Sylvan Associates, Inc. | Laura Isabella Sylvan | Katherine Yelena (8
I don't know when this bug popped up, but I can no longer select with
the mouse (click-hold-drag) although the SHIFT-move method of text
selection seems to work.
--
Kayvan A. Sylvan | Proud husband of | Father to my kids:
Sylvan Associates, Inc. | Laura Isabella Sylvan | Katheri
I have a lyx document with a branch called "titlepage" (for when I want
to turn a custom titlepage off or on).
When LyX reads it, I see:
no text in updateScrollbar
Buffer::Buffer()
LColor::getFromLyXName: Unknown color "titlepage"
It does not seem to affect branch function, however.
John Levon wrote:
> So either I'm stupid, or the bugs aren't quite as easy
> to find as you say...
I'd say that Andrà is exaggerating. The lyx tree is huge and there is still
plenty of super-ugly stuff around in the core (take for instance the
recursive leftMargin stuff etc.). And tables are prob
this patch
- renames MetricsBase::textwidth -> maxwidth (easier for the non-LaTeX
experts out here)
- adds a MetricsInfo::remaining_width member
- put children metrics calls into the rebreak loop again, passing this
remaining_width.
It doesn't use it yet, so behaviour should be unchanged.
Ok to
Andre Poenitz wrote:
>> option 2) he uses only w -> we get current cvs behaviour
>> option 3) use a mixture of the two, choosing the one that spans less
>> vertical space (the inlined version uses a line less, but then has less
>> horizontal space to accomodate the remaining rows and so there will
On Sun, Mar 21, 2004 at 03:24:59PM +0100, Andre Poenitz wrote:
> More importantly, I think it would be generally a good idea if the 'Old
> gang' had a look at the core in its current incarnation. It has changed
> quite a bit, so some things that were true a year ago aren't true
> anymore (and the
Am Samstag, 20. März 2004 21:14 schrieb Andre Poenitz:
> On Sat, Mar 20, 2004 at 12:29:09PM +0100, Alfredo Braunstein wrote:
> > Now what happens if we have the inset in the first char of an indented
line?
> >
> ><--- s --->
> >[open inset] blah blah blah
>
On Sat, Mar 20, 2004 at 12:29:09PM +0100, Alfredo Braunstein wrote:
> < s ->
> blah blah blah blah [open inset]
> ++
> ||
> ||
>
> |
On Sat, Mar 20, 2004 at 05:17:35PM +0100, Lars Gullik Bjønnes wrote:
> Andre Poenitz <[EMAIL PROTECTED]> writes:
>
> | And note that this is using 'stupid std::vector' which make full deep
> | copies of all insets. It is straight-forward to implement a 'swap'-based
> | vector<>::insert which can a
On Sat, Mar 20, 2004 at 05:20:46PM +0100, Lars Gullik Bjønnes wrote:
> Alfredo Braunstein <[EMAIL PROTECTED]> writes:
>
> | In any case, I'm not really against the move. If only we could get more
> | people fixing cvs, it wouldn't be unwise. Right now, I don't know.
>
> I'd be happy to help more,
Angus Leeming wrote:
> Most important comment is that all these solutions are temporary hacks
> if the ultimate goal is "an inset is three boxes". IOW, I don't think
> we should be t worried about which ever choice is implemented.
Is not clear to me if this is the general consensus. I may be
Georg Baum wrote:
> Possible solution: Make LaTeXFeatures::buffer_ a pointer instead of
> a reference (InsetInclude::validate() is the only place where it is
> needed), and do the following in InsetInclude::validate():
>
> Buffer const * buffer = features.buffer();
> ...
> if (tmp
Alfredo Braunstein wrote:
> I've tried to make some sense on the last discussions on rebreaking,
> did some experimaentations with 1.3.x, and still I don't see a clear
> path.
[Compelling discussion snipped.]
> Any /constructive/ comment is welcomed.
Most important comment is that all these sol
John Levon wrote:
> That's correct. Very (very) few system calls are usable in a signal
> context. This includes anything printf-like.
>
> You can refer to the UNIX standards for more info, but basically,
> setting a sigatomic_t variable to TRUE or equivalent is the way to
> go.
I've been readin
Jean-Marc Lasgouttes wrote:
>> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
>
> Angus> Branches can define arbitrary new colours as their background
> Angus> colour. I believe that the same mechanism can also be used to
> Angus> add arbitrary character colours also.
>
> Where is the
There is a problem related to nested included files that has not been solved
yet. InsetInclude::validate() gets its buffer like this:
Buffer const & buffer = features.buffer();
Lateron, the included file is validated:
if (tmp)
tmp->validate(features);
LaTeXFeatu
Kayvan A. Sylvan wrote:
> A cvs diff patch is attached.
Commited.
Alfredo
Am Mittwoch, 17. März 2004 17:13 schrieb Angus Leeming:
> Georg Baum wrote:
> > I propose not to introduce a new variable but to
> > change the meaning of $$FName from
> > "The filename exactly as the user entered it"
> > to
> > "The absolute filename (if the user entered an absolute
> > na
22 matches
Mail list logo
