Description

I would still prefer MORE command not to break on 40 column screen modes, thus I have added short prompts, which do not contain ANY tips/hints for the user; this way they will remain short for every translation imaginable.

I agree that no one uses them on purpose, but sometimes we end up in one when the program malfunctions and terminates - the change is to give a small aid to the user, who might want to do some recovery actions or post-mortem analysis.

Manual testing

I have only tested this by manually changing use_short_prompt condition in the code, to trigger displaying short prompts.

Checklist

I have:

• followed the project's contributing guidelines and code of conduct.
• performed a self-review of my code.
• commented on the particularly hard-to-understand areas of my code.
• split my work into well-defined, bisectable commits, and I named my commits well.
• applied the appropriate labels (bug, enhancement, refactoring, documentation, etc.)
• checked that all my commits can be built.
• confirmed that my code does not cause performance regressions (e.g., by running the Quake benchmark).
• added unit tests where applicable to prove the correctness of my code and to avoid future regressions.
• made corresponding changes to the documentation or the website according to the documentation guidelines.
• locally verified my website or documentation changes.