Marked keystrokes with the :kbd: role.

Fixed the case of the "Ctrl-" prefixes.
This commit is contained in:
Serhiy Storchaka 2015-09-12 17:45:25 +03:00
parent 06171bd52a
commit 0424eaf753
19 changed files with 32 additions and 32 deletions

View file

@ -1174,8 +1174,8 @@ partial list:
* In the editor window, there is now a line/column bar at the bottom.
* Three new keystroke commands: Check module (Alt-F5), Import module (F5) and
Run script (Ctrl-F5).
* Three new keystroke commands: Check module (:kbd:`Alt-F5`), Import module (:kbd:`F5`) and
Run script (:kbd:`Ctrl-F5`).
.. ======================================================================

View file

@ -827,7 +827,7 @@ inheritance relationships are::
This rearrangement was done because people often want to catch all exceptions
that indicate program errors. :exc:`KeyboardInterrupt` and :exc:`SystemExit`
aren't errors, though, and usually represent an explicit action such as the user
hitting Control-C or code calling :func:`sys.exit`. A bare ``except:`` will
hitting :kbd:`Control-C` or code calling :func:`sys.exit`. A bare ``except:`` will
catch all exceptions, so you commonly need to list :exc:`KeyboardInterrupt` and
:exc:`SystemExit` in order to re-raise them. The usual pattern is::

View file

@ -2320,7 +2320,7 @@ Port-Specific Changes: Windows
* The :func:`os.kill` function now works on Windows. The signal value
can be the constants :const:`CTRL_C_EVENT`,
:const:`CTRL_BREAK_EVENT`, or any integer. The first two constants
will send Control-C and Control-Break keystroke events to
will send :kbd:`Control-C` and :kbd:`Control-Break` keystroke events to
subprocesses; any other value will use the :c:func:`TerminateProcess`
API. (Contributed by Miki Tebeka; :issue:`1220212`.)