New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Key bindings for simplification/normalization of goals #1868
Comments
Personally, I'm in favor of keeping the current behavior: normalised only helps me very rarely, since it destroys all my carefully crafted layers of abstraction. I can understand that newcomers don't find this a big problem (since they don't have as many layers of abstraction) but for me, having the default behavior be normalization would discourage me from trying to build the abstractions in the first place. |
I like the current behaviour, normalized is sometimes slow and unreadable. |
On Mon, Feb 22, 2016 at 07:29:03AM -0800, James Chapman wrote:
(can be several minutes in some of my theories)
(I've had over 120,000 lines there --- sometimes it is still Normalised as default somehow does not feel right to me, For discoverability, perhaps the goal menu in Emacs Wolfram |
There are strong arguments for keeping the current behaviour, so I'm closing the issue. |
@WolframKahl Please edit your comment. The ellipsis on the gray box can be easily not taken into account. |
I agree. Please open a new issue related to this enhancement. |
@asr I have no idea what is going on there, and why it does not even format mail quotations as it does for example in the original posting in this issue. I find nothing in the github MarkDown documentation that might explain that ellipsis: Where do I find that documented? Please feel free to fix it if you know how. |
The same here. |
In #1851 (comment) Ulf wrote:
Andrea Vezzosi wrote here:
I'm also agree with switching the default back to fully normalised.
The text was updated successfully, but these errors were encountered: