Robert Jacobson

Is this a version of the ambiguity between `x_.` and `x_..`? Mathematica (the software) treats the expression `x_..` inconsistently between the Notebook and command line interfaces. See [here](https://wltools.github.io/LanguageSpec/Contributing/Homeless-content/#different-behavior-between-the-kernel-and-the-notebook). I consider...

The rules for how `.` is parsed are arcane. Here are my private notes on the subject from last summer: `1//..9` is `` ReplaceRepeated[1, 0.9`] `` `1//.9` is `ReplaceRepeated[1, 9]`...

Pingback to #2 for reference, which references the edge case `x_..` discussed [here](https://wltools.github.io/LanguageSpec/Contributing/Homeless-content/#different-behavior-between-the-kernel-and-the-notebook).

They are tricky, because they are evaluated in a nonstandard and inconsistent way in Mathematica. I and other Mathematica syntax experts I have spoken with are inclined to treat them...

Screenshot, if it helps: 

Note that `ReplaceAll` is [the only known general purpose function that traverses the expression tree in preorder](https://mathematica.stackexchange.com/questions/9233/how-to-perform-a-depth-first-preorder-traversal-of-an-expression/9234#9234).

I have this issue in Chrome and Firefox. I work with data frames with many columns.

In my case, I used the app on my local repos, and then I connected my sourcerer account to my GitHub account. The local app did not add any of...

Is this still relevant in nom 6.0.0-alpha1? It might be easier just to wait for the new version of nom.

@kenkangxgwe My apologies for missing your question! My GitHub notifications have been overwhelming, and this issue got lost in the crowd. It appears the command line arguments aren't working at...