Re: Regression when copying a multirow row in table
On Fri, Apr 07, 2023 at 10:33:37AM +1200, Andrew Parsloe wrote: > I'm using Version 2.4.0-beta2 on windows 10. > > In the attached mwe if you copy the entire row, say with the cursor to the > right of c then sweep to the left to include the cells with a and b, and > press Ctrl+C (or click the copy button), LyX crashes. This does not happen > in 2.3.7. > > I had a multirow table and, after I had added some other entries, wished to > transfer such a row to a lower postion in the table by cutting and pasting. > The emergency recover system worked well, but this doesn't feel like a > corner case to me. Nice catch, Andrew! I can reproduce, and git bisect leads here: commit 5cb89a8f818537cf997625c7c7fd7b5399a677a6 Author: Juergen Spitzmueller Date: Mon Jun 29 15:13:45 2020 +0200 Implement proper pasting from multiple table cells to non-table (#4447) Scott signature.asc Description: PGP signature -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Regression when copying a multirow row in table
I don't see this crash (but I had to change lyxformat from 614 to 613 in order to read the file, even though I'm using 2.4.0-beta2) Version 2.4.0-beta2 (Sunday, December 11, 2022) Qt Version (run-time): 6.4.1 on platform cocoa Qt Version (compile-time): 6.4.1 OS Version (run-time): macOS Monterey (12.6) Python detected: python3 -tt John On Thu, Apr 6, 2023 at 3:34 PM Andrew Parsloe wrote: > I'm using Version 2.4.0-beta2 on windows 10. > > In the attached mwe if you copy the entire row, say with the cursor to the > right of c then sweep to the left to include the cells with a and b, and > press Ctrl+C (or click the copy button), LyX crashes. This does not happen > in 2.3.7. > > I had a multirow table and, after I had added some other entries, wished > to transfer such a row to a lower postion in the table by cutting and > pasting. The emergency recover system worked well, but this doesn't feel > like a corner case to me. > > Andrew > -- > lyx-devel mailing list > lyx-devel@lists.lyx.org > http://lists.lyx.org/mailman/listinfo/lyx-devel > -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Regression when copying a multirow row in table
I'm using Version 2.4.0-beta2 on windows 10. In the attached mwe if you copy the entire row, say with the cursor to the right of c then sweep to the left to include the cells with a and b, and press Ctrl+C (or click the copy button), LyX crashes. This does not happen in 2.3.7. I had a multirow table and, after I had added some other entries, wished to transfer such a row to a lower postion in the table by cutting and pasting. The emergency recover system worked well, but this doesn't feel like a corner case to me. Andrew CopyMultirow.lyx Description: application/lyx -- lyx-devel mailing list lyx-devel@lists.lyx.org http://lists.lyx.org/mailman/listinfo/lyx-devel
Re: Unicode characters in mathed
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 screen, but use the mathrel math class from \neq so
that we have a good spacing
I would say (a) but only for symbols that are actually translated in
output.
What I wonder is whether keeping the unicode characters in the document
could be helpful (for html/docbook export, for example) and avoid
overrriding users actions. I think I will try b/ first, until I have
other people (Günther, do you read this?) tell me that I can get rid of
unicode keys early.
Also, things like ² are translated to more complex commands like {}^2, I
am not sure that I want to insert it with an editable nucleus.
Then, I see that there are two ways of matching \neq to U+2260:
i/ lib/unicodesymbol has a "mathcommand" entry for that (which is
presumably used right now)
ii/ lib/symbols also links these elements
Which one is more reliable for what I want to do?
As I see it, (i) is for export and (ii) is for screen representation, so
I would suggest using (i).
Right.
My general problem is that, while I see what happens with \neq, I
suspect that many weird things can happen with other characters.
Any advice?
Be careful ;)
Indeed. This is probably not 2.4 material anyway, unless it turns out to
be very easy to implement.
JMarc
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
