Re: Insert underscore (_) in math ERT?

On Fri, Jul 07, 2023 at 11:33:17AM +0300, Udicoudco wrote: > On Fri, Jul 7, 2023 at 11:30 AM Udicoudco wrote: > > \let\Scott_ > Sorry, it should be \let\foo_ of course... I mixed things a bit :) > Attached a corrected example. Wow, that's creative! It did not work for me. I think the difference

Re: Insert underscore (_) in math ERT?

On Fri, Jul 7, 2023 at 11:30 AM Udicoudco wrote: > \let\Scott_ Sorry, it should be \let\foo_ of course... I mixed things a bit :) Attached a corrected example. > > -- > > lyx-devel mailing list > > lyx-devel@lists.lyx.org > > http://lists.lyx.org/mailman/listinfo/lyx-devel

Re: Insert underscore (_) in math ERT?

On Fri, Jul 7, 2023 at 11:09 AM Scott Kostyshak wrote: > Basically, is there any workaround to be able to use LyX's math mode and > output the LaTeX \Sexpr{mean(x_draws)}? > > If I try to paste from LaTeX, LyX converts it to the following: > $\Sexpr{mean(x_{d}raws)}$, which gives a knitr error.

Insert underscore (_) in math ERT?

If I recall correctly, it's a known issue that we don't have true ERT in math mode. We can still insert custom LaTeX commands, but sometimes the workaround is limited. For example, in a knitr document (which runs R on commands in the .lyx file and substitutes in the output), R functions

Re: #11579: Words cannot be input into ERT when using "Unicode (CJK) (utf8)" encoding

Yes, this problem occurs only on windows, not linux. 在 2019/7/20 13:05, LyX Ticket Tracker 写道: #11579: Words cannot be input into ERT when using "Unicode (CJK) (utf8)" encoding +- Reporter: goodluck| Owner: lasgouttes

Re: Is it possible to make the ERT inset show different colors for different text?

On 2019-06-27, Richard Kimberly Heck wrote: > On 6/27/19 1:36 PM, Kornel Benko wrote: >> Am Donnerstag, 27. Juni 2019, 12:08:05 CEST schrieb Jason Sun: >>> I think this is crucial to implement syntax highlighting of ERT box. >> I don't think so. ERT is/was meant for

Re: Is it possible to make the ERT inset show different colors for different text?

Le 27/06/2019 à 18:08, Jason Sun a écrit : I think this is crucial to implement syntax highlighting of ERT box. I tend to be careful with sentences that contain words like 'crucial' ;) Qt text edit does support some syntax highlighting, so we could have that in a dialog

Re: Is it possible to make the ERT inset show different colors for different text?

On 6/27/19 1:36 PM, Kornel Benko wrote: > Am Donnerstag, 27. Juni 2019, 12:08:05 CEST schrieb Jason Sun: >> I think this is crucial to implement syntax highlighting of ERT box. >> > I don't think so. ERT is/was meant for text, which we do _not_ interpret. Yes, if you want to

Re: Is it possible to make the ERT inset show different colors for different text?

Am Donnerstag, 27. Juni 2019, 12:08:05 CEST schrieb Jason Sun: > I think this is crucial to implement syntax highlighting of ERT box. > I don't think so. ERT is/was meant for text, which we do _not_ interpret. Kornel signature.asc Description: This is a digitally signed message part.

Is it possible to make the ERT inset show different colors for different text?

I think this is crucial to implement syntax highlighting of ERT box.

Re: Closing ERT inset in LyX 2.3.0

On 09/18/2018 10:15 AM, Rasmus K. Rendsvig wrote: > I had made customizations. Starting fresh, the entry in the context > menu is indeed present. > > I apologize for not having checked this possibility -- it's been so > long, that I had simply forgotten. This is a very common thing. I do it all

Re: Closing ERT inset in LyX 2.3.0

I had made customizations. Starting fresh, the entry in the context menu is indeed present. I apologize for not having checked this possibility -- it's been so long, that I had simply forgotten. Thank you all for your help. All the best, Rasmus

Re: Closing ERT inset in LyX 2.3.0

