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

Feature request: use goal count information printed at top of goals buffer in modeline #605

Open
cpitclaudel opened this issue Oct 6, 2021 · 4 comments

Comments

@cpitclaudel
Copy link
Member

I won't have time to implement this, but it should be easy and it should provide a nice quality of life improvement.

Each goal buffer stars with a header line, like this:

1 focused subgoal
(shelved: 1) (ID 339)
  
  width : Z
  BW : Bitwidth width
  …

It would be nice to move that info to the modeline, next to the buffer name (*goals*). We can change the "lighter" of the response mode to be a variable for that, and then update the variable when we update the response buffer.

This would save a bit of space, which is always nice with large Coq goals.

@cpitclaudel
Copy link
Member Author

Related: coq/coq#14999

@Matafou
Copy link
Contributor

Matafou commented Oct 8, 2021

PG already shows the number of goals in the scripting buffer modeline.
People hardly notice it I suppose.
What exact display do you have in mind?

@Matafou
Copy link
Contributor

Matafou commented Oct 8, 2021

As you suggest we could show it in the goals buffer modeline of course. I suppose it is more intuitive.

@Matafou
Copy link
Contributor

Matafou commented Oct 13, 2021

Actually I have been thinking of enhancing further the coq/PG UI wrt to number of subgoals and also script parenthesizing ({ }) and bullets.
Ideally I would like coq to print all subgoals together with the corresponding bullet imbrication :

n subgoals.

current goal:
- + * {

n,m:nat
H: ...
H0: ....
======
...
}
      forall n m: Z, ...
- + * forall n:nat, ...
- + forall x:bool, ....
- + forall n:Z, ...
- forall n:nat, ...

I think this information could be of some help when dealing with large proofs. I am not sure how PG could relay it in a nice way though...

axe1d pushed a commit to axe1d/PG that referenced this issue Mar 31, 2024
axe1d pushed a commit to axe1d/PG that referenced this issue Mar 31, 2024
axe1d pushed a commit to axe1d/PG that referenced this issue Mar 31, 2024
axe1d pushed a commit to axe1d/PG that referenced this issue Apr 7, 2024
axe1d pushed a commit to axe1d/PG that referenced this issue Apr 7, 2024
axe1d pushed a commit to axe1d/PG that referenced this issue Apr 7, 2024
axe1d pushed a commit to axe1d/PG that referenced this issue Apr 7, 2024
axe1d pushed a commit to axe1d/PG that referenced this issue Apr 18, 2024
axe1d pushed a commit to axe1d/PG that referenced this issue Apr 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants