# Tag Info

24

Update August 2014 The Legacy Solution below has been corrected to work in recent versions (9 and 10). At the same time however the introduction of PlotTheme functionality makes my solution largely academic as plot themes are designed to combine in the same manner. If no existing theme has the desired style you can create a custom one. This example ...

20

Here is one take on it -- the hard part was estimating how the PlotStyle option is turned into a list of directives. I think this works as the internal implementation: canonicalPlotStyle::usage = "Turn a PlotStyle option into the canonical form {_Directive...}"; canonicalPlotStyle[ps_] := Replace[ps, { a_List :> (Flatten[Directive @@ Flatten[{#}]] ...

20

I've never seen that command before but this does work at least in version 7 on Windows: FrontEndExecute[ AddMenuCommands[ "BackgroundDialog", {Delimiter, Item["L&inen", Background -> RGBColor[0.980, 0.941, 0.902]], Item["A&liceBlue", Background -> RGBColor[0.941, 0.973, 1.0]], Item["Min&tCream", Background -> ...

19

You need to add the following to KeyEventTranslations.tr: Item[KeyEvent["Tab", Modifiers -> {Control}], FrontEndExecute[FrontEndToken["CycleNotebooksForward"]]], Item[KeyEvent["Tab", Modifiers -> {Shift, Control}], FrontEndExecute[FrontEndToken["CycleNotebooksBackward"]]], This will map Control-Tab and Control-Shift-Tab to cycling between ...

15

There is an undocumented file in the installation directory named specialArgFunctions.tr: NotebookOpen @ FileNameJoin @ { $InstallationDirectory, "SystemFiles", "FrontEnd", "SystemResources" , "FunctionalFrequency", "specialArgFunctions.tr" } This file describes in detail how to attach completion actions to each parameter of listed functions. For ... 13 This is similar to my Log question and similar methods can be used.$PrePrint = # /. { Csc[z_] :> 1 / Defer@Sin[z], Sec[z_] :> 1 / Defer@Cos[z] } &; Example: (x + y) Csc[x] Sec[y] (x + y)/(Cos[y] Sin[x])

13

Referencing Szabolcs's answer, here is the code that must be added to KeyEventTranslations.tr: Item[KeyEvent["m", Modifiers -> {Control}], FrontEndExecute[{ FrontEndSelectionMove[FrontEndSelectedNotebook[], All, Cell], FrontEndFrontEndToken["Clear"] }]], I chose Ctrl+M at random; change it to whatever you want. See this ...

13

Changing shortcuts isn't that complicated. All you have to do is change one line in the file KeyEventTranslations.tr in a location in your file system specified by this command: FileNameJoin[{$InstallationDirectory, "SystemFiles", "FrontEnd", "TextResources",$OperatingSystem}] Locate the following line in a text editor and change the key into the one ...

13

This can be accomplished using LinkWrite. You can place the following code in init.m. To add a color to the background colors submenu you can use... LinkWrite[$ParentLink, AddMenuCommands[ "BackgroundDialog", {Delimiter, Item["M&y Color", Background -> RGBColor[0.980, 0.941, 0.902]]}]] To add a link to the AddOns documentation you can ... 12 This will add Quit to Control+Q (and Alt+V Q Q): FrontEndExecute[ FrontEndAddMenuCommands["MenuListQuitEvaluators", {MenuItem["AddMenu &Quit", FrontEndKernelExecute[ToExpression["Quit[]"]], MenuKey["q", Modifiers -> {"Control"}], SystemMenuEvaluator -> Automatic]}]] It only persists for the front end session. Usually I keep ... 12 Open the Edit -> Preferences menu and try setting the following: 12 To format all your output expressions as TraditionalForm, you can set the$Post variable as: $Post = TraditionalForm Here's how it would look: To clear the definition for$Post (if you need to), just evaluate $Post =. You can add this to your init.m if you'd like to make this apply to all notebooks henceforth, but I wouldn't suggest doing that. 12 You could create a custom stylesheet that has a different background color and define it to be the default one. To do that, go to Format | Edit Stylesheet, select All in the "Choose a style" combo box. Select the appearing entry in the list below and set your appropriate style definitions for it, in your case that would be another background color using ... 11 Here's a quick solution. Note that it's only tested in Ubuntu - please test it in other operating systems and make any changes that are necessary. First we define a sendNotification command and then show how to create a style of input cell that automatically calls it. Also included is a palette that will modify any cell to have the appropriate CellEpilog ... 11 Preamble I will interpret your question in the narrow context of customizibility. Most of the information can be found in the documentation, but is alas scattered over several places. Below I will attempt to assemble a single sequence, mostly using this source. Where my description deviates from it, I will put the LS sign indicating that what follows ismy ... 11 Thanks to everyone for the helpful comments. Here's the exact procedure I used to fix this (specific to Mac OS X, version 10.8 if that matters, and Mathematica 8, but it should be analogously applicable to other versions and operating systems): Close Mathematica Delete the keymap cache. For me this was in ~/Library/Mathematica/FrontEnd/8.0 ... 11 Edit > Preferences > "Advanced" tab > Open Option Inspector In the Option Inspector's sidebar, drill down to Notebook Options > Window Properties. For the WindowElements option, uncheck "StatusArea" and "MagnificationPopUp". Here's what your Option Inspector should look like: 10 Re: appearance, you can do this with a style sheet. Below are some cells with my styles for a) running the terminal in Mma and b) sending stuff to a word document. If that is what you are looking for I'll post a more detailed example. Re: "predictive text coloring" I presume you mean syntax styling of Mathematica code? If so this can be configured from ... 10 You can SetOptions for the current notebook as: SetOptions[EvaluationNotebook[], Background -> LightGreen] to change the background to whatever colour you like. You can also supply an RGB colour as: SetOptions[EvaluationNotebook[], Background -> RGBColor[0.9, 0.7, 0.7]] Other possibilities for the first argument of SetOptions are$FrontEnd ...

10

Extending ColorData For some background consider reading this bookmarked conversation. The color scheme data itself is accessed through the definition of this Symbol: DataPacletsColorDataDumpcolorSchemes The data is located by use of the list defined in: DataPacletsColorDataDumpcolorSchemeNames That is to say the scheme is extracted using ...

9

I usually press the down key until I get out of the cell, then press shift-up to select it. Here are two buttons that will select or delete the whole cell for you: select = Button["Select Cell", SelectionMove[SelectedNotebook[], All, Cell]] delete = Button["Delete Cell", SelectionMove[SelectedNotebook[], All, Cell]; FrontEndTokenExecute["Clear"]] ...

9

This is work in progress, I'm posting it because I'm not sure to be able to finish it, and perhaps someone wants to. The idea is to combine the wonderful Janus's solution with this nice trick to redefine the Plot[ ] standard behavior. The program below works for a large subset of the help page for Plot[ ], but fails for two or three. The code is not ...

9

Since you want this functionality to be able to insert aliases using the EscshortcutEsc syntax, you can edit the KeyEventsTranslation.tr file to achieve this. Copy the following file: $InstallationDirectory/SystemFiles/FrontEnd/TextResources/Macintosh/KeyEventTranslations.tr or its equivalent on your system to$UserBaseDirectory/ (with the same directory ...

9

You can't add an entirely new menu using AddMenuCommands. We have it from John Fultz here: "AddMenuCommands can only position a menu relative to one with a simple front end token." (I trust I've not taken that out of context.)

9

Go to Format -> Edit Stylesheet Under "Choose a style" choose "Output" Select the cell bracket of the new cell that appears Press Ctrl+Shift+E (Command+Shift+E on a Mac) to show the cell expression Change Cell[StyleData["Output"]] to Cell[StyleData["Output"], ShowCellLabel -> False] Press Ctrl+Shift+E again Close the stylesheet window

8

Yes, you can use InputAliases to style the replacements as you wish. I explained how to make auto replacements in this answer, but that was for a more specialized purpose. As a simple example, you can do something like: SetOptions[SelectedNotebook[], InputAliases -> {"foo" -> MakeBoxes@Row[{ Style[foo, FontColor -> Red, FontWeight ...

8

Actually I got my answer by looking at the question "Changing default window appearance" answers. It is explained there that to change the default settings of the Documentation Center notebook you have to go to the settings "HelpViewerSettings" and make "Enable" True. The "WindowsSize" option in "Windows Properties" in the "NoteBook Options" does not apply. ...

8

The simplest (and canonical) method is to place the keyboard cursor in the Symbol name, or select it with a double-click, and press F1 if you use Windows/Linux or Command-Shift-F if you use OS X. This will bring up the Help for that item. This also works with compound operators, e.g. /;. Nevertheless I like a challenge, therefore: \$PreRead = # /. ...

8

I'm the one inside the company who suggested RightComposition (and pushed for syntax for Composition and RightComposition). I'm sympathetic to your need, and have wanted the same thing once or twice myself. Given that not much /* and @* code has been written yet, I think it is certainly possible we could have /* parse to LeftComposition. I'm not sure what ...

7

You can also use hotstrings as a way of autocompletion. By using such replacements, words are immediately replaced by another word on typing a space after the hotstring: CreateDocument[{}, InputAutoReplacements -> {"sync" -> SynchronousInitialization}] You can set such replacements globally under Option Inspector (CtrlShiftO). Of course no one would ...

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