gt;> >> Not on my system (LyX 2.3.0, Linux Mint 18.3). If I right-click in an >> ERT box, "Close Inset" (accelerator key "C") is the second item in the >> context menu. > If the OP made any menu customizations, these may be over-riding the new > behavior.

Re: Closing ERT inset in LyX 2.3.0

On 09/12/2018 01:52 PM, Paul A. Rubin wrote: > On 09/12/2018 07:21 AM, Rasmus K. Rendsvig wrote: >> included a "close inset" option to collapse them, but this is gone in >> 2.3.0. >> >> > Not on my system (LyX 2.3.0, Linux Mint 18.3). If I right-click in

Re: Closing ERT inset in LyX 2.3.0

On 09/12/2018 07:21 AM, Rasmus K. Rendsvig wrote: included a "close inset" option to collapse them, but this is gone in 2.3.0. Not on my system (LyX 2.3.0, Linux Mint 18.3). If I right-click in an ERT box, "Close Inset" (accelerator key "C") is the second item in the context menu. Paul

Re: Closing ERT inset in LyX 2.3.0

On 12/09/2018 13:21, Rasmus K. Rendsvig wrote: Dear LyX developers, First of all, thank you for the so ever-amazing LyX. I use it daily, push it to my students and collaborators, and would not know what to do if it was not around. Thank you! My question/comment/bug/plea concerns ERT insets

Closing ERT inset in LyX 2.3.0

Dear LyX developers, First of all, thank you for the so ever-amazing LyX. I use it daily, push it to my students and collaborators, and would not know what to do if it was not around. Thank you! My question/comment/bug/plea concerns ERT insets in 2.3.0 and their collapsability. Unlike e.g

Mark ERT at documents end

Hello, Summary of the problem (from Lyx Bug Tracker): In large insets, like ERT, scrolling down is difficult. The cursor goes down to the end of ERT and jumps then up to the pilcrow at the beginning of ERT (to highlight the whole inset). Then the cursor jumps again to the first line

Pasting TeX code in Lyx ERT inset looses layout

Hi. When I paste TeX code from a text editor in an ERT inset in a LyX document, the text layout from the text editor is lost, and I have to enter the newlines and the tabulations manually in order to have the original layout back in the ERT inset. Do you experience the same issue? Do you have

Re: Pasting TeX code in Lyx ERT inset looses layout

On Tue, 02 Dec 2014 16:40:51 +0100, Gim gilles.mo...@gmail.com wrote: NB : I first asked this question on Tex StackExchange, cf: http://tex.stackexchange.com/questions/214989/pasting-tex-code-in-lyx-ert-inset-looses-layout I answered your question on TeX SE: http://tex.stackexchange.com

Pasting TeX code in Lyx ERT inset looses layout

Hi. When I paste TeX code from a text editor in an ERT inset in a LyX document, the text layout from the text editor is lost, and I have to enter the newlines and the tabulations manually in order to have the original layout back in the ERT inset. Do you experience the same issue? Do you have

Re: Pasting TeX code in Lyx ERT inset looses layout

On Tue, 02 Dec 2014 16:40:51 +0100, Gim <gilles.mo...@gmail.com> wrote: NB : I first asked this question on Tex StackExchange, cf: http://tex.stackexchange.com/questions/214989/pasting-tex-code-in-lyx-ert-inset-looses-layout I answered your question on TeX SE: http://tex.stackexchan

Re: [LyX/master] Beamer block conversion: consider ERT arguments with leading/trailing blanks

On 05/08/2014 09:14 AM, Juergen Spitzmueller wrote: commit 769b585176a78bc9a1380190e145aafdbe7d3a17 Author: Juergen Spitzmueller sp...@lyx.org Date: Thu May 8 15:14:44 2014 +0200 Beamer block conversion: consider ERT arguments with leading/trailing blanks Should also go

Re: [LyX/master] Beamer block conversion: consider ERT arguments with leading/trailing blanks

On 05/08/2014 09:14 AM, Juergen Spitzmueller wrote: commit 769b585176a78bc9a1380190e145aafdbe7d3a17 Author: Juergen Spitzmueller <sp...@lyx.org> Date: Thu May 8 15:14:44 2014 +0200 Beamer block conversion: consider ERT arguments with leading/trailing blanks Should a

