GNU TeXmacs - Bugs: bug #62850, Crash on highlighting movement in...
You are not allowed to post comments on this tracker with your current authentication level.
bug #62850: Crash on highlighting movement in macro definition
Submitter: | Gennady Uraltsev <guraltsev> | ||
Submitted: | Mon 01 Aug 2022 04:10:05 PM UTC | ||
Category: | Editor | Priority: | 5 - Normal |
Item Group: | Error | Status: | Confirmed |
Privacy: | Public | Assigned to: | None |
Originator Name: | Open/Closed: | Open | |
Release: | None | Release: | 2.1.1 |
Fixed Release: | None | Fixed Release: | |
Keywords: |
Thu 05 Jan 2023 07:33:06 PM UTC, comment #3: |
Philippe Joyez <pjoyez> |
Wed 10 Aug 2022 05:46:01 PM UTC, comment #2: Somehow the row calculation is off. The `row` argument to `table_search_cell`, the function where the error occurs equals 86913880, which is obviously far outside the table in question. |
Jeroen Wouters <jeronim> |
Wed 10 Aug 2022 05:39:44 PM UTC, comment #1: I get an error `Throwing path is too short`. The debugger says the error happens on line `src/Data/Tree/tree_select.cpp:321`, "t= t [row];" |
Jeroen Wouters <jeronim> |
Mon 01 Aug 2022 04:10:05 PM UTC, original submission:
I defined a table-based macro in my preamble. It works perfectly well, but TeXmacs crashes when trying to select a piece of code with the keyboard or with the mouse (I am talking about the actual definition code in the preamble).
|
Gennady Uraltsev <guraltsev> |
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 3 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2022-08-07 | jeronim | Item Group | None | Error | |
Status | None | Confirmed | |||
2022-08-01 | guraltsev | Attached File | - | Added crash-on-tabledef.tm, #53498 |
Powered by Savane 3.13-f8d8.
Corresponding source code
The crash can be prevented by changing the first test in edit_select_rep::compute_selection
if (is_table_selection (et, p1, p2, true)) {
->
if (!in_source () && is_table_selection (et, p1, p2, true)) {
but it's just a ad hoc change for this bug and a broader perspective on the code is probably needed. Also I find it surprising the bug does not occur more systematically when working with tables in source mode.