11

The notebook interface and the kernel have different parsers, because the notebook needs to manipulate the input before the kernel sees it for a variety of reasons. There are many differences between the two parsers. It has not been a priority to Wolfram to fix the differences. I have been trying to catalog the differences here (rendered as a webpage here)....


8

I suspect, much to my chagrin, that the FE is right and the InputForm parser is wrong. For one thing, the kernel itself thinks that parens are needed for Repeated: Repeated[Pattern[x,Blank[]]]//InputForm (*(x_)..*) The reason it breaks in the FE is that the FE treats the x_. as a single token: RowBox[{"x_.", "."}]. And that's absolutely correct: see ...


5

I am going to answer this from an experienced software developer's perspective. Wolfram is written to support a number of platforms and processor architectures. The widgets that you see on the front end are usually third party additions, e.g. QT, but Wolfram may well be using their own. However, these widgets do try to be compatible with most systems, and ...


4

(feel free to contribute) Using the Mathematica front-end efficiently for editing notebooks Adding new shortcuts / menu items / events: How can I set a keyboard shortcut to run a command? Further examples in search results for KeyEventTranslations.tr UserBase vs InstallationDirectory for modified resources External solutions Shortcuts`, package with ...


2

I reported this as a bug to support ~8 months ago and then logged it again in Redmine about 7 months ago (Bug #132) - it was one of the first things I noticed in 12.0's release. It was also documented on Wolfram Community around the same time. The work-around is pretty unsatisfactory - basically save, close the notebook, open and then laboriously ...


Only top voted, non community-wiki answers of a minimum length are eligible