Re: [patch] Fix bug 8874 Chunk insets behave differently form ERT insets when applying formatting

09/02/2014 15:30, Georg Baum: You mean resetFontEdit() should return return true if isPassThru() returns true? This would certainly make sense, but I am not sure if we should do it now. My proposed patch is conservative in the sense that the behaviour is not changed for any inset except the

Re: [patch] Fix bug 8874 Chunk insets behave differently form ERT insets when applying formatting

Jean-Marc Lasgouttes wrote: Thanks for looking at this. Thanks for the comments, I took all of them into account abnd submitted the patch. Georg

Re: [patch] Fix bug 8874 Chunk insets behave differently form ERT insets when applying formatting

09/02/2014 15:30, Georg Baum: You mean resetFontEdit() should return return true if isPassThru() returns true? This would certainly make sense, but I am not sure if we should do it now. My proposed patch is conservative in the sense that the behaviour is not changed for any inset except the

Re: [patch] Fix bug 8874 Chunk insets behave differently form ERT insets when applying formatting

Jean-Marc Lasgouttes wrote: > Thanks for looking at this. Thanks for the comments, I took all of them into account abnd submitted the patch. Georg

Re: [patch] Fix bug 8874 Chunk insets behave differently form ERT insets when applying formatting

Jean-Marc Lasgouttes wrote: I have a couple questions still. * the description I see of ResetsFont in the Customization manual strikes me as being like the opposite of Inset::inheritFont. How could an inset have non-compatible values for these two values? Would it make any sense? Or is one

Re: [patch] Fix bug 8874 Chunk insets behave differently form ERT insets when applying formatting

Jean-Marc Lasgouttes wrote: > I have a couple questions still. > > * the description I see of ResetsFont in the Customization manual > strikes me as being like the opposite of Inset::inheritFont. How could > an inset have non-compatible values for these two values? Would it make > any sense? Or

Re: [patch] Fix bug 8874 Chunk insets behave differently form ERT insets when applying formatting

Georg Baum wrote: I tested this patch extensively, and it works fine now (it is the third version), but since it involves a layout file format change I'd rather ask: Is it OK to go in? I am all for it. Regards, Jürgen

Re: [patch] Fix bug 8874 Chunk insets behave differently form ERT insets when applying formatting

06/02/2014 22:14, Georg Baum: This is one of three bugs scheduled for 2.1.0: If you apply font changes, e.g. small size to a paragraph including a chunk inset, the result will not be compilable anymore (only after saving and reloading the document). Jean-Marc did the detective work and found

Re: [patch] Fix bug 8874 Chunk insets behave differently form ERT insets when applying formatting

Georg Baum wrote: > I tested this patch extensively, and it works fine now (it is the third > version), but since it involves a layout file format change I'd rather ask: > Is it OK to go in? I am all for it. Regards, Jürgen

Re: [patch] Fix bug 8874 Chunk insets behave differently form ERT insets when applying formatting

06/02/2014 22:14, Georg Baum: This is one of three bugs scheduled for 2.1.0: If you apply font changes, e.g. small size to a paragraph including a chunk inset, the result will not be compilable anymore (only after saving and reloading the document). Jean-Marc did the detective work and found

[patch] Fix bug 8874 Chunk insets behave differently form ERT insets when applying formatting

This is one of three bugs scheduled for 2.1.0: If you apply font changes, e.g. small size to a paragraph including a chunk inset, the result will not be compilable anymore (only after saving and reloading the document). Jean-Marc did the detective work and found out the reason: resetFontEdit()

[patch] Fix bug 8874 Chunk insets behave differently form ERT insets when applying formatting

This is one of three bugs scheduled for 2.1.0: If you apply font changes, e.g. small size to a paragraph including a chunk inset, the result will not be compilable anymore (only after saving and reloading the document). Jean-Marc did the detective work and found out the reason: resetFontEdit()

Knitr ERT inset ?

Could anyone that has an opinion on this subject please have a look at bug 8514 ? http://www.lyx.org/trac/ticket/8514 Vincent

Knitr ERT inset ?

Could anyone that has an opinion on this subject please have a look at bug 8514 ? http://www.lyx.org/trac/ticket/8514 Vincent

math manual: Why spce in ERT?

