Bug 374098 - Replace the Maxima entry code with its LaTeX representation
Summary: Replace the Maxima entry code with its LaTeX representation
Status: RESOLVED WORKSFORME
Alias: None
Product: cantor
Classification: Applications
Component: maxima-backend (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR wishlist
Target Milestone: ---
Assignee: Alexander Semke
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-12-23 19:07 UTC by Emmanuel Lepage Vallée
Modified: 2019-07-01 04:33 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Emmanuel Lepage Vallée 2016-12-23 19:07:14 UTC
Hello,

When not being edited, could the entry line be replaced by its LaTeX representation. Maxima has built in support for that. All you have to do is to add "'" in front of the line and evaluate that.

When selected or clicked, it should go back to the string representation. This would make the output much more readable.
Comment 1 Alexander Semke 2018-05-06 13:10:49 UTC
(In reply to Emmanuel Lepage Vallée from comment #0)
> Hello,
> 
> When not being edited, could the entry line be replaced by its LaTeX
> representation. Maxima has built in support for that. All you have to do is
> to add "'" in front of the line and evaluate that.
> 
> When selected or clicked, it should go back to the string representation.
> This would make the output much more readable.
Are you referring here to the input command or to the output produced by maxima?

The latex output was broken and was fixed in 18.04 - with the last release Cantor shows latex output for maxima again. Are you suggesting to switch from the latex rendered image to the string representation if the user clicks on such a latex rendered image?
Comment 2 Nikita Sirgienko 2019-06-01 14:03:29 UTC
Close as inactive for a year
Comment 3 Bug Janitor Service 2019-06-16 04:33:10 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Bug Janitor Service 2019-07-01 04:33:10 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!