cursor advance at start of search if in mathed.
> >
> > Fixes #13070 Advanced S&R does not find math symbols at start of
> > document
>
> I tried cherry-picking this for 2.4.1-devel, but there was a merge
> conflict. So I'll leave it t
On 6/10/24 08:40, Kornel Benko wrote:
commit 8c501308c3c9bf2389275837798ed6c62a9a17bf
Author: Alexander Dunlap
Date: Mon Jun 10 14:42:29 2024 +0200
FindAdv: Omitting cursor advance at start of search if in mathed.
Fixes #13070 Advanced S&R does not find math symbols at s
On 4/12/2023 6:21 am, Richard Kimberly Heck wrote:
On 11/27/23 17:15, Andrew Parsloe wrote:
On 27/11/2023 6:02 pm, Isaac Oscar Gariano wrote:
Personally, I just don't use the |'| in LyX at all, especially as
it doesn't display correctly, and as you show, doesn't combine
properly with other s
On 11/27/23 17:15, Andrew Parsloe wrote:
On 27/11/2023 6:02 pm, Isaac Oscar Gariano wrote:
Personally, I just don't use the |'| in LyX at all, especially as it
doesn't display correctly, and as you show, doesn't combine properly
with other superscripts/subscripts.
Instead, I always do |^\prime
ter).
Andrew
— Isaac Oscar Gariano
*From:* lyx-devel on behalf of
Andrew Parsloe
*Sent:* Monday, 27 November 2023 10:10 AM
*To:* LyX Developers
*Subject:* Primes and superscripts in mathed
TeX accepts S'^{2} (between $ delimiters) a
rime).
— Isaac Oscar Gariano
From: lyx-devel on behalf of Andrew Parsloe
Sent: Monday, 27 November 2023 10:10 AM
To: LyX Developers
Subject: Primes and superscripts in mathed
TeX accepts S'^{2} (between $ delimiters) as a valid construction (TeXbook,
p.130, line above E
ubscript preceding superscript when both are involved
in a symbol? R^{ij}_{kl} in mathed becomes R_{kl}^{ij}, and inserting a
prime as in R'_{kl}^{ij} then produces the double superscript error. In
contrast, R_{kl}'^{ij} does not. TeX accepts the '^ combination and I
think mathed
On Wed, Nov 08, 2023 at 08:31:23AM +0100, Enrico Forestieri wrote:
> >These will not get distributed to tarball unless added to makefiles.
>
> Adding them to src/Makefile.am is not sufficient?
It is, I didn't see it in the diff, athough I see it now :) Sorry. Pavel
--
lyx-devel mailing list
lyx-
On Tue, Nov 07, 2023 at 04:33:49PM +0100, Pavel Sanda wrote:
On Mon, Nov 06, 2023 at 04:55:31PM +0100, Enrico Forestieri wrote:
commit 58103cf214cc5e9e5d0f4aaa03f4250ee011e55a
Author: Enrico Forestieri
Date: Mon Nov 6 18:04:44 2023 +0100
Allow using the text properties dialog in mathed
On Mon, Nov 06, 2023 at 04:55:31PM +0100, Enrico Forestieri wrote:
> commit 58103cf214cc5e9e5d0f4aaa03f4250ee011e55a
> Author: Enrico Forestieri
> Date: Mon Nov 6 18:04:44 2023 +0100
>
> Allow using the text properties dialog in mathed
>
> Until now only
articular, instead of typing \neq in mathed, why not copy and paste
a ≠ from some PDF or HTML page?
When doing this, two things happen :
1/ on screen, there is no spacing around the ≠
2/ in LaTeX output, the character is exported as \neq and all is well
This nice behaviour doesn'
Le 30/05/2023 à 00:37, Jean-Marc Lasgouttes a écrit :
Thanks for your input, this is the direction I would take if I ever find
the time to solve this issue.
This is now ticket #12788.
https://www.lyx.org/trac/ticket/12788
JMarc
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx
Le 30/05/2023 à 00:14, Udicoudco a écrit :
So how should I solve problem 1/ ? I see 3 solutions
a/ replace ≠ with a \neq directly in the document at input time; we
might not want to do that in case we eventually use unicode in math too
b/ replace ≠ with a \neq on screen only
c/ keep the ≠ on scre
On Sat, Apr 1, 2023 at 4:10 PM Jean-Marc Lasgouttes wrote:
> In particular, instead of typing \neq in mathed, why not copy and paste
> a ≠ from some PDF or HTML page?
>
> When doing this, two things happen :
> 1/ on screen, there is no spacing around the ≠
> 2/ in LaTeX output
Am Thu, 13 Apr 2023 16:57:27 +0200
schrieb Jean-Marc Lasgouttes :
> Le 13/04/2023 à 16:29, Kornel Benko a écrit :
> > Would be nice to have a list of these math-commands which can map to
> > unicode. (Not all
> > are in file unicodesymbols). This is important for advanced find too.
>
> And in
Le 13/04/2023 à 16:29, Kornel Benko a écrit :
Would be nice to have a list of these math-commands which can map to unicode.
(Not all
are in file unicodesymbols). This is important for advanced find too.
And in lib/symbols ?
JMarc
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists
Am Thu, 6 Apr 2023 10:43:42 +0200
schrieb Jean-Marc Lasgouttes :
> Le 03/04/2023 à 00:36, Enrico Forestieri a écrit :
> >> So how should I solve problem 1/ ? I see 3 solutions
> >> a/ replace ≠ with a \neq directly in the document at input time; we
> >> might not want to do that in case we eventu
Le 03/04/2023 à 00:36, Enrico Forestieri a écrit :
So how should I solve problem 1/ ? I see 3 solutions
a/ replace ≠ with a \neq directly in the document at input time; we
might not want to do that in case we eventually use unicode in math too
b/ replace ≠ with a \neq on screen only
c/ keep the
On Sat, Apr 01, 2023 at 03:09:58PM +0200, Jean-Marc Lasgouttes wrote:
Hello,
A relative has been using LyX recently, and it is interesting to see
how the use is different from what I would do.
In particular, instead of typing \neq in mathed, why not copy and
paste a ≠ from some PDF or HTML
On Sat, Apr 01, 2023 at 09:13:22PM +0200, Jean-Marc Lasgouttes wrote:
> Le 01/04/2023 à 20:57, Scott Kostyshak a écrit :
> > On Sat, Apr 01, 2023 at 03:09:58PM +0200, Jean-Marc Lasgouttes wrote:
> > Would another possibility be to prompt the user? I'm not sure what a
> > friendly prompt would be t
Le 01/04/2023 à 20:57, Scott Kostyshak a écrit :
On Sat, Apr 01, 2023 at 03:09:58PM +0200, Jean-Marc Lasgouttes wrote:
Would another possibility be to prompt the user? I'm not sure what a friendly
prompt would be though since many LyX users do not know what unicode is. I
could try to work on so
On Sat, Apr 01, 2023 at 03:09:58PM +0200, Jean-Marc Lasgouttes wrote:
> Hello,
>
> A relative has been using LyX recently, and it is interesting to see how the
> use is different from what I would do.
>
> In particular, instead of typing \neq in mathed, why not copy and paste a
Hello,
A relative has been using LyX recently, and it is interesting to see how
the use is different from what I would do.
In particular, instead of typing \neq in mathed, why not copy and paste
a ≠ from some PDF or HTML page?
When doing this, two things happen :
1/ on screen, there is no
On Mon, Feb 08, 2021 at 02:23:38PM +0100, Jean-Marc Lasgouttes wrote:
> Le 07/02/2021 à 17:42, Enrico Forestieri a écrit :
> > It's InsetArgumentProxy that is returning MC_UNKNOWN.
>
> Fixed at c3114515180d. I am not sure though what this code is doing: when
> creating the color inset, there is no
Le 07/02/2021 à 17:42, Enrico Forestieri a écrit :
It's InsetArgumentProxy that is returning MC_UNKNOWN.
Fixed at c3114515180d. I am not sure though what this code is doing:
when creating the color inset, there is no \mathxxx anywhere, but they
are introduced when writing back the .lyx file,
On Sun, Feb 07, 2021 at 09:37:57AM +0100, Enrico Forestieri wrote:
> On Sat, Feb 06, 2021 at 11:06:41PM -0500, Scott Kostyshak wrote:
> > I see an assertion on master that I think started happening with this
> > commit.
> >
> > Here's the assertion:
> > ASSERTION false VIOLATED IN
> > /home/scot
On Sun, Feb 07, 2021 at 01:06:15PM +0100, Jean-Marc Lasgouttes wrote:
> Le 07/02/2021 à 09:37, Enrico Forestieri a écrit :
> > On Sat, Feb 06, 2021 at 11:06:41PM -0500, Scott Kostyshak wrote:
> > > I see an assertion on master that I think started happening with this
> > > commit.
> > >
> > > Her
Le 07/02/2021 à 09:37, Enrico Forestieri a écrit :
On Sat, Feb 06, 2021 at 11:06:41PM -0500, Scott Kostyshak wrote:
I see an assertion on master that I think started happening with this commit.
Here's the assertion:
ASSERTION false VIOLATED IN
/home/scott/lyxbuilds/master/repo/src/mathed/MathC
On Sat, Feb 06, 2021 at 11:06:41PM -0500, Scott Kostyshak wrote:
> I see an assertion on master that I think started happening with this commit.
>
> Here's the assertion:
> ASSERTION false VIOLATED IN
> /home/scott/lyxbuilds/master/repo/src/mathed/MathClass.cpp:59
>
> The assertion happens when
On Sun, Aug 02, 2020 at 06:38:06PM +0200, Enrico Forestieri wrote:
> commit 7441172d4d9a26eb4824bb8bee003f457ef34f1c
> Author: Enrico Forestieri
> Date: Sun Aug 2 18:58:40 2020 +0200
>
> Assure correct spacing of colored items in mathed
>
> When coloring a n
On 2/4/21 3:20 PM, Enrico Forestieri wrote:
commit 8202e4e571b90b3b87918437d6346bbf1cbfc6aa
Author: Enrico Forestieri
Date: Thu Feb 4 21:20:45 2021 +0100
Disable direct insertion of multiple spaces in mathed text
Fixes #1311
An old one!
Riki
--
lyx-devel mailing list
lyx
On 26/07/2019 8:41 PM, Richard Kimberly Heck wrote:
On 7/26/19 12:46 AM, Daniel wrote:
On 2019-07-25 23:40, Andrew Parsloe wrote:
I can create a crash by trying to delete the final column in the
following construction:
\begin{align*}
\begin{aligned}\end{aligned}
\\
\end{align*}
To create
On 7/26/19 12:46 AM, Daniel wrote:
> On 2019-07-25 23:40, Andrew Parsloe wrote:
>> I can create a crash by trying to delete the final column in the
>> following construction:
>>
>>
>> \begin{align*}
>>
>> \begin{aligned}\end{aligned}
>>
>> \\
>>
>> \end{align*}
>>
>>
>> To create:
>>
>>
>> 1. Ctrl+
On 2019-07-25 23:40, Andrew Parsloe wrote:
I can create a crash by trying to delete the final column in the
following construction:
\begin{align*}
\begin{aligned}\end{aligned}
\\
\end{align*}
To create:
1. Ctrl+Shift+M to create a display math equation.
2. Ctrl+Return to create an alig
I can create a crash by trying to delete the final column in the
following construction:
\begin{align*}
\begin{aligned}\end{aligned}
\\
\end{align*}
To create:
1. Ctrl+Shift+M to create a display math equation.
2. Ctrl+Return to create an align* environment
3. Insert > Math > Aligned E
values. This value is used in mathed since 03a4b8c9328.
So, am I the only one seeing this (it is not present in windows)?
Actually this is font-dependent. I see this with DejaVu Serif, but not
other fonts. It seems this this font for some reason is not adapted for
use in mathed.
Let's sa
Now that I compile LyX with Qt5 by default on some of my computers, I
see that, in linux, characters are annoyingly spaced (see attachments)
with Qt5, but not Qt4.
I traced this back to QFontMetrics::rightBearing which returns different
values. This value is used in mathed since 03a4b8c9328
Jean-Marc Lasgouttes wrote:
>>> Pavel, please test this new code. It should get the cursor size right
>>> without crashing of changing bizarrely the current font.
>>>
>>> Riki, if this works, I will probably propose to backport to 2.3.2.
>> Any chance you would provide 2.3 patch? Anything in master
Le 27/04/2018 à 11:35, Pavel Sanda a écrit :
Jean-Marc Lasgouttes wrote:
Le 27/04/2018 ?? 00:13, Jean-Marc Lasgouttes a écrit :
commit 90cfe4ec3b4ff22ef798a63e98ca70d0d33a1656
Author: Jean-Marc Lasgouttes
Date: Fri Apr 27 00:03:48 2018 +0200
Adapt caret height to context in mathed
Le 27/04/2018 à 13:17, Pavel Sanda a écrit :
Clearly you prefer to think in a systematic way.
That might be good for the code, but what will remain for all the
procrastinating
hackers in the future who will be left without the mystery where the b came
from?
The good side is that we have plent
Jean-Marc Lasgouttes wrote:
>> I was refering merely to caret height; but we are getting to nitpicking,
>> meaning the situation is likely good enough for now :)
>
> Currently, the caret is never higher than the cell it is in. This is why I
> argue that the cell is too small.
Clearly you prefer t
Le 27/04/2018 à 12:38, Pavel Sanda a écrit :
Jean-Marc Lasgouttes wrote:
Le 27/04/2018 ?? 11:47, Pavel Sanda a écrit :
Limited testing shows no crash. As said previously cursor is much better
now,
though I would suggest use of 'b' instead of 'x' min height, e.g. try
&q
Jean-Marc Lasgouttes wrote:
> Le 27/04/2018 ?? 11:47, Pavel Sanda a écrit :
>> Limited testing shows no crash. As said previously cursor is much better
>> now,
>> though I would suggest use of 'b' instead of 'x' min height, e.g. try
>> "\dot
Le 27/04/2018 à 11:47, Pavel Sanda a écrit :
Limited testing shows no crash. As said previously cursor is much better now,
though I would suggest use of 'b' instead of 'x' min height, e.g. try "\dot u"
in mathed and compare both versions.
Note that, whil
Jean-Marc Lasgouttes wrote:
> Le 27/04/2018 ?? 00:13, Jean-Marc Lasgouttes a écrit :
>> commit 90cfe4ec3b4ff22ef798a63e98ca70d0d33a1656
>> Author: Jean-Marc Lasgouttes
>> Date: Fri Apr 27 00:03:48 2018 +0200
>> Adapt caret height to context in mathed.
>>
Jean-Marc Lasgouttes wrote:
> Le 27/04/2018 ?? 00:13, Jean-Marc Lasgouttes a écrit :
>> commit 90cfe4ec3b4ff22ef798a63e98ca70d0d33a1656
>> Author: Jean-Marc Lasgouttes
>> Date: Fri Apr 27 00:03:48 2018 +0200
>> Adapt caret height to context in mathed.
>>
On 04/26/2018 06:17 PM, Jean-Marc Lasgouttes wrote:
> Le 27/04/2018 à 00:13, Jean-Marc Lasgouttes a écrit :
>> commit 90cfe4ec3b4ff22ef798a63e98ca70d0d33a1656
>> Author: Jean-Marc Lasgouttes
>> Date: Fri Apr 27 00:03:48 2018 +0200
>>
>> Adapt
Le 27/04/2018 à 00:13, Jean-Marc Lasgouttes a écrit :
commit 90cfe4ec3b4ff22ef798a63e98ca70d0d33a1656
Author: Jean-Marc Lasgouttes
Date: Fri Apr 27 00:03:48 2018 +0200
Adapt caret height to context in mathed.
Compute a height from current font and current cell vertical
Ok, I see now. I've seen bigger dots in macOS screenshot and zoomed the doc.
But with normal zoom it looks definitely better than before (still not
as big as on your Linux screenshot). Thanks for the patch.
On 14.03.2018 15:01, Pavel Sanda wrote:
> No, this is as expected :)
>
> Many of our math
Yuriy Skalko wrote:
> Seems like it doesn't work as expected. Am I missing something?
No, this is as expected :)
Many of our math decorations (painted through the machinery of deco_table) does
not zoom with the font, so if you increase font size to gigantic proportions it
looks as in your exampl
Seems like it doesn't work as expected. Am I missing something?
On 13.03.2018 10:03, Pavel Sanda wrote:
> Anyone can show windows situation?
>
> Pavel
Scott Kostyshak wrote:
> On Tue, Mar 13, 2018 at 12:27:58AM +, Joel Kulesza wrote:
> > On Fri, Mar 9, 2018 at 10:57 AM, Pavel Sanda wrote:
> >
> > > Whether now, or after it's committed I would appreciate testing from
> > > someone
> > > sitting on Win and Mac(?Retina) machine to check whethe
On Tue, Mar 13, 2018 at 12:27:58AM +, Joel Kulesza wrote:
> On Fri, Mar 9, 2018 at 10:57 AM, Pavel Sanda wrote:
>
> > Whether now, or after it's committed I would appreciate testing from
> > someone
> > sitting on Win and Mac(?Retina) machine to check whether they see what I
> > see
> > on li
On Fri, Mar 9, 2018 at 10:57 AM, Pavel Sanda wrote:
> Whether now, or after it's committed I would appreciate testing from
> someone
> sitting on Win and Mac(?Retina) machine to check whether they see what I
> see
> on linux for \dot and \ddot, i.e. the second attachment.
Looks good on a Mac Re
Scott Kostyshak wrote:
> > > > You mean zoom-in changes the visual appearance for \dot in your
> > > > environemnt?
> > > > It does not change a single pixel here. Do you use linux?
> > >
> > > I have the same behavior as you, I think: \dot doesn't change at all
> > > with zoom. \ddots does.
> >
On Fri, Mar 09, 2018 at 05:57:01PM +, Pavel Sanda wrote:
> Scott Kostyshak wrote:
> > > > > > I've seen this in the past also, but only at high zoom levels.
> > > > >
> > > > > In other words, when you put \dot in mathed you see dot?
Scott Kostyshak wrote:
> > > > > I've seen this in the past also, but only at high zoom levels.
> > > >
> > > > In other words, when you put \dot in mathed you see dot?
> > >
> > > For that one, I can indeed see that the dot is not a
On Thu, Mar 08, 2018 at 11:16:02PM +, Pavel Sanda wrote:
> Scott Kostyshak wrote:
> > > > I've seen this in the past also, but only at high zoom levels.
> > >
> > > In other words, when you put \dot in mathed you see dot?
> >
> > For that
Jean-Marc Lasgouttes wrote:
> Le 08/03/2018 ? 18:18, Pavel Sanda a écrit :
>> am I the only one who sees that we paint lines instead of dots
>> for \dots, \ddots, \dddots etc. in mathed?
>> The fix seems to be so trivial that I wonder whether I am missing
>> something?
Scott Kostyshak wrote:
> > > I've seen this in the past also, but only at high zoom levels.
> >
> > In other words, when you put \dot in mathed you see dot?
>
> For that one, I can indeed see that the dot is not a dot at low zoom
> levels as well.
You mean zo
On Thu, Mar 08, 2018 at 05:35:25PM +, Pavel Sanda wrote:
> Scott Kostyshak wrote:
> > > am I the only one who sees that we paint lines instead of dots
> > > for \dots, \ddots, \dddots etc. in mathed?
> >
> > I've seen this in the past also, but only at
Le 08/03/2018 à 18:18, Pavel Sanda a écrit :
Hi,
am I the only one who sees that we paint lines instead of dots
for \dots, \ddots, \dddots etc. in mathed?
The fix seems to be so trivial that I wonder whether I am missing something?
Attached is the fix (two short lines make it to something
Scott Kostyshak wrote:
> > am I the only one who sees that we paint lines instead of dots
> > for \dots, \ddots, \dddots etc. in mathed?
>
> I've seen this in the past also, but only at high zoom levels.
In other words, when you put \dot in mathed you see dot?
This is w
On Thu, Mar 08, 2018 at 05:18:47PM +, Pavel Sanda wrote:
> Hi,
>
> am I the only one who sees that we paint lines instead of dots
> for \dots, \ddots, \dddots etc. in mathed?
I've seen this in the past also, but only at high zoom levels.
Scott
signature.asc
Description: PGP signature
Hi,
am I the only one who sees that we paint lines instead of dots
for \dots, \ddots, \dddots etc. in mathed?
The fix seems to be so trivial that I wonder whether I am missing something?
Attached is the fix (two short lines make it to something which looks like
a dot).
Attached is the solutions
Le 23/06/2017 à 20:38, Jean-Marc Lasgouttes a écrit :
Le 20/06/2017 à 23:31, Guillaume MM a écrit :
Hi Jean-Marc,
There is the case of InsetMathRef which has nargs()!=0 but whose cell
is not active. See e.g. the fix at 7337c968. Is the logic still valid
in this case? Just in case.
Hi Guilla
o strong and broke mathed, d0acc3e57044 is too
lenient and can accept insets (mathed/CommandInset, InsetInfo) that
have a positive nargs() but are not editable (because they encapsulate
something).
Therefore the best solution for now is to use editable() in text and
isActive() in mathed, until t
Le 20/06/2017 à 23:31, Guillaume MM a écrit :
Hi Jean-Marc,
There is the case of InsetMathRef which has nargs()!=0 but whose cell is
not active. See e.g. the fix at 7337c968. Is the logic still valid in
this case? Just in case.
Very good point. Sigh. The good solution would be a careful merg
d0acc3e570447b293169b8bdd5ac67aaade189e0
Author: Jean-Marc Lasgouttes
Date: Tue Jun 20 09:41:48 2017 +0200
Fixup 522516d9 : editable() is unusable in mathed
This is a relic from IU (Inset Unification): editable() is for text
insets and isActive() for mathed. This needs to be cleaned up.
Part of
On Sun, Sep 25, 2016 at 01:33:38AM +0200, Enrico Forestieri wrote:
> On Thu, Sep 22, 2016 at 01:07:28PM +, Guenter Milde wrote:
>
> > Unit symbols wrong when using a fraction in \text:
> >
> > \begin_inset Formula $50\,\text{\frac{m}{s}}$
> > \end_inset
> >
> > exported as
> >
> > $50\,\
On Thu, Sep 22, 2016 at 01:07:28PM +, Guenter Milde wrote:
>
> It still fails for \textdegree:
>
> - \textdegree in math-mode input as-is
> - \textdegree in "mathematical text" wrapped in \ensuremath{}
This is because the MathMacro class was missing a currentMode method.
Fixed at 314e30d
On 2016-09-21, Guillaume Munch wrote:
> Le 19/09/2016 à 11:58, Enrico Forestieri a écrit :
>> When inserting a command or symbol in mathed, it is now automatically
>> wrapped in a real inset (either \text or \ensuremath) assuring the correct
>> mode, instead of being wrapp
Le 19/09/2016 à 11:58, Enrico Forestieri a écrit :
commit d0f608d28ebeabadc8308f408f2a67980da8e73c
Author: Enrico Forestieri
Date: Mon Sep 19 11:57:39 2016 +0200
Document the new behaviour in mathed
---
lib/RELEASE-NOTES | 12 +---
1 files changed, 9 insertions(+), 3 deletions
Le 17/09/2015 06:06, Andrew Parsloe a écrit :
LyX doesn't handle nested braces correctly. In a maths inset write {
{1234 } } so that the outer pair of braces contains a single argument.
Now save and close the document, then reopen it and the maths inset will
contain { 1234 } i.e. 4 tokens rather
Andrew Parsloe wrote:
> LyX doesn't handle nested braces correctly. In a maths inset write {
> {1234 } } so that the outer pair of braces contains a single argument.
> Now save and close the document, then reopen it and the maths inset will
> contain { 1234 } i.e. 4 tokens rather than the single a
LyX doesn't handle nested braces correctly. In a maths inset write {
{1234 } } so that the outer pair of braces contains a single argument.
Now save and close the document, then reopen it and the maths inset will
contain { 1234 } i.e. 4 tokens rather than the single argument grouping
before. De
On 09/10/2011 10:27 AM, Jürgen Spitzmüller wrote:
> Richard Heck wrote:
>> Branch, too, I would suppose, as this makes the behavior consistent with
>> previous behavior.
> OK, done. Please remember to remove respective release notes again (I did not
> find anything in SVN).
>
Hadn't committed yet.
Richard Heck wrote:
> Branch, too, I would suppose, as this makes the behavior consistent with
> previous behavior.
OK, done. Please remember to remove respective release notes again (I did not
find anything in SVN).
Jürgen
On 09/10/2011 01:35 AM, Jürgen Spitzmüller wrote:
> Guenter Milde wrote:
>>> So the attached patch would be what you request. Shall I put this in?
>> Looks fine to me:
> I've committed to trunk. What about branch?
>
Branch, too, I would suppose, as this makes the behavior consistent with
previous
Guenter Milde wrote:
> > So the attached patch would be what you request. Shall I put this in?
>
> Looks fine to me:
I've committed to trunk. What about branch?
Jürgen
On 2011-09-09, Jürgen Spitzmüller wrote:
> [-- Type: text/plain, Encoding: quoted-printable --]
> Jürgen Spitzmüller wrote:
>> > I don't know what the lfun for this "toggleable math space" is
>> me neither.
> math-space.
> So the attached patch would be what you request. Shall I put this in?
Jürgen Spitzmüller wrote:
> > I don't know what the lfun for this "toggleable math space" is
>
> me neither.
math-space.
So the attached patch would be what you request. Shall I put this in?
JürgenIndex: lib/bind/cua.bind
===
--- l
Guenter Milde wrote:
> I don't know what the lfun for this "toggleable math space" is
me neither.
Jürgen
On 2011-09-08, Richard Heck wrote:
> On 09/08/2011 09:37 AM, Pavel Sanda wrote:
>> Jürgen Spitzmüller wrote:
>>> Jürgen Spitzmüller wrote:
The lfun resulted in a thin space as a fall back (which has
Ctlr-Alt-Space),
>>> That is: Ctrl-Shift-Space
However, the math space can (could) be tog
On 09/08/2011 09:37 AM, Pavel Sanda wrote:
> Jürgen Spitzmüller wrote:
>> Jürgen Spitzmüller wrote:
>>> The lfun resulted in a thin space as a fall back (which has
>>> Ctlr-Alt-Space),
>> That is: Ctrl-Shift-Space
> ahh this works! thanks, i think this should be put into release notes of
> 2.0.2.
Jürgen Spitzmüller wrote:
> Jürgen Spitzmüller wrote:
> > The lfun resulted in a thin space as a fall back (which has
> > Ctlr-Alt-Space),
>
> That is: Ctrl-Shift-Space
ahh this works! thanks, i think this should be put into release notes of 2.0.2.
pavel
Jürgen Spitzmüller wrote:
> If you insist on having thin space back with Cltr-space in mathed, this
> should
> be implemented via command-alternatives.
i find the new behaviour quite frustrating the more it was introduced in branch
which should be considered as safe place t
Jürgen Spitzmüller wrote:
> The lfun resulted in a thin space as a fall back (which has
> Ctlr-Alt-Space),
That is: Ctrl-Shift-Space
> which is probably what you miss. However, it was clearly
> that the protected space menu item inserts a thin space.
it was clearly _a bug_.
Jürgen
ntentional. Ctlr-space is bound to "inset-space protected", and
this kind of space is not supported in mathed. The lfun had to be disabled,
because the protected space menu item in inset formatting needs to be disabled
in mathed.
The lfun resulted in a thin space as a fall back (w
hi,
it seems that in current branch i'm no more able to use ctrl+space in
displayed equations, ouch.
i'm very busy with my real work atm to investigate, but i remember
some related thread recently. this regression was intentional?
pavel
> objections?
none, I think it is safe since you only insert an existing mathed inset.
regards Uwe
hi,
i would like to put the patch originally written by Georg into the trunk,
see http://www.lyx.org/trac/ticket/2045. as stated in the bug there are
some issue (which i didnt reproduce now), but anyway its with this fix
better than the current state.
objections?
pavel
diff --git a/src/mathed/In
Abdelrazak Younes writes:
> Looks good. And the initial misbehaviour is probably my fault.
I applied it, then. What I have to check now is what happens when a cell
is created (inset array row...).
> I remember fixing one last week-end.
I saw that too.
JMarc
Jean-Marc Lasgouttes wrote:
Hi,
The following patch should fix many/most of the buffer missettings in
mathed.
Looks good. And the initial misbehaviour is probably my fault.
However, I did not keep trace of the ways to trigger a null
buffer assertion with trunk. Could somebody refresh my
Hi,
The following patch should fix many/most of the buffer missettings in
mathed. However, I did not keep trace of the ways to trigger a null
buffer assertion with trunk. Could somebody refresh my memory?
JMarc
svndiff
Index: src/mathed/InsetMathHull.cpp
/show_bug.cgi?id=5269
I looked in the code but don't understand how the handling of \color work in
mathed.
regards Uwe
Andre Poenitz wrote:
You want to do that for all math insets?
>
> I don't think that'd be a desirable solution.
the only thing i want to do is to have selections drawn correctly, that
is: selection color background, highlighted text color foreground
I know that the current way to paint sele
On Sun, Mar 30, 2008 at 02:17:54PM +0200, Edwin Leuven wrote:
> as the subject says, i am trying to change the color of selected text in
> mathed
> attached the approach thing i am taking atm, which basically amounts to
> checking whether an element is spanned by a selection and
as the subject says, i am trying to change the color of selected text in
mathed
attached the approach thing i am taking atm, which basically amounts to
checking whether an element is spanned by a selection and changing the
font color if appropriate.
i have some questions for those of you
On Mon, Feb 11, 2008 at 08:51:53AM +0100, Abdelrazak Younes wrote:
> Dominik Böhm wrote:
>> Hello again,
>> bug that makes lyx crash.
>> I was able to reproduce one critical
>> Create a new file, insert one section at the beginning and then a formula
>> with a matrix (it doesn't matter if it's an
1 - 100 of 430 matches
Mail list logo