Dear LyX Team, Why does the Math manual define \newcommand{\spce}{\textvisiblespace} in the preamble and uses it in ERT boxes throuhout the document? LyX understands Character '␣' (9251, 0x2423) OPEN BOX and translates it to \textvisiblespace in the LaTeX source. When I try to search

Re: math manual: Why spce in ERT?

Le 24/05/2011 15:14, Guenter Milde a écrit : Dear LyX Team, Why does the Math manual define \newcommand{\spce}{\textvisiblespace} in the preamble and uses it in ERT boxes throuhout the document? LyX understands Character '␣' (9251, 0x2423) OPEN BOX and translates it to \textvisiblespace

Re: math manual: Why spce in ERT?

On Tue, May 24, 2011 at 03:42:23PM +0200, Jean-Marc Lasgouttes wrote: Le 24/05/2011 15:14, Guenter Milde a écrit : Dear LyX Team, Why does the Math manual define \newcommand{\spce}{\textvisiblespace} in the preamble and uses it in ERT boxes throuhout the document? LyX understands

Re: math manual: Why spce in ERT?

Il 24/05/2011 15:14, Guenter Milde ha scritto: LyX understands Character '␣' (9251, 0x2423) OPEN BOX and translates it to \textvisiblespace in the LaTeX source. When I try to search/replace the ERT boxes via the Advanced search, only the content (\spce) is replaced and I end up with the OPEN

Re: math manual: Why spce in ERT?

Le 24/05/2011 18:26, Enrico Forestieri a écrit : I proposed that to Uwe some time ago and it turns out that typical windows fonts do not have this unicode glyph for display... That is not true, I just tried unicode-insert 0x2423 with Times New Roman, Arial, and Courier New, and all of those

math manual: Why spce in ERT?

Dear LyX Team, Why does the Math manual define \newcommand{\spce}{\textvisiblespace} in the preamble and uses it in ERT boxes throuhout the document? LyX understands Character '␣' (9251, 0x2423) OPEN BOX and translates it to \textvisiblespace in the LaTeX source. When I try to search

Re: math manual: Why spce in ERT?

Le 24/05/2011 15:14, Guenter Milde a écrit : Dear LyX Team, Why does the Math manual define \newcommand{\spce}{\textvisiblespace} in the preamble and uses it in ERT boxes throuhout the document? LyX understands Character '␣' (9251, 0x2423) OPEN BOX and translates it to \textvisiblespace

Re: math manual: Why spce in ERT?

On Tue, May 24, 2011 at 03:42:23PM +0200, Jean-Marc Lasgouttes wrote: > Le 24/05/2011 15:14, Guenter Milde a écrit : > >Dear LyX Team, > > > >Why does the Math manual define > > > > \newcommand{\spce}{\textvisiblespace} > > > >in the preamble an

Re: math manual: Why spce in ERT?

Il 24/05/2011 15:14, Guenter Milde ha scritto: LyX understands Character '␣' (9251, 0x2423) OPEN BOX and translates it to \textvisiblespace in the LaTeX source. When I try to search/replace the ERT boxes via the Advanced search, only the content (\spce) is replaced and I end up with the OPEN

Re: math manual: Why spce in ERT?

Le 24/05/2011 18:26, Enrico Forestieri a écrit : I proposed that to Uwe some time ago and it turns out that typical windows fonts do not have this unicode glyph for display... That is not true, I just tried "unicode-insert 0x2423" with "Times New Roman", "Arial", and "Courier New", and all of

Re: Regression in r37463 by switt: Crash when deleting ERT from inside

Am 10.03.2011 um 04:42 schrieb John McCabe-Dansted: (Was Regression in r37463 by switt: Crash when deleting footnote) I found another bug that appears to be caused by r37463 KEYCODES: \Cla\[Delete] To Reproduce 1) Press Ctrl-L to enter ERT mode 2) Press A to enter a character 3) Press

Re: Regression in r37463 by switt: Crash when deleting ERT from inside

Am 10.03.2011 um 04:42 schrieb John McCabe-Dansted: > (Was Regression in r37463 by switt: Crash when deleting footnote) > I found another bug that appears to be caused by r37463 > > KEYCODES: \Cla\[Delete] > To Reproduce > 1) Press Ctrl-L to enter ERT mode > 2) Press A to

