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

proof-shell: Don't ask about killing the proof assistant on exit #793

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

hendriktews
Copy link
Collaborator

This PR is only about the commit in the title. To avoid conflicts, it builds on PR #791.

I have disabled this silly question about killing Coq when quitting Emacs decades ago already. IMO we don't need a user option to control this behavior.

- add menu entry to disable splash screen to quick options
- add info to the splash screen on how to leave and disable the splash
  screen
- add Proof-General menu to splash screen, such that the hints on the
  splash screen make sense
- fix saving of quick options for several options
- the CHANGES entry also describes commit ea0f007
- adapt manual
Comment on lines +480 to +481
;; If one quits Proof General, it's clear that the proof
;; assistant needs to be killed - don't ask.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

On the one hand I agree with your remark;
but on the other hand I believe changing would be not "uniform" w.r.t. other emacs features?

e.g. if we do M-x shell RET
then C-x C-s, exactly as you say, "if we quit emacs, it's clear that the nested shell needs to be killed", but emacs will still ask for confirmation.

Would you agree to customize this?

@monnier
Copy link
Contributor

monnier commented Oct 4, 2024 via email

@erikmd
Copy link
Member

erikmd commented Oct 4, 2024

@monnier thanks for your feedback!

regarding your main point:

it's whether the state of the process is likely to contain information
that the user cannot trivially recreate (e.g. by restarting the process).

it appears than unlike M-x shell processes, coqtop processes generally generally don't contain "critical state information", so I guess this amounts to a +1 for @hendriktews 's proposition.

@andreas-roehler
Copy link

andreas-roehler commented Oct 8, 2024

Being in favour of the change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants