Re: lyx-1.1.5cvs bug: All protected spaces export as ~

2000-03-09 Thread Jean-Marc Lasgouttes
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes: Lars> Will more thatn the buffer parameters be needed then? We may need info at the buffer level, but also at the paragraph level (maybe the current layout is enough). JMarc

Re: lyx-1.1.5cvs bug: All protected spaces export as ~

2000-03-08 Thread Lars Gullik Bjønnes
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes: | > "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes: | | Lars> "Kayvan A. Sylvan" <[EMAIL PROTECTED]> writes: | > | > No it | Lars> doesen't but it absolutely should. The best (less maintence | > | Lars> problems) would be if this knw

Re: lyx-1.1.5cvs bug: All protected spaces export as ~

2000-03-08 Thread Jean-Marc Lasgouttes
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes: Lars> "Kayvan A. Sylvan" <[EMAIL PROTECTED]> writes: | > | > No it Lars> doesen't but it absolutely should. The best (less maintence | > Lars> problems) would be if this knwledge about the surounding Lars> envronment | > could be don

Re: lyx-1.1.5cvs bug: All protected spaces export as ~

2000-03-07 Thread Lars Gullik Bjønnes
"Kayvan A. Sylvan" <[EMAIL PROTECTED]> writes: | > | > No it doesen't but it absolutely should. The best (less maintence | > problems) would be if this knwledge about the surounding envronment | > could be done with arguments. | > | | Do you want to make that change or should I? | | I can e

Re: lyx-1.1.5cvs bug: All protected spaces export as ~

2000-03-06 Thread Kayvan A. Sylvan
On Tue, Mar 07, 2000 at 02:21:13AM +0100, Lars Gullik Bjønnes wrote: > "Kayvan A. Sylvan" <[EMAIL PROTECTED]> writes: > > | On second thought, don't check in my diffs. > | > | I'm looking at and fixing your freespacing hack. > > I can asure you that it is not mine... *laugh* -- Kayvan A. Syl

Re: lyx-1.1.5cvs bug: All protected spaces export as ~

2000-03-06 Thread Lars Gullik Bjønnes
"Kayvan A. Sylvan" <[EMAIL PROTECTED]> writes: | > > In what way is this different from freespacing? | > | > I assume you mean freespacing? | > | > It's supposed to do the same thing, but the freespacing hack does not work | > and I didn't find it till after I'd implemented mine. :-) | | On s

Re: lyx-1.1.5cvs bug: All protected spaces export as ~

2000-03-06 Thread Kayvan A. Sylvan
> > No it doesen't but it absolutely should. The best (less maintence > problems) would be if this knwledge about the surounding envronment > could be done with arguments. > Do you want to make that change or should I? I can easily pass the freespacing bool around when the inset->latex() fun

Re: lyx-1.1.5cvs bug: All protected spaces export as ~

2000-03-06 Thread Lars Gullik Bjønnes
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes: | > "Kayvan" == Kayvan A Sylvan <[EMAIL PROTECTED]> writes: | | Kayvan> Does an inset have any access to its containing paragraph? If | Kayvan> so, it would be easy for the InsetSpecialChar::Latex to output | Kayvan> a space in that case. | |

Re: lyx-1.1.5cvs bug: All protected spaces export as ~

2000-03-06 Thread Jean-Marc Lasgouttes
> "Kayvan" == Kayvan A Sylvan <[EMAIL PROTECTED]> writes: Kayvan> Does an inset have any access to its containing paragraph? If Kayvan> so, it would be easy for the InsetSpecialChar::Latex to output Kayvan> a space in that case. I guess Lars is the best person to answer this question. With t

Re: lyx-1.1.5cvs bug: All protected spaces export as ~

2000-03-06 Thread Kayvan A. Sylvan
> > Kayvan> 3) Patch the input routine in lyxfunc.C so that the user's > Kayvan> attempt to enter a protected-space while in a free_spacing > Kayvan> layout is thwarted. > > And what if a normal paragraph containing a protected space is changed > to a freespaced paragraph? Hmmm... Good point.

Re: lyx-1.1.5cvs bug: All protected spaces export as ~

2000-03-06 Thread Jean-Marc Lasgouttes
> "Kayvan" == Kayvan A Sylvan <[EMAIL PROTECTED]> writes: Kayvan> After shooting my mouth off before, now I have a correct fix. Kayvan> This one basically does a few things right (as opposed to my Kayvan> previous fix): Kayvan> 1) It continues to work with old Literate Lyx files, thus Kayvan

Re: lyx-1.1.5cvs bug: All protected spaces export as ~

2000-03-06 Thread Kayvan A. Sylvan
On Sun, Mar 05, 2000 at 06:10:36PM -0800, Kayvan A. Sylvan wrote: > > In what way is this different from preespacing? > > I assume you mean freespacing? > > It's supposed to do the same thing, but the freespacing hack does not work > and I didn't find it till after I'd implemented mine. :-) Af

Re: lyx-1.1.5cvs bug: All protected spaces export as ~

2000-03-06 Thread Kayvan A. Sylvan
> > In what way is this different from freespacing? > > I assume you mean freespacing? > > It's supposed to do the same thing, but the freespacing hack does not work > and I didn't find it till after I'd implemented mine. :-) On second thought, don't check in my diffs. I'm looking at and fixi

Re: lyx-1.1.5cvs bug: All protected spaces export as ~

2000-03-05 Thread Kayvan A. Sylvan
On Sat, Mar 04, 2000 at 03:08:38PM -0800, Kayvan A. Sylvan wrote: > > > Hardcoding anything for Scrap layout is not an option unless it is in > > the layout file. This is also a more general problem. > > I'm working on it. I've added a new boolean AllowMultipleSpaces to the > layout file and am m

Re: lyx-1.1.5cvs bug: All protected spaces export as ~

2000-03-04 Thread Kayvan A. Sylvan
> So this is the free spacing hack... > My suggestion is that someone help me get this right in cvs with the > new InsetSpecialchar for protected spaces. Hmmm... What would be involved here? > | My suggestion is that inside Scrap layouts, the protected-space should output > | just a space (bette

Re: lyx-1.1.5cvs bug: All protected spaces export as ~

2000-03-04 Thread Lars Gullik Bjønnes
"Kayvan A. Sylvan" <[EMAIL PROTECTED]> writes: | Hi everyone, | | In the latest lyx-1.1.5cvs: | | All protected spaces (created by Ctl-SPC) are getting output as the ~ | character. | | While this seems to work for straight LaTeX, it does *not* work for noweb | output (for literate programming)

lyx-1.1.5cvs bug: All protected spaces export as ~

2000-03-03 Thread Kayvan A. Sylvan
Hi everyone, In the latest lyx-1.1.5cvs: All protected spaces (created by Ctl-SPC) are getting output as the ~ character. While this seems to work for straight LaTeX, it does *not* work for noweb output (for literate programming) and generates bad LaTeX output in that case too. My suggestion i