Regression in r37463 by switt: Crash when deleting ERT from inside

(Was Regression in r37463 by switt: Crash when deleting footnote) I found another bug that appears to be caused by r37463 KEYCODES: \Cla\[Delete] To Reproduce 1) Press Ctrl-L to enter ERT mode 2) Press A to enter a character 3) Press Delete to delete the ERT container. Program received signal

Regression in r37463 by switt: Crash when deleting ERT from inside

(Was Regression in r37463 by switt: Crash when deleting footnote) I found another bug that appears to be caused by r37463 KEYCODES: \Cla\[Delete] To Reproduce 1) Press Ctrl-L to enter ERT mode 2) Press A to enter a character 3) Press Delete to delete the ERT container. Program received signal

Re: (Regression in r37749 by forenr) Assert with ERT inset and LaTeX Error dialog open.

On Tue, Mar 1, 2011 at 2:55 AM, Pavel Sanda sa...@lyx.org wrote: neither me. John are you running up to date svn? It was quite recent, but I updated I now I cannot reproduce either :). -- John C. McCabe-Dansted

Re: (Regression in r37749 by forenr) Assert with ERT inset and LaTeX Error dialog open.

John McCabe-Dansted wrote: On Tue, Mar 1, 2011 at 2:55 AM, Pavel Sanda sa...@lyx.org wrote: neither me. John are you running up to date svn? It was quite recent, but I updated I now I cannot reproduce either :). yep something similar was fixed recently.p

Re: (Regression in r37749 by forenr) Assert with ERT inset and LaTeX Error dialog open.

On Tue, Mar 1, 2011 at 2:55 AM, Pavel Sanda wrote: > neither me. John are you running up to date svn? It was quite recent, but I updated I now I cannot reproduce either :). -- John C. McCabe-Dansted

Re: (Regression in r37749 by forenr) Assert with ERT inset and LaTeX Error dialog open.

John McCabe-Dansted wrote: > On Tue, Mar 1, 2011 at 2:55 AM, Pavel Sanda wrote: > > neither me. John are you running up to date svn? > > It was quite recent, but I updated I now I cannot reproduce either :). yep something similar was fixed recently.p

(Regression in r37749 by forenr) Assert with ERT inset and LaTeX Error dialog open.

To Reproduce: 1) Press Alt-Delete to insert a non-printable character 2) Press Ctrl-L to insert an ERT inset 3) Press Ctrl-D to bring up the LaTeX error dialog box. 4) Click inside the ERT. I then get the following assert. This appears to be a regression in r37749 by forenr, though note that I

Re: (Regression in r37749 by forenr) Assert with ERT inset and LaTeX Error dialog open.

On Mon, Feb 28, 2011 at 08:48:46PM +0800, John McCabe-Dansted wrote: To Reproduce: 1) Press Alt-Delete to insert a non-printable character 2) Press Ctrl-L to insert an ERT inset 3) Press Ctrl-D to bring up the LaTeX error dialog box. 4) Click inside the ERT. Sorry, cannot reproduce

Re: (Regression in r37749 by forenr) Assert with ERT inset and LaTeX Error dialog open.

Enrico Forestieri wrote: On Mon, Feb 28, 2011 at 08:48:46PM +0800, John McCabe-Dansted wrote: To Reproduce: 1) Press Alt-Delete to insert a non-printable character 2) Press Ctrl-L to insert an ERT inset 3) Press Ctrl-D to bring up the LaTeX error dialog box. 4) Click inside the ERT

(Regression in r37749 by forenr) Assert with ERT inset and LaTeX Error dialog open.

To Reproduce: 1) Press Alt-Delete to insert a non-printable character 2) Press Ctrl-L to insert an ERT inset 3) Press Ctrl-D to bring up the LaTeX error dialog box. 4) Click inside the ERT. I then get the following assert. This appears to be a regression in r37749 by forenr, though note that I

Re: (Regression in r37749 by forenr) Assert with ERT inset and LaTeX Error dialog open.

