Skip to content
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

Closed
asr opened this issue Feb 22, 2016 · 8 comments
Closed

Key bindings for simplification/normalization of goals #1868

asr opened this issue Feb 22, 2016 · 8 comments
Labels
reduction type: discussion Discussions about Agda's design and implementation

Comments

@asr
Copy link
Member

asr commented Feb 22, 2016

In #1851 (comment) Ulf wrote:

Right now in master:

  • (no modifier): simplification
  • C-u: non-normalised
  • C-u C-u: normalised

I don't have strong opinions on this, but personally I use normalised more than the other two.

Andrea Vezzosi wrote here:

I would argue that we should switch the default back to fully normalised: I think it's the best default especially for users less in the know, so that they might have learnt neither the C-u C-u prefix nor what to expect from definitional equality.

I'm also agree with switching the default back to fully normalised.

@asr asr added type: enhancement Issues and pull requests about possible improvements reduction labels Feb 22, 2016
@jespercockx
Copy link
Member

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.

@jmchapman
Copy link
Contributor

I like the current behaviour, normalized is sometimes slow and unreadable.

@WolframKahl
Copy link
Member

On Mon, Feb 22, 2016 at 07:29:03AM -0800, James Chapman wrote:

I like the current behaviour, normalized is sometimes slow

(can be several minutes in some of my theories)

>> and unreadable.

(I've had over 120,000 lines there --- sometimes it is still
useful and essential; for quick exploration I just use the
double-click-for-matching-parentheses feature of Emacs
to skip past irrelevant material (in the case of (record { etc })
, click on the brace, not on the parenthesis),
and if I really need to analyse it, I save it into a file
and compress manually.
)

Normalised as default somehow does not feel right to me,
even though I use it most of the time.

For discoverability, perhaps the goal menu in Emacs
could include a separate entry for the normalised version?

Wolfram

@asr
Copy link
Member Author

asr commented Feb 22, 2016

There are strong arguments for keeping the current behaviour, so I'm closing the issue.

@asr asr closed this as completed Feb 22, 2016
@asr asr added type: discussion Discussions about Agda's design and implementation and removed type: enhancement Issues and pull requests about possible improvements labels Feb 22, 2016
@asr
Copy link
Member Author

asr commented Feb 22, 2016

@WolframKahl Please edit your comment. The ellipsis on the gray box can be easily not taken into account.

@asr
Copy link
Member Author

asr commented Feb 22, 2016

For discoverability, perhaps the goal menu in Emacs could include a separate entry for the normalised version?

I agree. Please open a new issue related to this enhancement.

@WolframKahl
Copy link
Member

@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.

@asr
Copy link
Member Author

asr commented Feb 22, 2016

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?

The same here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
reduction type: discussion Discussions about Agda's design and implementation
Projects
None yet
Development

No branches or pull requests

4 participants