[Bug 666] lyx2lyx cannot load this file successfully (elasticity.lyx)
http://bugzilla.lyx.org/show_bug.cgi?id=666 [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|VERIFIED --- Additional Comments From [EMAIL PROTECTED] 2003-02-17 02:33 --- mass verify. grep -v ApplesWin --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is.
[Bug 666] lyx2lyx cannot load this file successfully (elasticity.lyx)
http://bugzilla.lyx.org/show_bug.cgi?id=666 [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|VERIFIED --- Additional Comments From [EMAIL PROTECTED] 2003-02-17 02:33 --- mass verify. grep -v ApplesWin --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is.
[Bug 666] lyx2lyx cannot load this file successfully (elasticity.lyx)
http://bugzilla.lyx.org/show_bug.cgi?id=666 [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2003-01-08 08:24 --- I will close this bug as the first test case is load correctly. Please open a new bug/reminder as the second file is streching lyx2lyx scope. This is a pre-0.12 and so it is not yet supported for this release. I suspect that the fix should be easy, so if possible I will fix it for 1.3.0 but don't hold your breath. :-) --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is.
[Bug 666] lyx2lyx cannot load this file successfully (elasticity.lyx)
http://bugzilla.lyx.org/show_bug.cgi?id=666 [EMAIL PROTECTED] changed: What|Removed |Added CC||[EMAIL PROTECTED] Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2003-01-08 08:24 --- I will close this bug as the first test case is load correctly. Please open a new bug/reminder as the second file is streching lyx2lyx scope. This is a pre-0.12 and so it is not yet supported for this release. I suspect that the fix should be easy, so if possible I will fix it for 1.3.0 but don't hold your breath. :-) --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is.
Re: Rename 666 to TEX
admitting that LyX can't do it all and providing some way of getting under the hood. I always felt that the whole EvilRedText thing was just an apeasement of the M$ Word crowd, anyhow. Still, Raw or PassThru seems fine by me. Go for 'Raw'. This way we would spare us a flame war on the correct spelling of 'PassThrough' ;-^H^H oh... it's Friday again... Andre' -- André Pönitz . [EMAIL PROTECTED]
Re: Rename 666 to TEX
Andre Poenitz wrote: Let's just keep it as it is now: ERT Encapsulated Raw Text Okokok... I thought you are the math guru, why don't you write $ok^3\ldot$ i see, the problem is the first uppercase letter ... Herbert :-) -- http://www.educat.hu-berlin.de/~voss/lyx/
Re: Rename 666 to TEX
Jose Abilio Oliveira Matos wrote:
On Fri, Aug 03, 2001 at 11:36:10AM +0200, Herbert Voss wrote:
Andre Poenitz wrote:
Let's just keep it as it is now: ERT Encapsulated Raw Text
Okokok...
I thought you are the math guru, why don't you write
$ok^3\ldot$
I'm not defending André, after all he doesn't need it, but even so I
should point some incoherence in your post Herbert...
i see, the problem is the first uppercase letter ...
Herbert :-)
So you are using those punny icons in a Friday, and I thought that you
oh sorry, but I have 45 holidays, 29 in front of me ...
so I don't know what day of weekend is, because it's
absolutely not important for me
$ \stackrel{.\, .}{\stackrel{|}{\smile }} $
well done!
BTW using docbook/xml I would write #x263A; just before you ask
or \smiley with package wasysym and
\Huge\smiley is just the same size than yours.
nice weekend
Herbert
--
http://www.educat.hu-berlin.de/~voss/lyx/
Re: Rename 666 to TEX
> admitting that LyX can't do it all and providing some way of getting > under the hood. I always felt that the whole "EvilRedText" thing was > just an apeasement of the M$ Word crowd, anyhow. > > Still, "Raw" or "PassThru" seems fine by me. Go for 'Raw'. This way we would spare us a flame war on the correct spelling of 'PassThrough' ;-^H^H oh... it's Friday again... Andre' -- André Pönitz . [EMAIL PROTECTED]
Re: Rename 666 to TEX
Andre Poenitz wrote: > > > Let's just keep it as it is now: "ERT" Encapsulated Raw Text > > Okokok... I thought you are the math guru, why don't you write $ok^3\ldot$ i see, the problem is the first uppercase letter ... Herbert :-) -- http://www.educat.hu-berlin.de/~voss/lyx/
Re: Rename 666 to TEX
Jose Abilio Oliveira Matos wrote:
>
> On Fri, Aug 03, 2001 at 11:36:10AM +0200, Herbert Voss wrote:
> > Andre Poenitz wrote:
> > >
> > > > Let's just keep it as it is now: "ERT" Encapsulated Raw Text
> > >
> > > Okokok...
> >
> > I thought you are the math guru, why don't you write
> >
> > $ok^3\ldot$
>
> I'm not defending André, after all he doesn't need it, but even so I
> should point some incoherence in your post Herbert...
>
> > i see, the problem is the first uppercase letter ...
> >
> > Herbert :-)
> """
> So you are using those punny icons in a Friday, and I thought that you
oh sorry, but I have 45 holidays, 29 in front of me ...
so I don't know what day of weekend is, because it's
absolutely not important for me
$ \stackrel{.\, .}{\stackrel{|}{\smile }} $
well done!
> BTW using docbook/xml I would write just before you ask
or \smiley with package wasysym and
\Huge\smiley is just the same size than yours.
nice weekend
Herbert
--
http://www.educat.hu-berlin.de/~voss/lyx/
Re: Rename 666 to TEX
On 29-Jul-2001 Garst R. Reese wrote: TeX is better, because it's no more like the eval red text. It goes away anyway. I like the 666, maybe the same people trying to ban Harry Potter will give lyx some publicity also :) Oh you have the same problems there, people seeing Harry Potter as a really evil book ;), I discovered recently that in some villages it was banned from the public library because of (some) parents complains! Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Never reveal your best argument.
Re: Rename 666 to TEX
On Mon, Jul 30, 2001 at 03:41:35PM +1000, Allan Rae wrote: On Sun, 29 Jul 2001, Kayvan A. Sylvan wrote: The TeX inset on the other hand, is clear and intuitive. In a DocBook document TeX won't make much sense. Whoa. Never thought of that. In my mind, the LyX backend is always LaTeX. On the other hand Raw may make more sense when used in both LaTeX and DocBook documents. Probably a good description. You could also just call it a Markup inset since LaTeX and DocBook are markup languages. To me, though, markup seems like it's even more marked up than LyX, not more raw. I'd go with raw. -Amir
Re: Rename 666 to TEX
On Mon, Jul 30, 2001 at 03:27:06PM +0200, Lars Gullik Bjønnes wrote: Amir Karger [EMAIL PROTECTED] writes: | To me, though, markup seems like it's even more marked up than LyX, not more | raw. I'd go with raw. I still think '666' gives the right assosiations. Only to those people who know all the various in-jokes and references. (but I won't argue is was a Bolzano change...) If you're not arguing, then let's change the name to the Raw inset. -- 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)
Re: Rename 666 to TEX
| Only to those people who know all the various in-jokes and references. eh? '666'? what do _you_ think/assosiate when you see 666? Actually, knowledge about the deeper meaning of '666' seems not to be too widespread among all the supporters of a few 'other' religions and the atheist... I had to explain '666' more than once and I do think 'Raw' is a much better name of that beast. Andre' -- André Pönitz . [EMAIL PROTECTED]
Re: Rename 666 to TEX
| I had to explain '666' more than once and I do think 'Raw' is a much better | name of that beast. pun intended? Sure... puns are not frowned upon hereabout... Why not just rename the inset label to The Beast For exactly the same raeson. _I_ would not know what 'The Beast' is in connection with LyX. I guess some time ago I'd have expected the LyX mascot in the inset... Andre' -- André Pönitz . [EMAIL PROTECTED]
Re: Rename 666 to TEX
On Mon, Jul 30, 2001 at 04:31:28PM +0200, Lars Gullik Bjønnes wrote: | I had to explain '666' more than once and I do think 'Raw' is a much better | name of that beast. pun intended? Why not just rename the inset label to The Beast the wickedest inset in the world john -- I'd rather be rudely informed than politely left in the dark.
Re: Rename 666 to TEX
Mike Ressler wrote: On 30 Jul 2001, Jean-Marc Lasgouttes wrote: Lars == Lars Gullik Bjønnes [EMAIL PROTECTED] writes: Lars Or just change the ERT acronym to be something else. Eloquent Lars Red Text, Encumbering Red Text, Extension Red Text... Encapsulated Raw Text? :-) A most excellent example of coming up with the full title after the acronym was chosen! (Standard operating procedure at NASA ...) Mike My favourite was Destination: IRAN - Destination: Inspect and Replace As Necessary Garst
Re: Rename 666 to TEX
Garst R. Reese wrote: Mike Ressler wrote: On 30 Jul 2001, Jean-Marc Lasgouttes wrote: Lars == Lars Gullik Bjønnes [EMAIL PROTECTED] writes: Lars Or just change the ERT acronym to be something else. Eloquent Lars Red Text, Encumbering Red Text, Extension Red Text... Encapsulated Raw Text? :-) A most excellent example of coming up with the full title after the acronym was chosen! (Standard operating procedure at NASA ...) Mike My favourite was Destination: IRAN - Destination: Inspect and Replace As Necessary ert seems to be the biggest problem which lyx ever had ... ;-) Herbert -- http://www.educat.hu-berlin.de/~voss/lyx/
Re: Rename 666 to TEX
* Andre Poenitz [EMAIL PROTECTED] [2001-07-30 16:26] schrieb: | Only to those people who know all the various in-jokes and references. eh? '666'? what do _you_ think/assosiate when you see 666? i only think hä, was is los? or for non germans what? what's going on here? (hoping htat not only kayvan had the right to answer ;) Actually, knowledge about the deeper meaning of '666' seems not to be too widespread among all the supporters of a few 'other' religions and the atheist... I had to explain '666' more than once and I do think 'Raw' is a much better name of that beast. can you explain it once more? either i have missed it or it was never explained in the list (and i dont read harry potter and won't do in near future, it seems to be related) Andre' -- thanks ronny
Re: Rename 666 to TEX
Amazingly it seems like we have reached a kind of consensus that ERT is better than 666, and this within two days! What the fuck? I had expected this thread to continue for weeks!?! Normally trivial details take forever to settle because everybody has an opinion. Hmm. I have to practice that mind reading business some more. Now, who would have the honors of making this Very Important Change that will surely mark a completely new era of the Beast called LyX? You have until Wednesday if you want to forego I. Greets, Asger
Re: Rename 666 to TEX
On Mon, Jul 30, 2001 at 11:36:49PM +0200, Asger K. Alstrup Nielsen wrote: Amazingly it seems like we have reached a kind of consensus that ERT is better than 666, and this within two days! What the fuck? I had expected this thread to continue for weeks!?! Normally trivial details take forever to settle because everybody has an opinion. Hmm. I have to practice that mind reading business some more. I think it was the brain-fart from Lars(?) who proposed re-defining the ERT acronym to mean Embedded Raw Text. Now, who would have the honors of making this Very Important Change that will surely mark a completely new era of the Beast called LyX? *laugh* -- 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)
Re: Rename 666 to TEX
On 29-Jul-2001 Garst R. Reese wrote: >> TeX is better, because it's no more like the eval red text. > It goes away anyway. I like the 666, maybe the same people trying to ban > Harry Potter will give lyx some publicity also :) Oh you have the same problems there, people seeing "Harry Potter" as a really evil book ;), I discovered recently that in some villages it was banned from the public library because of (some) parents complains! Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Never reveal your best argument.
Re: Rename 666 to TEX
On Mon, Jul 30, 2001 at 03:41:35PM +1000, Allan Rae wrote: > On Sun, 29 Jul 2001, Kayvan A. Sylvan wrote: > > > The "TeX inset" on the other hand, is clear and intuitive. > > In a DocBook document "TeX" won't make much sense. Whoa. Never thought of that. In my mind, the LyX backend is always LaTeX. > On the other hand "Raw" may make more sense when used in both LaTeX and > DocBook documents. Probably a good description. > You could also just call it a "Markup" inset since > LaTeX and DocBook are markup languages. To me, though, markup seems like it's even more marked up than LyX, not more raw. I'd go with raw. -Amir
Re: Rename 666 to TEX
On Mon, Jul 30, 2001 at 03:27:06PM +0200, Lars Gullik Bjønnes wrote: > Amir Karger <[EMAIL PROTECTED]> writes: > > | To me, though, markup seems like it's even more marked up than LyX, not more > | raw. I'd go with raw. > > I still think '666' gives the right assosiations. Only to those people who know all the various in-jokes and references. > (but I won't argue is was a Bolzano change...) If you're not arguing, then let's change the name to the Raw inset. -- 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)
Re: Rename 666 to TEX
> | Only to those people who know all the various in-jokes and references. > > eh? '666'? > > what do _you_ think/assosiate when you see "666"? Actually, knowledge about the deeper meaning of '666' seems not to be too widespread among all the supporters of a few 'other' religions and the atheist... I had to explain '666' more than once and I do think 'Raw' is a much better name of that beast. Andre' -- André Pönitz . [EMAIL PROTECTED]
Re: Rename 666 to TEX
> | I had to explain '666' more than once and I do think 'Raw' is a much better > | name of that beast. > > pun intended? Sure... puns are not frowned upon hereabout... > Why not just rename the inset label to "The Beast" For exactly the same raeson. _I_ would not know what 'The Beast' is in connection with LyX. I guess some time ago I'd have expected the LyX mascot in the inset... Andre' -- André Pönitz . [EMAIL PROTECTED]
Re: Rename 666 to TEX
On Mon, Jul 30, 2001 at 04:31:28PM +0200, Lars Gullik Bjønnes wrote: > | I had to explain '666' more than once and I do think 'Raw' is a much better > | name of that beast. > > pun intended? > > Why not just rename the inset label to "The Beast" "the wickedest inset in the world" john -- "I'd rather be rudely informed than politely left in the dark."
Re: Rename 666 to TEX
Mike Ressler wrote: > > On 30 Jul 2001, Jean-Marc Lasgouttes wrote: > > > > "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes: > > > > Lars> Or just change the "ERT" acronym to be something else. Eloquent > > Lars> Red Text, Encumbering Red Text, Extension Red Text... > > > > Encapsulated Raw Text? > > :-) A most excellent example of coming up with the full title after the > acronym was chosen! (Standard operating procedure at NASA ...) > > Mike My favourite was "Destination: IRAN" -> "Destination: Inspect and Replace As Necessary" Garst
Re: Rename 666 to TEX
"Garst R. Reese" wrote: > > Mike Ressler wrote: > > > > On 30 Jul 2001, Jean-Marc Lasgouttes wrote: > > > > > > "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes: > > > > > > Lars> Or just change the "ERT" acronym to be something else. Eloquent > > > Lars> Red Text, Encumbering Red Text, Extension Red Text... > > > > > > Encapsulated Raw Text? > > > > :-) A most excellent example of coming up with the full title after the > > acronym was chosen! (Standard operating procedure at NASA ...) > > > > Mike > My favourite was "Destination: IRAN" -> "Destination: Inspect and > Replace As Necessary" "ert" seems to be the biggest problem which lyx ever had ... ;-) Herbert -- http://www.educat.hu-berlin.de/~voss/lyx/
Re: Rename 666 to TEX
* Andre Poenitz <[EMAIL PROTECTED]> [2001-07-30 16:26] schrieb: > > | Only to those people who know all the various in-jokes and references. > > > > eh? '666'? > > > > what do _you_ think/assosiate when you see "666"? > i only think "hä, was is los?" or for non germans "what? what's going on here?" (hoping htat not only kayvan had the right to answer ;) > Actually, knowledge about the deeper meaning of '666' seems not to be too > widespread among all the supporters of a few 'other' religions and the > atheist... > > I had to explain '666' more than once and I do think 'Raw' is a much better > name of that beast. can you explain it once more? either i have missed it or it was never explained in the list (and i dont read harry potter and won't do in near future, it seems to be related) > > Andre' > -- thanks ronny
Re: Rename 666 to TEX
Amazingly it seems like we have reached a kind of consensus that ERT is better than 666, and this within two days! What the fuck? I had expected this thread to continue for weeks!?! Normally trivial details take forever to settle because everybody has an opinion. Hmm. I have to practice that mind reading business some more. Now, who would have the honors of making this Very Important Change that will surely mark a completely new era of the Beast called LyX? You have until Wednesday if you want to forego I. Greets, Asger
Re: Rename 666 to TEX
On Mon, Jul 30, 2001 at 11:36:49PM +0200, Asger K. Alstrup Nielsen wrote: > Amazingly it seems like we have reached a kind of consensus that ERT is > better than 666, and this within two days! What the fuck? I had expected this > thread to continue for weeks!?! Normally trivial details take forever to > settle because everybody has an opinion. Hmm. I have to practice that mind > reading business some more. I think it was the brain-fart from Lars(?) who proposed re-defining the ERT acronym to mean Embedded Raw Text. > Now, who would have the honors of making this Very Important Change that > will surely mark a completely new era of the Beast called LyX? *laugh* -- 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)
Re: Rename 666 to TEX
On Sun, Jul 29, 2001 at 02:32:00PM +0200, Asger K. Alstrup Nielsen wrote: Hi, The 666 name is fun, but not very intuitive/informative. What about changing it to TEX? Failing that, we should at least use ERT, which is not very intuitive either, but at least more established? Greets, Asger I totally agree. -- 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)
Re: Rename 666 to TEX
Asger K. Alstrup Nielsen wrote: The 666 name is fun, but not very intuitive/informative. What about changing it to TEX? Failing that, we should at least use ERT, which is not very intuitive either, but at least more established? TeX is better, because it's no more like the eval red text. HErbert -- http://www.educat.hu-berlin.de/~voss/lyx/
Re: Rename 666 to TEX
Herbert Voss wrote: Asger K. Alstrup Nielsen wrote: The 666 name is fun, but not very intuitive/informative. What about changing it to TEX? Failing that, we should at least use ERT, which is not very intuitive either, but at least more established? TeX is better, because it's no more like the eval red text. It goes away anyway. I like the 666, maybe the same people trying to ban Harry Potter will give lyx some publicity also :) Garst
Re: Rename 666 to TEX
On Sun, Jul 29, 2001 at 10:23:53AM -0300, Garst R. Reese wrote: Herbert Voss wrote: Asger K. Alstrup Nielsen wrote: The 666 name is fun, but not very intuitive/informative. What about changing it to TEX? Failing that, we should at least use ERT, which is not very intuitive either, but at least more established? TeX is better, because it's no more like the eval red text. It goes away anyway. I like the 666, maybe the same people trying to ban Harry Potter will give lyx some publicity also :) Funny, but Im going to have to agree with the others. If someone does happen to see an open 666 inset, this'll give them a clue as to what it does. -Amir
Re: Rename 666 to TEX
On Sun, Jul 29, 2001 at 08:14:41PM -0400, Amir Karger wrote: On Sun, Jul 29, 2001 at 10:23:53AM -0300, Garst R. Reese wrote: Herbert Voss wrote: Asger K. Alstrup Nielsen wrote: The 666 name is fun, but not very intuitive/informative. What about changing it to TEX? Failing that, we should at least use ERT, which is not very intuitive either, but at least more established? TeX is better, because it's no more like the eval red text. It goes away anyway. I like the 666, maybe the same people trying to ban Harry Potter will give lyx some publicity also :) Funny, but Im going to have to agree with the others. If someone does happen to see an open 666 inset, this'll give them a clue as to what it does. Yes, the name of program features should be primarily influenced by clarity and intuitiveness. Whie 666 inset is clever and it makes sense within the sub-culture of people who know that ERT means Evil Red Text which is a reference to TeX mode, it fails on both clarity and intuitiveness. Too many in-jokes and obscure references. The TeX inset on the other hand, is clear and intuitive. -- 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)
Re: Rename 666 to TEX
On Sun, 29 Jul 2001, Kayvan A. Sylvan wrote: On Sun, Jul 29, 2001 at 08:14:41PM -0400, Amir Karger wrote: On Sun, Jul 29, 2001 at 10:23:53AM -0300, Garst R. Reese wrote: Herbert Voss wrote: Asger K. Alstrup Nielsen wrote: The 666 name is fun, but not very intuitive/informative. What about changing it to TEX? Failing that, we should at least use ERT, which is not very intuitive either, but at least more established? TeX is better, because it's no more like the eval red text. It goes away anyway. I like the 666, maybe the same people trying to ban Harry Potter will give lyx some publicity also :) Interesting publicity opportunity... Funny, but Im going to have to agree with the others. If someone does happen to see an open 666 inset, this'll give them a clue as to what it does. Yes, the name of program features should be primarily influenced by clarity and intuitiveness. Whie 666 inset is clever and it makes sense within the sub-culture of people who know that ERT means Evil Red Text which is a reference to TeX mode, it fails on both clarity and intuitiveness. Too many in-jokes and obscure references. The TeX inset on the other hand, is clear and intuitive. In a DocBook document TeX won't make much sense. On the other hand Raw may make more sense when used in both LaTeX and DocBook documents. You could also just call it a Markup inset since LaTeX and DocBook are markup languages. Allan. (ARRae)
Re: Rename 666 to TEX
On Sun, Jul 29, 2001 at 02:32:00PM +0200, Asger K. Alstrup Nielsen wrote: > Hi, > > The 666 name is fun, but not very intuitive/informative. What about > changing it to TEX? Failing that, we should at least use ERT, which > is not very intuitive either, but at least more established? > > Greets, > > Asger I totally agree. -- 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)
Re: Rename 666 to TEX
"Asger K. Alstrup Nielsen" wrote: > > The 666 name is fun, but not very intuitive/informative. What about > changing it to TEX? Failing that, we should at least use ERT, which > is not very intuitive either, but at least more established? TeX is better, because it's no more like the eval red text. HErbert -- http://www.educat.hu-berlin.de/~voss/lyx/
Re: Rename 666 to TEX
Herbert Voss wrote: > > "Asger K. Alstrup Nielsen" wrote: > > > > The 666 name is fun, but not very intuitive/informative. What about > > changing it to TEX? Failing that, we should at least use ERT, which > > is not very intuitive either, but at least more established? > > TeX is better, because it's no more like the eval red text. It goes away anyway. I like the 666, maybe the same people trying to ban Harry Potter will give lyx some publicity also :) Garst
Re: Rename 666 to TEX
On Sun, Jul 29, 2001 at 10:23:53AM -0300, Garst R. Reese wrote: > Herbert Voss wrote: > > > > "Asger K. Alstrup Nielsen" wrote: > > > > > > The 666 name is fun, but not very intuitive/informative. What about > > > changing it to TEX? Failing that, we should at least use ERT, which > > > is not very intuitive either, but at least more established? > > > > TeX is better, because it's no more like the eval red text. > It goes away anyway. I like the 666, maybe the same people trying to ban > Harry Potter will give lyx some publicity also :) Funny, but I"m going to have to agree with the others. If someone does happen to see an open 666 inset, this'll give them a clue as to what it does. -Amir
Re: Rename 666 to TEX
On Sun, Jul 29, 2001 at 08:14:41PM -0400, Amir Karger wrote: > On Sun, Jul 29, 2001 at 10:23:53AM -0300, Garst R. Reese wrote: > > Herbert Voss wrote: > > > > > > "Asger K. Alstrup Nielsen" wrote: > > > > > > > > The 666 name is fun, but not very intuitive/informative. What about > > > > changing it to TEX? Failing that, we should at least use ERT, which > > > > is not very intuitive either, but at least more established? > > > > > > TeX is better, because it's no more like the eval red text. > > It goes away anyway. I like the 666, maybe the same people trying to ban > > Harry Potter will give lyx some publicity also :) > > Funny, but I"m going to have to agree with the others. If someone does > happen to see an open 666 inset, this'll give them a clue as to what it > does. Yes, the name of program features should be primarily influenced by clarity and intuitiveness. Whie "666 inset" is clever and it makes sense within the sub-culture of people who know that ERT means Evil Red Text which is a reference to TeX mode, it fails on both clarity and intuitiveness. Too many in-jokes and obscure references. The "TeX inset" on the other hand, is clear and intuitive. -- 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)
Re: Rename 666 to TEX
On Sun, 29 Jul 2001, Kayvan A. Sylvan wrote: > On Sun, Jul 29, 2001 at 08:14:41PM -0400, Amir Karger wrote: > > On Sun, Jul 29, 2001 at 10:23:53AM -0300, Garst R. Reese wrote: > > > Herbert Voss wrote: > > > > > > > > "Asger K. Alstrup Nielsen" wrote: > > > > > > > > > > The 666 name is fun, but not very intuitive/informative. What about > > > > > changing it to TEX? Failing that, we should at least use ERT, which > > > > > is not very intuitive either, but at least more established? > > > > > > > > TeX is better, because it's no more like the eval red text. > > > It goes away anyway. I like the 666, maybe the same people trying to ban > > > Harry Potter will give lyx some publicity also :) Interesting publicity opportunity... > > Funny, but I"m going to have to agree with the others. If someone does > > happen to see an open 666 inset, this'll give them a clue as to what it > > does. > > Yes, the name of program features should be primarily influenced by > clarity and intuitiveness. > > Whie "666 inset" is clever and it makes sense within the sub-culture of > people who know that ERT means Evil Red Text which is a reference to TeX > mode, it fails on both clarity and intuitiveness. Too many in-jokes > and obscure references. > > The "TeX inset" on the other hand, is clear and intuitive. In a DocBook document "TeX" won't make much sense. On the other hand "Raw" may make more sense when used in both LaTeX and DocBook documents. You could also just call it a "Markup" inset since LaTeX and DocBook are markup languages. Allan. (ARRae)
Re: 666 inset vs. Latex Layout
On 24-Jul-2001 Lars Gullik Bjønnes wrote: | 4) Lars does not like adding the Latex layout back in because there |would be two different ways of adding Latex. I'm still of the opinion that this is a artifical excuse. | * Add the Latex layout back in via the PassThru flag in a small file | (lib/layouts/latex-layout.inc). I'm really in PRO to do such a thing, but only with the ERT inset! We SHOULD also think on our power-users (as you called them) and not only on stupid users who use it as is without the knowledge what's behind (no offens of stupid is was just an other word for not knowing) Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Pardo's First Postulate: Anything good in life is either illegal, immoral, or fattening. Arnold's Addendum: Everything else causes cancer in rats.
Re: 666 inset vs. Latex Layout
On Wed, Jul 25, 2001 at 09:44:47AM +0200, Juergen Vigna wrote: On 24-Jul-2001 Lars Gullik Bjønnes wrote: | 4) Lars does not like adding the Latex layout back in because there |would be two different ways of adding Latex. I'm still of the opinion that this is a artifical excuse. Me too. | * Add the Latex layout back in via the PassThru flag in a small file | (lib/layouts/latex-layout.inc). I'm really in PRO to do such a thing, but only with the ERT inset! We SHOULD also think on our power-users (as you called them) and not only on stupid users who use it as is without the knowledge what's behind (no offens of stupid is was just an other word for not knowing) I think having the Latex Layout in addition to the ERT inset is actually the best of both worlds. The preferred method can become the ERT inset (which IS looking better and better!!! Thanks, everyone!) but there is no reason to chop off the LaTeX layout since now it can be done without too many hacks, hacks, hacks. So, I modify what I proposed before: 1) Leave the ERT inset code and improve it. 2) Leave the bindings as they are (ERT inset added when TeX button is pressed, etc.) 3) Add the LaTeX layout back in. 4) Remove the conversion code that takes a LaTeX layout paragraph and transforms it into an ERT inset. A user who really wants an ERT inset instead of a LaTeX paragraph should be able to copy and paste the paragraph into an ERT inset. ---Kayvan -- 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)
Re: 666 inset vs. Latex Layout
On 24-Jul-2001 Lars Gullik Bjønnes wrote: >| 4) Lars does not like adding the Latex layout back in because there >|would be two different ways of adding Latex. I'm still of the opinion that this is a "artifical" excuse. >| * Add the Latex layout back in via the PassThru flag in a small file >| (lib/layouts/latex-layout.inc). I'm really in PRO to do such a thing, but only with the ERT inset! We SHOULD also think on our power-users (as you called them) and not only on "stupid" users who use it as is without the knowledge what's behind (no offens of stupid is was just an other word for "not knowing") Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Pardo's First Postulate: Anything good in life is either illegal, immoral, or fattening. Arnold's Addendum: Everything else causes cancer in rats.
Re: 666 inset vs. Latex Layout
On Wed, Jul 25, 2001 at 09:44:47AM +0200, Juergen Vigna wrote: > > On 24-Jul-2001 Lars Gullik Bjønnes wrote: > > >| 4) Lars does not like adding the Latex layout back in because there > >|would be two different ways of adding Latex. > > I'm still of the opinion that this is a "artifical" excuse. Me too. > >| * Add the Latex layout back in via the PassThru flag in a small file > >| (lib/layouts/latex-layout.inc). > > I'm really in PRO to do such a thing, but only with the ERT inset! > We SHOULD also think on our power-users (as you called them) and not > only on "stupid" users who use it as is without the knowledge what's > behind (no offens of stupid is was just an other word for "not knowing") I think having the Latex Layout in addition to the ERT inset is actually the best of both worlds. The "preferred" method can become the ERT inset (which IS looking better and better!!! Thanks, everyone!) but there is no reason to chop off the LaTeX layout since now it can be done without too many "hacks, hacks, hacks". So, I modify what I proposed before: 1) Leave the ERT inset code and improve it. 2) Leave the bindings as they are (ERT inset added when TeX button is pressed, etc.) 3) Add the LaTeX layout back in. 4) Remove the conversion code that takes a LaTeX layout paragraph and transforms it into an ERT inset. A user who really wants an ERT inset instead of a LaTeX paragraph should be able to copy and paste the paragraph into an ERT inset. ---Kayvan -- 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)
Re: 666 insets looking much better
Mike Ressler [EMAIL PROTECTED] writes: I've just compiled the current CVS and like the 666 inset behavior much better - collapsing them looks good. However, could the maximum size of the box be made settable somewhere? From my previous example, \micron shows up very nicely, as does \farcs; both these have a box size which matches their length (very nice!). However, \citep(dantona) shows up as \citep(dan (Yes, I know I can now fix this with natbib, which is in fact what I was doing.) 15 characters doesn't seem to be overlong to me, so I was wondering if a settable length could be placed somewhere, perhaps in Edit-Preferences-Look Feel-Misc? Anyway, nice job! I'll stop having a cow now ... Well we could, but I really don't know if this is needed. I made this more for longer paragraphs with LaTeX code as for shorter one I'll make the inlined version so that it doesn't collapse, but it will show it's contents always, but WITHOUT breaking row! So this is really ONLY thought for really short LaTeX constructs. On 24-Jul-2001 Lars Gullik Bjønnes wrote: We could also make it end with ... if longer than the requested length. Did you have a look at the label he showed you? - \citep(dan... Anyway good idea #:O) Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Two is not equal to three, even for large values of two.
666 inset vs. Latex Layout
On Tue, Jul 24, 2001 at 05:08:26PM +0200, Juergen Vigna wrote: On 23-Jul-2001 Kayvan A. Sylvan wrote: Try this with lyx/.../examples/noweb2lyx.lyx and see. I did and fixed. Please have a look again! Jürgen I will do it as soon as it shows up in anon CVS. However, I do have an observation about the ERT-insets versus Latex paragraph layouts: 1) The ERT inset was supposed to fix and simplify the code. It added no new functionality (unless you count their collapsability). 2) The Literate dependency forced me to generalize the Scrap layout, adding the PassThru flag. 3) It is now possible to do a Latex layout that is backwards compatible with all old documents by simply using the PassThru flag in the appropriate layout file. 4) Lars does not like adding the Latex layout back in because there would be two different ways of adding Latex. So, I propose: * Add the Latex layout back in via the PassThru flag in a small file (lib/layouts/latex-layout.inc). * Remove the ERT inset and all the backwards compatibility loading and writing stuff. This further cleans up the code, completely preserves backwards compatibility, gets rid of the entire problems with the inset rendering, and makes all the power users (like Herbert and others) happy. You could also then do similar things with the DocBook stuff using the PassThru flag. ---Kayvan -- 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)
Re: 666 inset vs. Latex Layout
On Tue, Jul 24, 2001 at 05:58:49PM +0200, Lars Gullik Bjønnes wrote: | * Add the Latex layout back in via the PassThru flag in a small file | (lib/layouts/latex-layout.inc). | | * Remove the ERT inset and all the backwards compatibility loading and | writing stuff. | | This further cleans up the code, completely preserves backwards compatibility, | gets rid of the entire problems with the inset rendering, and makes all the | power users (like Herbert and others) happy. | | You could also then do similar things with the DocBook stuff using | the PassThru flag. and you get the latex font style back... not good. Hmmm... What was so bad about the Latex font style? It was an easy way to have in-lined LaTeX code. -- 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)
Re: 666 insets looking much better
On Tue, 24 Jul 2001, Juergen Vigna wrote: Well we could, but I really don't know if this is needed. I made this more for longer paragraphs with LaTeX code as for shorter one I'll make the inlined version so that it doesn't collapse, but it will show it's contents ^^^ Ah, yes ... if there will be a new inlined version, then I withdraw my proposal. Thanks! Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Re: 666 insets looking much better
> Mike Ressler <[EMAIL PROTECTED]> writes: > > I've just compiled the current CVS and like the "666 inset" behavior much > better - collapsing them looks good. However, could the maximum size of > the box be made settable somewhere? From my previous example, "\micron" > shows up very nicely, as does "\farcs"; both these have a box size which > matches their length (very nice!). However, "\citep(dantona)" shows up as > "\citep(dan...". (Yes, I know I can now fix this with natbib, which is in > fact what I was doing.) 15 characters doesn't seem to be overlong to me, > so I was wondering if a settable length could be placed somewhere, perhaps > in Edit->Preferences->Look & Feel->Misc? Anyway, nice job! I'll stop > having a cow now ... Well we could, but I really don't know if this is needed. I made this more for longer paragraphs with LaTeX code as for shorter one I'll make the inlined version so that it doesn't collapse, but it will show it's contents always, but WITHOUT breaking row! So this is really ONLY thought for really short LaTeX constructs. On 24-Jul-2001 Lars Gullik Bjønnes wrote: > We could also make it end with "..." if longer than the requested > length. Did you have a look at the label he showed you? -> "\citep(dan..." Anyway good idea #:O) Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Two is not equal to three, even for large values of two.
666 inset vs. Latex Layout
On Tue, Jul 24, 2001 at 05:08:26PM +0200, Juergen Vigna wrote: > > On 23-Jul-2001 Kayvan A. Sylvan wrote: > > > Try this with "lyx/.../examples/noweb2lyx.lyx" and see. > > I did and fixed. Please have a look again! > >Jürgen I will do it as soon as it shows up in anon CVS. However, I do have an observation about the ERT-insets versus Latex paragraph layouts: 1) The ERT inset was supposed to fix and simplify the code. It added no new functionality (unless you count their collapsability). 2) The Literate dependency forced me to generalize the Scrap layout, adding the PassThru flag. 3) It is now possible to do a Latex layout that is backwards compatible with all old documents by simply using the PassThru flag in the appropriate layout file. 4) Lars does not like adding the Latex layout back in because there would be two different ways of adding Latex. So, I propose: * Add the Latex layout back in via the PassThru flag in a small file (lib/layouts/latex-layout.inc). * Remove the ERT inset and all the backwards compatibility loading and writing stuff. This further cleans up the code, completely preserves backwards compatibility, gets rid of the entire problems with the inset rendering, and makes all the power users (like Herbert and others) happy. You could also then do similar things with the DocBook stuff using the PassThru flag. ---Kayvan -- 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)
Re: 666 inset vs. Latex Layout
On Tue, Jul 24, 2001 at 05:58:49PM +0200, Lars Gullik Bjønnes wrote: > | * Add the Latex layout back in via the PassThru flag in a small file > | (lib/layouts/latex-layout.inc). > | > | * Remove the ERT inset and all the backwards compatibility loading and > | writing stuff. > | > | This further cleans up the code, completely preserves backwards compatibility, > | gets rid of the entire problems with the inset rendering, and makes all the > | power users (like Herbert and others) happy. > | > | You could also then do similar things with the DocBook stuff using > | the PassThru flag. > > and you get the latex font style back... not good. Hmmm... What was so bad about the Latex font style? It was an easy way to have in-lined LaTeX code. -- 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)
Re: 666 insets looking much better
On Tue, 24 Jul 2001, Juergen Vigna wrote: > Well we could, but I really don't know if this is needed. I made this more > for longer paragraphs with LaTeX code as for shorter one I'll make the > inlined version so that it doesn't collapse, but it will show it's contents ^^^ Ah, yes ... if there will be a new inlined version, then I withdraw my proposal. Thanks! Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
666 insets looking much better
I've just compiled the current CVS and like the 666 inset behavior much better - collapsing them looks good. However, could the maximum size of the box be made settable somewhere? From my previous example, \micron shows up very nicely, as does \farcs; both these have a box size which matches their length (very nice!). However, \citep(dantona) shows up as \citep(dan (Yes, I know I can now fix this with natbib, which is in fact what I was doing.) 15 characters doesn't seem to be overlong to me, so I was wondering if a settable length could be placed somewhere, perhaps in Edit-Preferences-Look Feel-Misc? Anyway, nice job! I'll stop having a cow now ... Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
666 insets looking much better
I've just compiled the current CVS and like the "666 inset" behavior much better - collapsing them looks good. However, could the maximum size of the box be made settable somewhere? From my previous example, "\micron" shows up very nicely, as does "\farcs"; both these have a box size which matches their length (very nice!). However, "\citep(dantona)" shows up as "\citep(dan...". (Yes, I know I can now fix this with natbib, which is in fact what I was doing.) 15 characters doesn't seem to be overlong to me, so I was wondering if a settable length could be placed somewhere, perhaps in Edit->Preferences->Look & Feel->Misc? Anyway, nice job! I'll stop having a cow now ... Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Re: Natbib announcement (and 666 inset gripes)
On 19-Jul-2001 Angus Leeming wrote: Well this is well known and as developer you should have looked at the buglist on SourceForge.net ;) I still think that this was a sly way to get help, but anyway I've played further. #:O) Well you won't believe it but I know since a long time the exact spot and code which is culpable for this. It is InsetTabular::resetPos()! It's just that something with that scrolling mechanism is wrong, but I don't have a good idea to fix it. So if someone has time to spare he can do some investigation and see what we can do there to fix the cycle. A fast fix would be to have a bool so that resetPos is not entered 2 times, but probably that wouldn't do the right scroll, but who knows :) Anyway I'll save the mail so that when I have time I can do this myself if noone beats me in it. I'm still working A LOT in making Find/Replace work correctly and I only have a really small bug to fix right now, but you know small bugs are hard to spot :). Anyway my local tree has in a lot of cleanups and IMO some of the bugs on SourceForge are gone now as I took the time to fix also other stuff I've seen when testing the Find/Replace stuff. One of them is the Cursor appearing outside the inset on some ocacions :) Jürgen -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Penn's aunts made great apple pies at low prices. No one else in town could compete with the pie rates of Penn's aunts.
Small 666 insets all over the place
In my literate documents, I sprinkle the following construct all over the place: [[variable]] This should be in ERT and it is noweb's way of doing an in-lined code construct that also plugs into its indexing features. Look at .../examples/noweb2lyx.lyx for an example. Before the ERT inset, I could scan-read my documents without trouble: In the following code, [[io_str_iterator]] is going to walk down Now, I see this: In the following code, [666] - | [[io_str_iterator]] - is going to walk down If I collapse the inset, I see this: In the following code, [666] is going to walk down I know there is work being done to fix this. My fantasy would be to be able to see these short constructs as the label (instead of 666) of the inset. That would make the most sense in my opinion. -- 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)
Re: Natbib announcement (and 666 inset gripes)
On 19-Jul-2001 Angus Leeming wrote: >> Well this is well known and as developer you should have looked at the > buglist >> on SourceForge.net ;) > > I still think that this was a sly way to get help, but anyway I've played > further. #:O) Well you won't believe it but I know since a long time the exact spot and code which is culpable for this. It is InsetTabular::resetPos()! It's just that something with that scrolling mechanism is wrong, but I don't have a good idea to fix it. So if someone has time to spare he can do some investigation and see what we can do there to fix the cycle. A fast fix would be to have a bool so that resetPos is not entered 2 times, but probably that wouldn't do the right scroll, but who knows :) Anyway I'll save the mail so that when I have time I can do this myself if noone beats me in it. I'm still working A LOT in making Find/Replace work correctly and I only have a really small bug to fix right now, but you know small bugs are hard to spot :). Anyway my local tree has in a lot of cleanups and IMO some of the bugs on SourceForge are gone now as I took the time to fix also other stuff I've seen when testing the Find/Replace stuff. One of them is the Cursor appearing outside the inset on some ocacions :) Jürgen -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Penn's aunts made great apple pies at low prices. No one else in town could compete with the pie rates of Penn's aunts.
Small 666 insets all over the place
In my literate documents, I sprinkle the following construct all over the place: [[variable]] This should be in ERT and it is noweb's way of doing an in-lined code construct that also plugs into its indexing features. Look at .../examples/noweb2lyx.lyx for an example. Before the ERT inset, I could scan-read my documents without trouble: In the following code, [[io_str_iterator]] is going to walk down Now, I see this: In the following code, [666] - | [[io_str_iterator]] - is going to walk down If I collapse the inset, I see this: In the following code, [666] is going to walk down I know there is work being done to fix this. My fantasy would be to be able to see these short constructs as the label (instead of 666) of the inset. That would make the most sense in my opinion. -- 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)
Re: Natbib announcement (and 666 inset gripes)
On 18-Jul-2001 Mike Ressler wrote: This is not a stunning example of WYSIWYM. Please, please, (Lars?) change the appearance back to the old behavior!!! I don't think this will happen. What will happen is that we will change the InsetERT to be inlined. What will NOT happen is that a inlined ERT inset breaks row, so this is really thought only for short stuff! Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Might as well be frank, monsieur. It would take a miracle to get you out of Casablanca and the Germans have outlawed miracles. -- Casablanca
Re: Natbib announcement (and 666 inset gripes)
On Thu, 19 Jul 2001, Juergen Vigna wrote: On 18-Jul-2001 Mike Ressler wrote: This is not a stunning example of WYSIWYM. Please, please, (Lars?) change the appearance back to the old behavior!!! I don't think this will happen. What will happen is that we will change the InsetERT to be inlined. What will NOT happen is that a inlined ERT inset breaks row, so this is really thought only for short stuff! I don't care what the underlying mechanism is (insets, fonts, etc.). I would like the _appearance_ to resemble the old style. Having it appear like a math inset would be fine. Maybe that is the model: an inlined ERT box and a display ERT box, for longer chunks of LaTeX code. Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Re: Natbib announcement (and 666 inset gripes)
On Thu, 19 Jul 2001, Juergen Vigna wrote: On 19-Jul-2001 Mike Ressler wrote: like a math inset would be fine. Maybe that is the model: an inlined ERT box and a display ERT box, for longer chunks of LaTeX code. That's exactly what we plan to do :) Excellent! Why didn't you just say so :-) Sorry if I sounded overly loud - I was just shocked by the appearance of those 666 boxes, and hadn't really followed the previous discussion closely enough to realize what was going on. Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Re: Natbib announcement (and 666 inset gripes)
On Thu, Jul 19, 2001 at 09:21:51AM +0200, Juergen Vigna wrote: On 18-Jul-2001 Mike Ressler wrote: This is not a stunning example of WYSIWYM. Please, please, (Lars?) change the appearance back to the old behavior!!! I don't think this will happen. What will happen is that we will change the InsetERT to be inlined. What will NOT happen is that a inlined ERT inset breaks row, so this is really thought only for short stuff! can't you un-inline the ert inset automagically when it extends beyond the right margin of the workarea ? john -- Voodoo Programming: Things programmers do that they know shouldn't work but they try anyway, and which sometimes actually work, such as recompiling everything. - Karl Lehenbauer
Re: Natbib announcement (and 666 inset gripes)
On 19-Jul-2001 John Levon wrote: can't you un-inline the ert inset automagically when it extends beyond the right margin of the workarea ? Probably yes, but do I want to do this? Probably no, as then I would get complaints about this automatic behaviour someone surely doesn't like! Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Life sucks, but death doesn't put out at all. -- Thomas J. Kopp
Re: Natbib announcement (and 666 inset gripes)
On Thu, Jul 19, 2001 at 05:08:12PM +0200, Juergen Vigna wrote: On 19-Jul-2001 John Levon wrote: can't you un-inline the ert inset automagically when it extends beyond the right margin of the workarea ? Probably yes, but do I want to do this? Probably no, as then I would get complaints about this automatic behaviour someone surely doesn't like! Think about the alternative - I add a lot of ert into the inset, so it is drawn off the side, and I can't even read it ! Surely we dont really have/want a choice in this circumstance. john -- Voodoo Programming: Things programmers do that they know shouldn't work but they try anyway, and which sometimes actually work, such as recompiling everything. - Karl Lehenbauer
Re: Natbib announcement (and 666 inset gripes)
On Thursday 19 July 2001 16:08, Juergen Vigna wrote: On 19-Jul-2001 John Levon wrote: can't you un-inline the ert inset automagically when it extends beyond the right margin of the workarea ? Probably yes, but do I want to do this? Probably no, as then I would get complaints about this automatic behaviour someone surely doesn't like! Well it seems like a good suggestion to me because it only affects the users ability to see what's on LyX's screen. Who's going to complain loudly about LyX won't let me write text off the end of the screen when I want to? Anyway, that's the joy of being an open source developer: you can tell the user to get used to this behaviour I've implemented or change it yourself if you decide they're being a PITA. As I probably am. Enough, Angus
Re: Natbib announcement (and 666 inset gripes)
On 19-Jul-2001 Angus Leeming wrote: Probably yes, but do I want to do this? Probably no, as then I would get complaints about this automatic behaviour someone surely doesn't like! Well it seems like a good suggestion to me because it only affects the users The only change to the above I would admit is making it displayed as soon as it is Larger then the screen, all other cases have to have a user interaction. Anyway before we have to implement the inlined stuff then we can discuss about this :) Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Lots of folks are forced to skimp to support a government that won't.
Re: Natbib announcement (and 666 inset gripes)
On Thursday 19 July 2001 16:14, Juergen Vigna wrote: On 19-Jul-2001 John Levon wrote: Think about the alternative - I add a lot of ert into the inset, so it is drawn off the side, and I can't even read it ! Surely we dont really have/want a choice in this circumstance. Well we have already the inset will scroll to the right if the cursor exits to the left ;) (try this in a tabular cell where the InsetText IS inlined). Oh you bugger! I've just done this and now I'm getting infinite redraws of the table and can do nothing useful at all. Phew! LyX has just crashed on me. Road test to infinite redraws: 1. Insert table, I row, 2 columns 2. Type in first (leftmost) column until the table gets bigger than the width Bingo! Actually, If you leave this on screen doing its stuff then you'll crash LyX in malloc. Presumably it just runs out of memory therefore. Angus
Re: Natbib announcement (and 666 inset gripes)
On 19-Jul-2001 Angus Leeming wrote: Road test to infinite redraws: 1. Insert table, I row, 2 columns 2. Type in first (leftmost) column until the table gets bigger than the width Well this is well known and as developer you should have looked at the buglist on SourceForge.net ;) Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Your aim is high and to the right.
Re: Natbib announcement (and 666 inset gripes)
On Thu, Jul 19, 2001 at 05:50:43PM +0200, Juergen Vigna wrote: On 19-Jul-2001 Angus Leeming wrote: Road test to infinite redraws: 1. Insert table, I row, 2 columns 2. Type in first (leftmost) column until the table gets bigger than the width Well this is well known and as developer you should have looked at the buglist on SourceForge.net ;) actually it's changed behaviour recently - a 1x2 table didn't used to trigger it ... john -- Voodoo Programming: Things programmers do that they know shouldn't work but they try anyway, and which sometimes actually work, such as recompiling everything. - Karl Lehenbauer
Re: Natbib announcement (and 666 inset gripes)
On Thursday 19 July 2001 16:50, Juergen Vigna wrote: On 19-Jul-2001 Angus Leeming wrote: Road test to infinite redraws: 1. Insert table, I row, 2 columns 2. Type in first (leftmost) column until the table gets bigger than the width Well this is well known and as developer you should have looked at the buglist on SourceForge.net ;) I still think that this was a sly way to get help, but anyway I've played further. The infinite redraws are the result of a recursive cycling 18 updateLocal__C12InsetTabularXP10BufferView11UpdateCodesjb(0x28e, 0x0, 0x12034b334, 0x1401e4900, 0x1401814b0) [0x120348320] 19 resetPos__C12InsetTabularXP10BufferView(0x1401814b0, 0x1401e4938, 0x36, 0x1401e4968, 0x26a) [0x12034b330] 20 updateLocal__C12InsetTabularXP10BufferView11UpdateCodesjb(0x26a, 0x0, 0x12034b334, 0x1401e4900, 0x1401814b0) [0x120348320] 21 resetPos__C12InsetTabularXP10BufferView(0x1401814b0, 0x1401e4938, 0x1d, 0x1401e4968, 0x28e) [0x12034b330] 22 updateLocal__C12InsetTabularXP10BufferView11UpdateCodesjb(0x28e, 0x0, 0x12034b334, 0x1401e4900, 0x1401814b0) [0x120348320] Note that 18 and 22 are identical. As are 19 and 23 etc. So it's not just a simple oscillation between the two methods. Interestingly, if I create my table so that it reaches the width of the screen (just less) and then paste in some more text, then I CAN scroll. But doing so, I get a new problem. Effectively, I scroll off the end and into a segmentation fault. Backtrace below, but physically what happens is: Create a new document. Insert a table, 1row, 2cols Type e e e e e e in the first column until just before the table reaches screen width. Exit the table and on the line above type elephant elephant Cut this text, move the cursor around so only the line with the table on it exists. Paste the cut text into the leftmost column of the table so that the width is greater than the screen width. Scroll happily to the end of the first column (of two) with the right arrow key. Leave it and enter second column. Continue scrolling til we leave this column, continue scrolling (one more arrow press) to leave the table. The table is now redrawn with its left-most edge showing (fine), but the cursor is invisible. Pressing the arrow keys (some combination, any combo), to try and get the cursor visible again and eventually we get the segmentation fault and backtrace below. Angus signal Segmentation fault at *[GetCellNumber__C10LyXTabularXii, 0x1202aaa08] ldl r0, 0(r0) (dbx) where 0 GetCellNumber__C10LyXTabularXii(0x3ff801151ac, 0x, 0x12034ad68, 0x1401e2600, 0x397) [0x1202aaa08] 1 setPos__C12InsetTabularXP10BufferViewii(0x1401814b0, 0x397, 0xa, 0x0, 0x1400a80d8) [0x12034ad64] 2 edit__12InsetTabularXP10BufferViewiiUi(0x1201e83b8, 0x120348170, 0x1401e2600, 0x32, 0x1401814b0) [0x120348264] 3 Dispatch__Q110BufferView5PimplX9kb_actionRCQ13std60basic_string__TcQ13std15char_traits__TcQ13std13allocator__Tv(0x0, 0x0, 0x1201e56f0, 0x1400f6ed8, 0x1201dc100) [0x1201e83b4] 4 Dispatch__10BufferViewX9kb_actionRCQ13std60basic_string__TcQ13std15char_traits__TcQ13std13allocator__Tv(0x1201e56f0, 0x1400f6ed8, 0x1201dc100, 0x1400ac4c0, 0x120275bb0) [0x1201dc304] 5 dispatch__7LyXFuncXiRCQ13std60basic_string__TcQ13std15char_traits__TcQ13std13allocator__Tv(0x3ff801151ac, 0x1, 0x1ff51, 0x0, 0x1400f6e48) [0x120275bac] 6 processKeySym__7LyXFuncXUiUi(0x3ff801151ac, 0x1400a8000, 0x12042f700, 0x1400ac4c0, 0x120425108) [0x12027058c] 7 workAreaKeyPress__Q110BufferView5PimplXUiUi(0x12042f700, 0x1400ac4c0, 0x120425108, 0x140186658, 0x1201e02dc) [0x1201e288c] 8 (unknown)() [0x1201e02d8] 9 emit__Q14SigC38Signal2__Tv__TUiUiQ14SigC11Marshal__TvXRCUiRCUi(0x120219a30, 0x140186658, 0x61, 0x1400a5924, 0xcbff0c51) [0x120150a90] 10 work_area_handler__8WorkAreaXP7flobjs_Pv(0x540006f, 0xff51, 0xff51, 0xff51, 0x140186658) [0x120219a2c] 11 C_WorkArea_work_area_handler(0xff51, 0xff51, 0x140186658, 0x140178080, 0x3ffbff8c494) [0x120218370] 12 (unknown)() [0x3ffbff8c490] 13 fl_handle_object(0x140187600, 0x140187600, 0x3fc6300, 0xff51, 0x3ffbff51e90) [0x3ffbff8c584] 14 (unknown)() [0x3ffbff51e8c] 15 (unknown)() [0x3ffbff52504] 16 (unknown)() [0x3ffbff52970] 17 (unknown)() [0x3ffbff530fc] 18 fl_treat_interaction_events(0x13365100022641, 0x1336510001233d, 0x143954000d314c, 0x116320001233d, 0xa2c4500052a44) [0x3ffbff5386c] 19 fl_check_forms(0x143954000d314c, 0x116320001233d, 0xa2c4500052a44, 0x1233d00072739, 0x12037728c) [0x3ffbff538bc] 20 runTime__10GUIRunTimeXv(0x14019c260, 0x0, 0x14019c2c0, 0x3a017422, 0x140176690) [0x120377288] 21 runTime__6LyXGUIXv(0x14019c2c0, 0x3a017422, 0x140176690, 0x1400a8000, 0x120263e30) [0x12026047c] 22 __ct__3LyXXPiPPc(0x140065820, 0x3ffc00802a0, 0x12024cc6c, 0x140027148, 0x116c8) [0x120263e2c] 23 main(0x0, 0x80084600, 0x1400ecda0, 0x11748, 0x10001) [0x12028db2c]
Re: Natbib announcement (and 666 inset gripes)
On 18-Jul-2001 Mike Ressler wrote: > This is not a stunning example of WYSIWYM. Please, please, (Lars?) change > the appearance back to the old behavior!!! I don't think this will happen. What will happen is that we will change the InsetERT to be inlined. What will NOT happen is that a inlined ERT inset breaks row, so this is really thought only for short stuff! Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Might as well be frank, monsieur. It would take a miracle to get you out of Casablanca and the Germans have outlawed miracles. -- Casablanca
Re: Natbib announcement (and 666 inset gripes)
On Thu, 19 Jul 2001, Juergen Vigna wrote: > On 18-Jul-2001 Mike Ressler wrote: > > This is not a stunning example of WYSIWYM. Please, please, (Lars?) change > > the appearance back to the old behavior!!! > > I don't think this will happen. What will happen is that we will change > the InsetERT to be inlined. What will NOT happen is that a inlined ERT > inset breaks row, so this is really thought only for short stuff! I don't care what the underlying mechanism is (insets, fonts, etc.). I would like the _appearance_ to resemble the old style. Having it appear like a math inset would be fine. Maybe that is the model: an inlined ERT box and a "display" ERT box, for longer chunks of LaTeX code. Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Re: Natbib announcement (and 666 inset gripes)
On Thu, 19 Jul 2001, Juergen Vigna wrote: > On 19-Jul-2001 Mike Ressler wrote: > > > like a math inset would be fine. Maybe that is the model: an inlined ERT > > box and a "display" ERT box, for longer chunks of LaTeX code. > > That's exactly what we plan to do :) Excellent! Why didn't you just say so :-) Sorry if I sounded overly loud - I was just shocked by the appearance of those 666 boxes, and hadn't really followed the previous discussion closely enough to realize what was going on. Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Re: Natbib announcement (and 666 inset gripes)
On Thu, Jul 19, 2001 at 09:21:51AM +0200, Juergen Vigna wrote: > > On 18-Jul-2001 Mike Ressler wrote: > > > This is not a stunning example of WYSIWYM. Please, please, (Lars?) change > > the appearance back to the old behavior!!! > > I don't think this will happen. What will happen is that we will change > the InsetERT to be inlined. What will NOT happen is that a inlined ERT > inset breaks row, so this is really thought only for short stuff! can't you un-inline the ert inset automagically when it extends beyond the right margin of the workarea ? john -- "Voodoo Programming: Things programmers do that they know shouldn't work but they try anyway, and which sometimes actually work, such as recompiling everything." - Karl Lehenbauer
Re: Natbib announcement (and 666 inset gripes)
On 19-Jul-2001 John Levon wrote: > can't you un-inline the ert inset automagically when it extends beyond the right >margin > of the workarea ? Probably yes, but do I want to do this? Probably no, as then I would get complaints about this automatic behaviour someone surely doesn't like! Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Life sucks, but death doesn't put out at all. -- Thomas J. Kopp
Re: Natbib announcement (and 666 inset gripes)
On Thu, Jul 19, 2001 at 05:08:12PM +0200, Juergen Vigna wrote: > > On 19-Jul-2001 John Levon wrote: > > > can't you un-inline the ert inset automagically when it extends beyond the right >margin > > of the workarea ? > > Probably yes, but do I want to do this? Probably no, as then I would get > complaints about this automatic behaviour someone surely doesn't like! Think about the alternative - I add a lot of ert into the inset, so it is drawn off the side, and I can't even read it ! Surely we dont really have/want a choice in this circumstance. john -- "Voodoo Programming: Things programmers do that they know shouldn't work but they try anyway, and which sometimes actually work, such as recompiling everything." - Karl Lehenbauer
Re: Natbib announcement (and 666 inset gripes)
On Thursday 19 July 2001 16:08, Juergen Vigna wrote: > On 19-Jul-2001 John Levon wrote: > > > can't you un-inline the ert inset automagically when it extends beyond the right margin > > of the workarea ? > > Probably yes, but do I want to do this? Probably no, as then I would get > complaints about this automatic behaviour someone surely doesn't like! Well it seems like a good suggestion to me because it only affects the users ability to see what's on LyX's screen. Who's going to complain loudly about "LyX won't let me write text off the end of the screen when I want to"? Anyway, that's the joy of being an open source developer: you can tell the user to "get used to this behaviour I've implemented or change it yourself" if you decide they're being a PITA. As I probably am. Enough, Angus
Re: Natbib announcement (and 666 inset gripes)
On 19-Jul-2001 Angus Leeming wrote: >> Probably yes, but do I want to do this? Probably no, as then I would get >> complaints about this automatic behaviour someone surely doesn't like! > > Well it seems like a good suggestion to me because it only affects the users The only change to the above I would admit is making it displayed as soon as it is "Larger" then the screen, all other cases have to have a user interaction. Anyway before we have to implement the inlined stuff then we can discuss about this :) Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Lots of folks are forced to skimp to support a government that won't.
Re: Natbib announcement (and 666 inset gripes)
On Thursday 19 July 2001 16:14, Juergen Vigna wrote: > On 19-Jul-2001 John Levon wrote: > > > Think about the alternative - I add a lot of ert into the inset, so it is drawn off > > the side, and I can't even read it ! > > > > Surely we dont really have/want a choice in this circumstance. > > Well we have already the inset will scroll to the right if the cursor exits to > the left ;) (try this in a tabular cell where the InsetText IS inlined). Oh you bugger! I've just done this and now I'm getting infinite redraws of the table and can do nothing useful at all. Phew! LyX has just crashed on me. Road test to infinite redraws: 1. Insert table, I row, 2 columns 2. Type in first (leftmost) column until the table gets bigger than the width Bingo! Actually, If you leave this on screen doing its stuff then you'll crash LyX in malloc. Presumably it just runs out of memory therefore. Angus
Re: Natbib announcement (and 666 inset gripes)
On 19-Jul-2001 Angus Leeming wrote: > Road test to infinite redraws: > 1. Insert table, I row, 2 columns > 2. Type in first (leftmost) column until the table gets bigger than the width Well this is well known and as developer you should have looked at the buglist on SourceForge.net ;) Jürgen -- -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Dr. Jürgen VignaE-Mail: [EMAIL PROTECTED] Italienallee 13/N Tel/Fax: +39-0471-450260 / +39-0471-450253 I-39100 Bozen Web: http://www.sad.it/~jug -._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._ Your aim is high and to the right.
Re: Natbib announcement (and 666 inset gripes)
On Thu, Jul 19, 2001 at 05:50:43PM +0200, Juergen Vigna wrote: > > On 19-Jul-2001 Angus Leeming wrote: > > > Road test to infinite redraws: > > 1. Insert table, I row, 2 columns > > 2. Type in first (leftmost) column until the table gets bigger than the width > > Well this is well known and as developer you should have looked at the buglist > on SourceForge.net ;) actually it's changed behaviour recently - a 1x2 table didn't used to trigger it ... john -- "Voodoo Programming: Things programmers do that they know shouldn't work but they try anyway, and which sometimes actually work, such as recompiling everything." - Karl Lehenbauer
Re: Natbib announcement (and 666 inset gripes)
On Thursday 19 July 2001 16:50, Juergen Vigna wrote: > On 19-Jul-2001 Angus Leeming wrote: > > > Road test to infinite redraws: > > 1. Insert table, I row, 2 columns > > 2. Type in first (leftmost) column until the table gets bigger than the width > > Well this is well known and as developer you should have looked at the buglist > on SourceForge.net ;) I still think that this was a sly way to get help, but anyway I've played further. The infinite redraws are the result of a recursive cycling 18 updateLocal__C12InsetTabularXP10BufferView11UpdateCodesjb(0x28e, 0x0, 0x12034b334, 0x1401e4900, 0x1401814b0) [0x120348320] 19 resetPos__C12InsetTabularXP10BufferView(0x1401814b0, 0x1401e4938, 0x36, 0x1401e4968, 0x26a) [0x12034b330] 20 updateLocal__C12InsetTabularXP10BufferView11UpdateCodesjb(0x26a, 0x0, 0x12034b334, 0x1401e4900, 0x1401814b0) [0x120348320] 21 resetPos__C12InsetTabularXP10BufferView(0x1401814b0, 0x1401e4938, 0x1d, 0x1401e4968, 0x28e) [0x12034b330] 22 updateLocal__C12InsetTabularXP10BufferView11UpdateCodesjb(0x28e, 0x0, 0x12034b334, 0x1401e4900, 0x1401814b0) [0x120348320] Note that 18 and 22 are identical. As are 19 and 23 etc. So it's not just a simple oscillation between the two methods. Interestingly, if I create my table so that it reaches the width of the screen (just less) and then paste in some more text, then I CAN scroll. But doing so, I get a new problem. Effectively, I scroll off the end and into a segmentation fault. Backtrace below, but physically what happens is: Create a new document. Insert a table, 1row, 2cols Type "e e e e e e" in the first column until just before the table reaches screen width. Exit the table and on the line above type "elephant elephant" Cut this text, move the cursor around so only the line with the table on it exists. Paste the cut text into the leftmost column of the table so that the width is greater than the screen width. Scroll happily to the end of the first column (of two) with the right arrow key. Leave it and enter second column. Continue scrolling til we leave this column, continue scrolling (one more arrow press) to leave the table. The table is now redrawn with its left-most edge showing (fine), but the cursor is invisible. Pressing the arrow keys (some combination, any combo), to try and get the cursor visible again and eventually we get the segmentation fault and backtrace below. Angus signal Segmentation fault at >*[GetCellNumber__C10LyXTabularXii, 0x1202aaa08] ldl r0, 0(r0) (dbx) where > 0 GetCellNumber__C10LyXTabularXii(0x3ff801151ac, 0x, 0x12034ad68, 0x1401e2600, 0x397) [0x1202aaa08] 1 setPos__C12InsetTabularXP10BufferViewii(0x1401814b0, 0x397, 0xa, 0x0, 0x1400a80d8) [0x12034ad64] 2 edit__12InsetTabularXP10BufferViewiiUi(0x1201e83b8, 0x120348170, 0x1401e2600, 0x32, 0x1401814b0) [0x120348264] 3 Dispatch__Q110BufferView5PimplX9kb_actionRCQ13std60basic_string__TcQ13std15char_traits__TcQ13std13allocator__Tv(0x0, 0x0, 0x1201e56f0, 0x1400f6ed8, 0x1201dc100) [0x1201e83b4] 4 Dispatch__10BufferViewX9kb_actionRCQ13std60basic_string__TcQ13std15char_traits__TcQ13std13allocator__Tv(0x1201e56f0, 0x1400f6ed8, 0x1201dc100, 0x1400ac4c0, 0x120275bb0) [0x1201dc304] 5 dispatch__7LyXFuncXiRCQ13std60basic_string__TcQ13std15char_traits__TcQ13std13allocator__Tv(0x3ff801151ac, 0x1, 0x1ff51, 0x0, 0x1400f6e48) [0x120275bac] 6 processKeySym__7LyXFuncXUiUi(0x3ff801151ac, 0x1400a8000, 0x12042f700, 0x1400ac4c0, 0x120425108) [0x12027058c] 7 workAreaKeyPress__Q110BufferView5PimplXUiUi(0x12042f700, 0x1400ac4c0, 0x120425108, 0x140186658, 0x1201e02dc) [0x1201e288c] 8 (unknown)() [0x1201e02d8] 9 emit__Q14SigC38Signal2__Tv__TUiUiQ14SigC11Marshal__TvXRCUiRCUi(0x120219a30, 0x140186658, 0x61, 0x1400a5924, 0xcbff0c51) [0x120150a90] 10 work_area_handler__8WorkAreaXP7flobjs_Pv(0x540006f, 0xff51, 0xff51, 0xff51, 0x140186658) [0x120219a2c] 11 C_WorkArea_work_area_handler(0xff51, 0xff51, 0x140186658, 0x140178080, 0x3ffbff8c494) [0x120218370] 12 (unknown)() [0x3ffbff8c490] 13 fl_handle_object(0x140187600, 0x140187600, 0x3fc6300, 0xff51, 0x3ffbff51e90) [0x3ffbff8c584] 14 (unknown)() [0x3ffbff51e8c] 15 (unknown)() [0x3ffbff52504] 16 (unknown)() [0x3ffbff52970] 17 (unknown)() [0x3ffbff530fc] 18 fl_treat_interaction_events(0x13365100022641, 0x1336510001233d, 0x143954000d314c, 0x116320001233d, 0xa2c4500052a44) [0x3ffbff5386c] 19 fl_check_forms(0x143954000d314c, 0x116320001233d, 0xa2c4500052a44, 0x1233d00072739, 0x12037728c) [0x3ffbff538bc] 20 runTime__10GUIRunTimeXv(0x14019c260, 0x0, 0x14019c2c0, 0x3a017422, 0x140176690) [0x120377288] 21 runTime__6LyXGUIXv(0x14019c2c0, 0x3a017422, 0x140176690, 0x1400a8000, 0x120263e30) [0x12026047c] 22 __ct__3LyXXPiPPc(0x140065820, 0x3ffc00802a0, 0x12024cc6c, 0x140027148, 0x116c8) [0x120263e2c] 23 main(0x0, 0x80084600, 0x1400ecda0, 0x11748, 0x10001) [0x12028db2c]
Re: Natbib announcement (and 666 inset gripes)
On Wed, 18 Jul 2001, Angus Leeming wrote: I believe that the NATBIB branch is now in a fit state to merge back into head. This is now your final chance to try it out before I completely screw up the CVS head by rolling the branch back in ;-) Woo hoo!!! Yes! Grabbed it, compiled it, already playing with it - even though I should go to bed since I just finished observing all night and need to get up in 6 hours to start all over again. The natbib stuff is working great. Great job, Angus! That said, I want to gripe about the 666 insets, since this is the first I've seen them. I don't care what goes on under the hood, but I want them to look and behave like the old ERT. I was playing around with converting a paper I had written. If a bit of ERT appeared midsentence (e.g. I often insert \microns, rather than doing the $\mu$m equivalent), the line before it was justified fully left to right: if there were only 3 words on the line, one would be on the left, one dead center, the third on the right margin. It looks TERRIBLE! Furthermore, instead of aiding reading, a sentence like We observed the source at 10 \microns, whenever the weather was good shows up as We observed the source at 10 666 \microns , whenever the weather was good This is not a stunning example of WYSIWYM. Please, please, (Lars?) change the appearance back to the old behavior!!! I still like the natbib though!!! Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Re: Natbib announcement (and 666 inset gripes)
On Wed, Jul 18, 2001 at 11:49:45AM -0700, Mike Ressler wrote: That said, I want to gripe about the 666 insets, since this is the first yes, everyone has this gripe. Lars and Juergen are doing things to get it nice again, but with out re-introducing latex font mode (something that needs updating in the docs). ert-inset is the new thing, and will probably be made inlineable (by default). regards john -- Voodoo Programming: Things programmers do that they know shouldn't work but they try anyway, and which sometimes actually work, such as recompiling everything. - Karl Lehenbauer
Re: Natbib announcement (and 666 inset gripes)
John Levon wrote: On Wed, Jul 18, 2001 at 11:49:45AM -0700, Mike Ressler wrote: That said, I want to gripe about the 666 insets, since this is the first yes, everyone has this gripe. Lars and Juergen are doing things to get it nice again, but with out re-introducing latex font mode (something that needs updating in the docs). ert-inset is the new thing, and will probably be made inlineable (by default). The nice thing is that there is a growing list of common uses of ERT that LyX could do without using ERT. And John, clicking on MathPanel Greek killed LyX for me also, so it is probably not your xforms. Garst
Re: Natbib announcement (and 666 inset gripes)
On Wed, Jul 18, 2001 at 05:05:42PM -0300, Garst R. Reese wrote: And John, clicking on MathPanel Greek killed LyX for me also, so it is probably not your xforms. hmm. I've tried it against an xforms with /definitely/ the right glibc and still get the problem too. I'll have to see what's going on. There doesn't appear to be anything relevant in the ChangeLog :/ john -- Voodoo Programming: Things programmers do that they know shouldn't work but they try anyway, and which sometimes actually work, such as recompiling everything. - Karl Lehenbauer
Re: Natbib announcement (and 666 inset gripes)
On Wed, 18 Jul 2001, Angus Leeming wrote: > I believe that the NATBIB branch is now in a fit state to merge back into > head. This is now your final chance to try it out before I completely screw > up the CVS head by rolling the branch back in ;-) Woo hoo!!! Yes! Grabbed it, compiled it, already playing with it - even though I should go to bed since I just finished observing all night and need to get up in 6 hours to start all over again. The natbib stuff is working great. Great job, Angus! That said, I want to gripe about the 666 insets, since this is the first I've seen them. I don't care what goes on under the hood, but I want them to look and behave like the old ERT. I was playing around with converting a paper I had written. If a bit of ERT appeared midsentence (e.g. I often insert \microns, rather than doing the $\mu$m equivalent), the line before it was justified fully left to right: if there were only 3 words on the line, one would be on the left, one dead center, the third on the right margin. It looks TERRIBLE! Furthermore, instead of aiding reading, a sentence like We observed the source at 10 \microns, whenever the weather was good shows up as We observed the source at 10 666 \microns , whenever the weather was good This is not a stunning example of WYSIWYM. Please, please, (Lars?) change the appearance back to the old behavior!!! I still like the natbib though!!! Mike -- Mike Ressler [EMAIL PROTECTED] OK, I'm lame: I don't have my own website ...
Re: Natbib announcement (and 666 inset gripes)
On Wed, Jul 18, 2001 at 11:49:45AM -0700, Mike Ressler wrote: > That said, I want to gripe about the 666 insets, since this is the first yes, everyone has this gripe. Lars and Juergen are doing things to get it nice again, but with out re-introducing latex font mode (something that needs updating in the docs). ert-inset is the new thing, and will probably be made inlineable (by default). regards john -- "Voodoo Programming: Things programmers do that they know shouldn't work but they try anyway, and which sometimes actually work, such as recompiling everything." - Karl Lehenbauer
Re: Natbib announcement (and 666 inset gripes)
John Levon wrote: > > On Wed, Jul 18, 2001 at 11:49:45AM -0700, Mike Ressler wrote: > > > That said, I want to gripe about the 666 insets, since this is the first > > yes, everyone has this gripe. Lars and Juergen are doing things to get it nice > again, but with out re-introducing latex font mode (something that needs updating > in the docs). ert-inset is the new thing, and will probably be made inlineable (by >default). The nice thing is that there is a growing list of common uses of ERT that LyX could do without using ERT. And John, clicking on MathPanel Greek killed LyX for me also, so it is probably not your xforms. Garst
Re: Natbib announcement (and 666 inset gripes)
On Wed, Jul 18, 2001 at 05:05:42PM -0300, Garst R. Reese wrote: > And John, clicking on MathPanel Greek killed LyX for me also, so it is > probably not your xforms. hmm. I've tried it against an xforms with /definitely/ the right glibc and still get the problem too. I'll have to see what's going on. There doesn't appear to be anything relevant in the ChangeLog :/ john -- "Voodoo Programming: Things programmers do that they know shouldn't work but they try anyway, and which sometimes actually work, such as recompiling everything." - Karl Lehenbauer
Re: [666] grey-boxes around inlined math
Hi, Sorry to bring this issue up again; I had a look at the long thread of this topic and could follow/understand only a very few of them. My question is still: What is the LyX way of typing This is 2 A in size. Where A is the Angstrom (the tiny distance) symbol? I now use in texmode \AA. But that results in Thisis 2 [666]| || | \AA| || in size. Can't believe that's the way WYSIWYM of new-LyX (1.2.0) is going. Have I missed the trick about how to make this example a one-liner in LyX. Regards, Rob.
Re: [666] grey-boxes around inlined math
Have I missed the trick about how to make this example a one-liner in LyX. You seemingly missed a bit of the ongoing Lars bashing... Andre' -- André Pönitz . [EMAIL PROTECTED]
Re: [666] grey-boxes around inlined math
Andre Poenitz wrote: Have I missed the trick about how to make this example a one-liner in LyX. You seemingly missed a bit of the ongoing Lars bashing... Should I learn from this reply that in LyX WYSIWYM This is 2 A apart. will not anymore fit on one line (A as the Angstrom symbol). Then in LyX it would look even uglier than in the raw LaTeX code !!??!! Strange. Rob.
Re: [666] grey-boxes around inlined math
R. Lahaye [EMAIL PROTECTED] writes: | Hi, | | Sorry to bring this issue up again; I had a look at the long thread of this topic | and could follow/understand only a very few of them. | | My question is still: What is the LyX way of typing | |This is 2 A in size. | | Where A is the Angstrom (the tiny distance) symbol? Of course you could just use 'Å'... alternatively accent-circle A | I now use in texmode \AA. But that results in | | Thisis 2 | | [666]| | || | | \AA| | || I have a simple solution for these cases. -- Lgb
Re: [666] grey-boxes around inlined math
R. Lahaye [EMAIL PROTECTED] writes: | Lars Gullik Bjønnes wrote: | | R. Lahaye [EMAIL PROTECTED] writes: | | | Where A is the Angstrom (the tiny distance) symbol? | | Of course you could just use 'Å'... alternatively accent-circle A | | Great! Didn't know that! | | How do I squeeze such funny characters as 'Å' out of my simple keyboard? | For now I cut pasted from your email into LyX :(. | | Is accent-circle a magic key-combination (e.g. Alt-Shift-... or so)? | | And then more general: Where can I learn about how to generate all other | unusual characters in LyX ? (\oe, \o, \l, \SS and many more). \oe not in latin1 \o is 'ø' 'Ø' \l not in latin1 \SS is 'ß' We do not have good support for the unaccented special chars. -- Lgb
Re: [666] grey-boxes around inlined math
Lars Gullik Bjnnes wrote: \oe not in latin1 \o is '' '' \l not in latin1 \SS is '' Black Magic! We do not have good support for the unaccented special chars. A window like the math-panel could help out here. Support is a must, I bet, if LyX 1.2.0 persues the [666] insets style. Rob.