On Mon, Feb 28, 2011 at 08:48:46PM +0800, John McCabe-Dansted wrote: > To Reproduce: > 1) Press Alt-Delete to insert a non-printable character > 2) Press Ctrl-L to insert an ERT inset > 3) Press Ctrl-D to bring up the LaTeX error dialog box. > 4) Click inside the ERT. Sorry, c

Re: (Regression in r37749 by forenr) Assert with ERT inset and LaTeX Error dialog open.

Enrico Forestieri wrote: > On Mon, Feb 28, 2011 at 08:48:46PM +0800, John McCabe-Dansted wrote: > > > To Reproduce: > > 1) Press Alt-Delete to insert a non-printable character > > 2) Press Ctrl-L to insert an ERT inset > > 3) Press Ctrl-D to bring up the LaTeX

Re: edit ERT insets with external editor?

On 2010-04-01, rgheck wrote: On 04/01/2010 04:41 AM, Abdelrazak Younes wrote: On 03/31/2010 05:53 PM, Liviu Andronic wrote: Dear LyX developers Would it be a good idea to allow users to edit ERT insets with an external editor? [snip] It is a good idea but it sounds a bit complicated

Re: edit ERT insets with external editor?

Hello On Tue, Apr 6, 2010 at 12:16 PM, Guenter Milde mi...@users.berlios.de wrote: * will have a favourite LaTeX editor. Reproducing the favourite LaTeX editors in LyX will never reach near the original. Abdel's idea to use QScintilla looks very appealing to me. This has the advantage of

Re: edit ERT insets with external editor?

On 2010-04-01, rgheck wrote: > On 04/01/2010 04:41 AM, Abdelrazak Younes wrote: >> On 03/31/2010 05:53 PM, Liviu Andronic wrote: >>> Dear LyX developers >>> Would it be a good idea to allow users to edit ERT insets with an >>> external editor? [snip] >

Re: edit ERT insets with external editor?

Hello On Tue, Apr 6, 2010 at 12:16 PM, Guenter Milde wrote: > * will have a favourite LaTeX editor. > > Reproducing the favourite LaTeX editors in LyX will never reach near the > original. > Abdel's idea to use QScintilla looks very appealing to me. This has the advantage

Re: edit ERT insets with external editor?

On 03/31/2010 05:53 PM, Liviu Andronic wrote: Dear LyX developers Would it be a good idea to allow users to edit ERT insets with an external editor? I am thinking of something similar to: 1. Have a Edit with external editor entry to the ERT inset context menu 2. When activated, LyX would export

Re: edit ERT insets with external editor?

On 04/01/2010 04:41 AM, Abdelrazak Younes wrote: On 03/31/2010 05:53 PM, Liviu Andronic wrote: Dear LyX developers Would it be a good idea to allow users to edit ERT insets with an external editor? [snip] It is a good idea but it sounds a bit complicated to implement for the communication

Re: edit ERT insets with external editor?

On 04/01/2010 05:32 PM, rgheck wrote: On 04/01/2010 04:41 AM, Abdelrazak Younes wrote: On 03/31/2010 05:53 PM, Liviu Andronic wrote: Dear LyX developers Would it be a good idea to allow users to edit ERT insets with an external editor? [snip] It is a good idea but it sounds a bit complicated

Re: edit ERT insets with external editor?

On 03/31/2010 05:53 PM, Liviu Andronic wrote: Dear LyX developers Would it be a good idea to allow users to edit ERT insets with an external editor? I am thinking of something similar to: 1. Have a "Edit with external editor" entry to the ERT inset context menu 2. When activated,

Re: edit ERT insets with external editor?

On 04/01/2010 04:41 AM, Abdelrazak Younes wrote: On 03/31/2010 05:53 PM, Liviu Andronic wrote: Dear LyX developers Would it be a good idea to allow users to edit ERT insets with an external editor? [snip] It is a good idea but it sounds a bit complicated to implement for the communication

Re: edit ERT insets with external editor?

On 04/01/2010 05:32 PM, rgheck wrote: On 04/01/2010 04:41 AM, Abdelrazak Younes wrote: On 03/31/2010 05:53 PM, Liviu Andronic wrote: Dear LyX developers Would it be a good idea to allow users to edit ERT insets with an external editor? [snip] It is a good idea but it sounds a bit complicated

edit ERT insets with external editor?

