# Tag Info

3

The documentation for Association offers the following tantalizing (and frustrating) remarks... Typical list operations (such as Map, Select, and Sort) apply to the values in an association, leaving the keys unchanged. ... and ... Keys are "transparent" for many operations ... but it remains silent on the identity of those "many operations" ...

3

To me your question boils down to whether or not Listable functions are supposed to act as wrapped in Thread or MapThread. According to the documentation, Thread has not changed since V1 and, indeed, Thread[f[<|a -> 1, b -> 2|>, <|a -> 5, b -> 6|>]] f[<|a -> 1, b -> 2|>, <|a -> 5, b -> 6|>] However, ...

3

An alternative to modifying DocumentationNavigator.nb using a text editor is to change the notebook's options programmatically. Locate and open the notebook: NotebookOpen[FindFile["DocumentationNavigator.nb"]] Get the list of open notebooks using Notebooks[]: nbks = Notebooks[] nbks[[2]] is the notebook object we want to modify using SetOptions ...

4

In version 10 you can change the font size of the Virtual Book by changing its Magnification but in previous versions of Mathematica the file FindFile["DocumentationNavigator.nb"] C:\Program Files\Wolfram Research\Mathematica\8.0\Documentation\English\System\DocumentationNavigator.nb (which is the Virtual Book Notebook) has the option Editable ...

5

As far as I can tell, this wording was introduced in the V4 documentation. It predates the current documentation conventions where relationships and contrasts between functions are usually noted under the Properties & Relations heading. So I think that the wording is simply there to guide the user to the Element function if the goal is to do ...

6

Yes, this statement looks almost as if the last part is just a repetition of the first part with different wording, but for a different command. But there is an important difference, ad the juxtaposition of the two commands MemberQ and Element is probably intended to highlight that difference: It's all in the word immediate. The difference is probably best ...

2

The problem lies with the very first demo under "Neat Examples": DynamicModule[{text = ""}, Column[{InputField[Dynamic[text], String, ContinuousAction -> True, FieldHint -> "Enter a string"], Dynamic[Classify["Language", text, "TopProbabilities"]]}]] I can reproduce the bug exactly when I evaluate this in v10.0.1 on OSX 10.9.5 (sorry, ...

8

I confirm (Windows 7 x64, MMa 10.0.1). After opening the "Neat Examples" tab in the Documentation Center page for Classify MathKernel.exe loads HUGE amount of data from pacletserver2.wolfram.com. After 2 hours of waiting with hanging Mathematica FrontEnd I found in the %userprofile%\AppData\Roaming\Mathematica\Paclets\Temporary directory more than 600 ...

8

Indeed, StringCases does not have an operator form in 10.0.1. The documentation and usage message appear to be in error. StringCases does not appear on the list TypeSystem$OperatorForms -- although that is by no means conclusive as discussed here. I would argue that it should have an operator form, in symmetry with Cases. In any event, there is a bug ... 1 Run the follow to retrieve results Get[$InstallationDirectory<>"\\AddOns\\Applications\\DocumentationSearch\\DocumentationSearch.m"]; DocumentationSearchSearchDocumentation["test"] The formatting I believe is stored in C:\Program Files\Wolfram Research\Mathematica\10.0\SystemFiles\FrontEnd\StyleSheets\Wolfram\Reference.nb Or ...

2

Using Autohotkey the following works pretty well. #IfWinActive ahk_class NotebookFrame Enter::Send {blind}{shift down}{enter}{shift up} Shift & Enter::Send {enter} return In case the internals are ever changed you can use the following to get the internal class. Return:: WinGetClass, class, A MsgBox, The active window's class is "%class%". ...

Top 50 recent answers are included