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
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
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.
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
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
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
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
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
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.
I think this is crucial to implement syntax highlighting of ERT box.
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
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
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.
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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()
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()
Could anyone that has an opinion on this subject please have a look at
bug 8514 ?
http://www.lyx.org/trac/ticket/8514
Vincent
Could anyone that has an opinion on this subject please have a look at
bug 8514 ?
http://www.lyx.org/trac/ticket/8514
Vincent
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
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
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
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
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
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
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
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
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
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
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
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
(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
(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
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
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
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
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
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
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
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
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
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
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
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
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
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]
>
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
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
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
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
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,
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
.
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
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
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
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
...
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
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
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 - 100 of 1278 matches
Mail list logo