Dear LyX developers Would it be a good idea to allow users to edit ERT insets with an external editor? I am thinking of something similar to: 1. Have a Edit with external editor entry to the ERT inset context menu 2. When activated, LyX would export the current contents of the ERT inset

edit ERT insets with external editor?

Dear LyX developers Would it be a good idea to allow users to edit ERT insets with an external editor? I am thinking of something similar to: 1. Have a "Edit with external editor" entry to the ERT inset context menu 2. When activated, LyX would export the current contents of the

ERT insert preview

Hi, a couple of friends of mine and I think that being able to (optionally) preview ERT inserts would be very nice, it would definetely step-up LyX power: we could use a lot of TeX packages without having to use an external document to have instant preview. Do you think it would be difficult

Re: ERT insert preview

venom00 wrote: Do you think it would be difficult to implement? I'm at my first experience with LyX code, but I could give a look. What do you think? the code is partly finished and hopefully shipped with 2.0. pavel

ERT insert preview

Hi, a couple of friends of mine and I think that being able to (optionally) preview ERT inserts would be very nice, it would definetely step-up LyX power: we could use a lot of TeX packages without having to use an external document to have instant preview. Do you think it would be difficult

Re: ERT insert preview

venom00 wrote: > Do you think it would be difficult to implement? I'm at my first experience > with LyX code, but I could give a look. > > What do you think? the code is partly finished and hopefully shipped with 2.0. pavel

Re: #6569: copying ERT instance and changing it corrupts latex source

thanks that explanation appears very logical. I have no experience with using other languages on lyx so never thought about it in that way. best samar On 8 March 2010 18:28, LyX Ticket Tracker t...@lyx.org wrote: #6569: copying ERT instance and changing it corrupts latex source

Re: #6569: copying ERT instance and changing it corrupts latex source

thanks that explanation appears very logical. I have no experience with using other languages on lyx so never thought about it in that way. best samar On 8 March 2010 18:28, LyX Ticket Tracker <t...@lyx.org> wrote: > #6569: copying ERT instance and changing it corrupts lat

Re: #6569: copying ERT instance and changing it corrupts latex source

Hi Very happy to assist in this way. Please see attached file. I am not sure this is specific to my machine. Please let me know if this happens on your machine too. best samar On 3 March 2010 01:13, LyX Ticket Tracker t...@lyx.org wrote: #6569: copying ERT instance and changing it corrupts

Re: #6569: copying ERT instance and changing it corrupts latex source

Samar Singh wrote: I am not sure this is specific to my machine. Please let me know if this happens on your machine too. no it doesnt not happen on my machine even with your file. moreover lyx really shouldnt do this. isn't possibly you have some keyboard completer on OS level? pavel

Re: #6569: copying ERT instance and changing it corrupts latex source

Hmm! interesting. It has not happened to me before. I shall try to do this and see if it replicates on another machine running Ubuntu 9.10 maybe its an os level problem. I dont think I have any keyboard completer in Ubuntu but shall investigate. Really appreciate the quick response samar

Re: #6569: copying ERT instance and changing it corrupts latex source

Hi Very happy to assist in this way. Please see attached file. I am not sure this is specific to my machine. Please let me know if this happens on your machine too. best samar On 3 March 2010 01:13, LyX Ticket Tracker <t...@lyx.org> wrote: > #6569: copying ERT instance and

Re: #6569: copying ERT instance and changing it corrupts latex source

Samar Singh wrote: > I am not sure this is specific to my machine. Please let me know if this > happens on your machine too. no it doesnt not happen on my machine even with your file. moreover lyx really shouldnt do this. isn't possibly you have some keyboard completer on OS level? pavel

Re: #6569: copying ERT instance and changing it corrupts latex source

Hmm! interesting. It has not happened to me before. I shall try to do this and see if it replicates on another machine running Ubuntu 9.10 maybe its an os level problem. I dont think I have any keyboard completer in Ubuntu but shall investigate. Really appreciate the quick response samar

Re: [patch] ERT instant preview

