9

Type > at the start of a cell (or when between cells). This is documented in an example on ref/ExternalEvaluate (last Basic Example). I'm a bit suprised it's not in the details section. It probably should be...


7

There is too much burden attached to working with KeyEvenTranslations.tr so I rarely use it. You can try an alternative: DevTools`:NotebookActions: ResourceFunction["GitHubInstall"]["kubapod", "devtools"] Needs @ "DevTools`"; NotebookActionsEnable[]; EditNotebookActions[]; add a cell with: <| "Label" -> "ClearCell" , "ShortKey" -> "c" , "...


5

Why not use an InputAutoReplacements instead? For example: CurrentValue[EvaluationNotebook[], {InputAutoReplacements, "ww"}] = "Ω" Then you can type: w w Control+- to enter the desired subscript. If you really want to use KeyEventTranslations.tr to do this, then you need to enter boxes: Item[KeyEvent["O", Modifiers -> {Control, Command, Shift}], ...


5

The option StyleKeyMapping controls "Tab" and "Backspace" does to the style (AFAIK, it is not documented). Row[Table[Most@NestWhileList["Tab" /. CurrentValue[{StyleDefinitions, #, StyleKeyMapping}]&, i, Not[StringMatchQ[#, "Tab"]] &] // Column[Style[#, #] & /@ #] &, {i, {"Chapter", "Title", "Section", "Item", "ItemParagraph", "...


4

Rephrasing comments: It's an ASCII BEL (bell) control code character. Teletypes and at least some computers had a physical, solenoid-driven electric bell in them up to like early eighties, as it was probably the technically cheapest way to implement an audio indication those days. They were pretty much the same technology as bells used on rotary dial phones ...


4

The key option is Scope -> SelectionCell. So, you can either modify the menu item in MenuSetup.tr to: MenuItem[ "Align Center", TextAlignment -> Center, Scope -> SelectionCell, MenuKey["c", Modifiers -> {"Command", "Option"}] ] or you can add a KeyEvent to KeyEventTranslations.tr: Item[ KeyEvent["c", Modifiers->{Command, ...


4

There is no support for 2D style input yet. However, after you type it in 1D, you can click the gear icon next to the cell bracket and "convert to traditional form" like this: Which converts it to look like this:


2

Goto C:\.....\Mathematica\System Files\Front End\TextResources\Windows Open the file: KeyEventTranslations.tr Locate line 11 of this file: Item[KeyEvent["KeypadEnter", Modifiers -> {Shift}], "EvaluateNextCell"], Change this line to: Item[KeyEvent["KeypadEnter", Modifiers -> {Shift}], "EvaluateNoteBook"], Save and restart Mathematica. After making ...


2

How we can do this: We will make an automated parser for these modifications, as stated! Let's see what we have here, shall we? The Answer: Mathematica is very powerful if used correctly and consise-ish-ly. So, as we can for many other things, we can programmatically generate these modifications like you will find below, noting that one would simply ...


1

1) This is a preexisting bug. It's slightly worse in V12 because it's inserting a null byte rather than a control character, and that null byte doesn't seem interceptable. 2) This isn't specific to the touch bar. The same thing happens with an external keyboard. 3) I presume you're noticing this because, like me, you have the touchbar set to show function ...


1

Note that both MenuSetup.tr and KeyEventTranslations.tr define keyboard shortcuts, and when a keyboard shortcut is defined in both files, the one in MenuSetup.tr takes precedence. Sometimes the keyboard short cut in MenuSetup.tr is defined, but not active, and in those situations the identical keyboard short cut in KeyEventTranslations.tr will work. So, let'...


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