# Tag Info

19

Feedback appreciated. I will try to add more definitions after hearing what features are needed. Features Markdown capabilities differ from environment to environment so I expect this will be only a base that one can modify so it fits his/her needs best. StackExchange MD supports only H1-H3 headers and Sub/sub/Titles are cell styles which I've ...

14

The old typesetting can be restored by SetSystemOptions["TypesetOptions" -> "IconicElidedForms" -> False]; Also mentioned previously: (1), (2), (3).

10

Intro One day I was playing with Developer package and found DateSetter which uses some kind of floating elements that I found useful. After taking a look at a source code I found out it was FrontEndAttachedCell. From the code one could learn enough to create something useful: Usage FrontEndAttachCell[ parentObject, (*Box or Cell ...

9

If you don't want to modify MenuSetup.tr you can easily modify init.m with: SetOptions[ $FrontEnd, NotebookEventActions :> { {"MenuCommand", "New"} :> CreateNotebook["Default"] } ] "MenuCommand" example 7 I think when it's done each time you save the notebook it should be nice enough :) SetOptions[ EvaluationNotebook[], NotebookEventActions -> { {"MenuCommand", "Save"} :> (Scan[ Module[{nr}, SelectionMove[#, All, CellGroup, AutoScroll -> False]; nr = Length @ Select[ SelectedCells[], ... 7 Several ways to do this but you could add the code below to a docked cell for example. DynamicModule[{open = False}, Button[Dynamic[If[TrueQ[open], "Open", "Close"]], NotebookFind[EvaluationNotebook[], "Input", All, CellStyle]; SetOptions[NotebookSelection[EvaluationNotebook[]], CellOpen -> open]; SelectionMove[EvaluationNotebook[], After, ... 7 If one feels comfortable modifying MenuSetup.tr, replacing its seventh line with MenuItem["&Notebook (.nb)", KernelExecute[CreateNotebook["Default"]], MenuEvaluator->"System", Method -> "Queued", MenuKey["n", Modifiers->{"Control"}]], will result in Ctrl+n creating a new notebook with a window size of ... 6 It doesn't seem to be possible with EvaluationCompletionAction but you can wrap input with custom function using$PreRead and friends: $Pre = Function[expr, Module[{start, result}, start = AbsoluteTime[]; result = expr; If[AbsoluteTime[] - start > 2, Speak @ "wow, it took at least 2 seconds"]; result ], HoldAll ] I'm using ... 6 This answer is focussed at more experienced users, to provide a way for them to find out more information. I do not discuss how anything works. Information in this answer corresponds to version 10.3 Despite the fact that PrintDefinitions@SyntaxInformation gives nothing, we can still see how the function works, by doing << GeneralUtilites ... 5 I get the same behaviour than your ("no output") with OSX. I did not even succeed to export some expressions to a file from this notebook (by inserting extra code with Put[...] or Save[...])... However, I've found 2 very simple alternatives using: NotebookEvaluate["yourPathTo/test.nb", InsertResults -> True] (Of course remove the command ... 5 Palette button CreatePalette[ Button["Compact Part", Do[ With[{ celldata = NotebookRead[cell], pattern = RuleDelayed[ RowBox[{h__, "[", RowBox[{"[", spec___, "]"}], "]"}], RowBox[{h, "\[LeftDoubleBracket]", RowBox[{spec}], "\[RightDoubleBracket]"}] ] }, If[ Not @ FreeQ[celldata, ... 5 If you want to make a nice neat way of displaying a thing with Head head, the following will work (thanks to Sjoerd): head /: Format[b : head[a_Association]] := RawBoxes[ BoxFormArrangeSummaryBox[ "NiceHeadName", b, Graphics3D[Cone[], ImageSize -> 20], {BoxFormMakeSummaryItem[{"Summary 1: ", a["sum1"]}, StandardForm], ... 4 You can do this by editing the private stylesheet (see other SE questions about this): which gives: or evaluate this, which can be inferred from other questions on this site about style sheeting: SetOptions[EvaluationNotebook[], StyleDefinitions -> Notebook[{Cell[StyleData[StyleDefinitions -> "Default.nb"]], Cell[StyleData["Notebook"], ... 3 To summarize and move from an unanswered stack: I have received a short and simple response from Wolfram tech support, informing me that they have "filed a bug report with the development team" and stating that "hopefully it would be improved in future release." So yes, I guess that makes it a bug. – ibeatty Aug 12 at 20:06 And indeed it is ... 3 The following shows a way to emulate the summary boxes using only documented constructs: grid[g_] := Column[Row /@ MapAt[Style[#, Gray] &, g, Table[{i, 1}, {i, Length[g]}]]] MakeBoxes[c : foo[___], form : (StandardForm | TraditionalForm)] := With[{boxes = RowBox[{"foo", "[", ToBoxes[Panel[ OpenerView[ ... 3 Here is what I got using V10.3: As you can see, V10.3 maintains all of the formatting when converting to pdf. I checked, just to make sure, and the PrintingStyleEnvironment is set to "PrintOut". 2 This answer is an addition to the excellent answer by Kuba that uses ImageResize and hence operates on the Notebook in a destructive way with loss of the original image data. Here is a modification of that solution which works non-destructively and simply sets widths for all images in the "Input" Cells equal to 100: Do[With[{nr = NotebookRead[cell]}, ... 1 This is how you can customize given notebook. Needs some testing but seems to work. It distinguishes users based on$UserName but you can use \$MachineID or whatever. CurrentValue[ EvaluationNotebook[], {TaggingRules, "Collaborators"}] = { "Kuba" -> Orange, "Friend" -> Red}; SetOptions[ EvaluationNotebook[], CellDynamicExpression :> ...

1

One way is to go with stylesheets, you can set DefaultNewInlineCellStyle option for StyleData["Notebook"] and for this given style, a specific CellSize, then you can proceed with toggling it. But it is messy and probably an overreaction. I'd go with this simple procedure, you can put it as a MenuItem, a new shortcut or whatever you find convenient. For ...

1