Pavel Sanda wrote: yes thats my idea. only erts toggled by user would be rendered through instant preview. pavel You may want to search the ERT contents for unbalanced { and [, and simply refuse preview in those cases. Helge Hafting

Re: [patch] ERT instant preview

Pavel Sanda wrote: yes thats my idea. only erts toggled by user would be rendered through instant preview. pavel You may want to search the ERT contents for unbalanced "{" and "[", and simply refuse preview in those cases. Helge Hafting

Re: [patch] ERT instant preview

Vincent van Ravesteijn wrote: no debug symbols here too, but anyway looks like metrics stuff #0 0x083b2713 in lyx::TextMetrics::getPitNearY () #1 0x083b373c in lyx::TextMetrics::checkInsetHit () #2 0x083fc68f in lyx::BufferView::getCoveringInset () #3 0x083fc6f8 in

Re: [patch] ERT instant preview

Pavel Sanda wrote: Jean-Marc Lasgouttes wrote: Le 14 déc. 09 ? 19:47, Pavel Sanda a écrit : Vincent van Ravesteijn - TNW wrote: A rough try to add instant preview for ERT. LyX crashes when you hover your mouse over it, but apart from that it seems to work with almost only code

Re: [patch] ERT instant preview

Abdelrazak Younes wrote: yes thats my idea. only erts toggled by user would be rendered through instant preview. That's too complicated IMHO. I would rather see something based on InsetFlex which will tell that this inset is really an ERT with graphics preview. So that you don't have

Re: [patch] ERT instant preview

Pavel Sanda wrote: Abdelrazak Younes wrote: yes thats my idea. only erts toggled by user would be rendered through instant preview. That's too complicated IMHO. I would rather see something based on InsetFlex which will tell that this inset is really an ERT with graphics preview. So

Re: [patch] ERT instant preview

Abdelrazak Younes wrote: yes thats my idea. only erts toggled by user would be rendered through instant preview. That's too complicated IMHO. I would rather see something based on InsetFlex which will tell that this inset is really an ERT with graphics preview. So that you don't

RE: [patch] ERT instant preview

. Anyway.. Why not making a real Inset InsetPreview (:public InsetText) that previews what is inside. This can then be a mixture of ERTs, normal text and maybe graphics.. In that way, you can use it for psfrag and stuff like that: \begin InsetPreview \begin ERT \psfrag{a}{b} \end ERT \begin

Re: RE: [patch] ERT instant preview

Original-Nachricht Datum: Tue, 15 Dec 2009 10:34:44 +0100 Von: Vincent van Ravesteijn - TNW v.f.vanraveste...@tudelft.nl An: Abdelrazak Younes you...@lyx.org CC: lyx-devel@lists.lyx.org Betreff: RE: [patch] ERT instant preview Anyway.. Why

Re: [patch] ERT instant preview

Vincent van Ravesteijn - TNW wrote: Why not making a real Inset InsetPreview (:public InsetText) that previews what is inside. This can then be a mixture of ERTs, normal text and maybe graphics.. looks much more general approach indeed. pael

RE: [patch] ERT instant preview

Vincent van Ravesteijn - TNW wrote: Why not making a real Inset InsetPreview (:public InsetText) that previews what is inside. This can then be a mixture of ERTs, normal text and maybe graphics.. I think preview should be optional for all InsetTexts. If we would have a Parameter

Re: [patch] ERT instant preview

... In that way, you can use it for psfrag and stuff like that: \begin InsetPreview \begin ERT \psfrag{a}{b} \end ERT \begin InsetGraphics \file a.eps \end InsetGraphics \end InsetPreview Switching between a previewed ERT and normal ERT is then moving it in or out of the InsetPreview

Re: [patch] ERT instant preview

Jürgen Spitzmüller wrote: Vincent van Ravesteijn - TNW wrote: Why not making a real Inset InsetPreview (:public InsetText) that previews what is inside. This can then be a mixture of ERTs, normal text and maybe graphics.. I think preview should be optional for all InsetTexts. If we

Re: [patch] ERT instant preview

Vincent van Ravesteijn wrote: no debug symbols here too, but anyway looks like metrics stuff #0 0x083b2713 in lyx::TextMetrics::getPitNearY () #1 0x083b373c in lyx::TextMetrics::checkInsetHit () #2 0x083fc68f in lyx::BufferView::getCoveringInset () #3 0x083fc6f8 in

  1   2   3   4   5   6   7   8   9   10   >