+2 -2

Documentation/admin-guide/braille-console.rst

reviewed

··· 21 21 By default, the braille device will just show the last kernel message (console 22 22 mode). To review previous messages, press the Insert key to switch to the VT 23 23 review mode. In review mode, the arrow keys permit to browse in the VT content, 24 24 - :kbd:`PAGE-UP`/:kbd:`PAGE-DOWN` keys go at the top/bottom of the screen, and 25 25 - the :kbd:`HOME` key goes back 24 24 + `PAGE-UP`/`PAGE-DOWN` keys go at the top/bottom of the screen, and 25 25 + the `HOME` key goes back 26 26 to the cursor, hence providing very basic screen reviewing facility. 27 27 28 28 Sound feedback can be obtained by adding the ``braille_console.sound=1`` kernel

+10 -10

Documentation/admin-guide/sysrq.rst

reviewed

··· 49 49 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 50 50 51 51 On x86 52 52 - You press the key combo :kbd:`ALT-SysRq-<command key>`. 52 52 + You press the key combo `ALT-SysRq-<command key>`. 53 53 54 54 .. note:: 55 55 Some 56 56 keyboards may not have a key labeled 'SysRq'. The 'SysRq' key is 57 57 also known as the 'Print Screen' key. Also some keyboards cannot 58 58 handle so many keys being pressed at the same time, so you might 59 59 - have better luck with press :kbd:`Alt`, press :kbd:`SysRq`, 60 60 - release :kbd:`SysRq`, press :kbd:`<command key>`, release everything. 59 59 + have better luck with press `Alt`, press `SysRq`, 60 60 + release `SysRq`, press `<command key>`, release everything. 61 61 62 62 On SPARC 63 63 - You press :kbd:`ALT-STOP-<command key>`, I believe. 63 63 + You press `ALT-STOP-<command key>`, I believe. 64 64 65 65 On the serial console (PC style standard serial ports only) 66 66 You send a ``BREAK``, then within 5 seconds a command key. Sending 67 67 ``BREAK`` twice is interpreted as a normal BREAK. 68 68 69 69 On PowerPC 70 70 - Press :kbd:`ALT - Print Screen` (or :kbd:`F13`) - :kbd:`<command key>`. 71 71 - :kbd:`Print Screen` (or :kbd:`F13`) - :kbd:`<command key>` may suffice. 70 70 + Press `ALT - Print Screen` (or `F13`) - `<command key>`. 71 71 + `Print Screen` (or `F13`) - `<command key>` may suffice. 72 72 73 73 On other 74 74 If you know of the key combos for other architectures, please ··· 88 88 89 89 echo _reisub > /proc/sysrq-trigger 90 90 91 91 - The :kbd:`<command key>` is case sensitive. 91 91 + The `<command key>` is case sensitive. 92 92 93 93 What are the 'command' keys? 94 94 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ··· 225 225 226 226 When this happens, try tapping shift, alt and control on both sides of the 227 227 keyboard, and hitting an invalid sysrq sequence again. (i.e., something like 228 228 - :kbd:`alt-sysrq-z`). 228 228 + `alt-sysrq-z`). 229 229 230 230 - Switching to another virtual console (:kbd:`ALT+Fn`) and then back again 230 230 + Switching to another virtual console (`ALT+Fn`) and then back again 231 231 should also help. 232 232 233 233 I hit SysRq, but nothing seems to happen, what's wrong? ··· 290 290 consumers as if the current loglevel was maximum. If only the header 291 291 is emitted it is almost certain that the kernel loglevel is too low. 292 292 Should you require the output on the console channel then you will need 293 293 - to temporarily up the console loglevel using :kbd:`alt-sysrq-8` or:: 293 293 + to temporarily up the console loglevel using `alt-sysrq-8` or:: 294 294 295 295 echo 8 > /proc/sysrq-trigger 296 296

+25 -25

Documentation/dev-tools/kgdb.rst

reviewed

··· 255 255 .. note:: 256 256 257 257 Kgdboc does not support interrupting the target via the gdb remote 258 258 - protocol. You must manually send a :kbd:`SysRq-G` unless you have a proxy 258 258 + protocol. You must manually send a `SysRq-G` unless you have a proxy 259 259 that splits console output to a terminal program. A console proxy has a 260 260 separate TCP port for the debugger and a separate TCP port for the 261 261 - "human" console. The proxy can take care of sending the :kbd:`SysRq-G` 261 261 + "human" console. The proxy can take care of sending the `SysRq-G` 262 262 for you. 263 263 264 264 When using kgdboc with no debugger proxy, you can end up connecting the ··· 267 267 waiting for the debugger. In this case you disconnect your terminal 268 268 program and then connect the debugger in its place. If you want to 269 269 interrupt the target system and forcibly enter a debug session you have 270 270 - to issue a :kbd:`Sysrq` sequence and then type the letter :kbd:`g`. Then you 270 270 + to issue a `Sysrq` sequence and then type the letter `g`. Then you 271 271 disconnect the terminal session and connect gdb. Your options if you 272 272 - don't like this are to hack gdb to send the :kbd:`SysRq-G` for you as well as 272 272 + don't like this are to hack gdb to send the `SysRq-G` for you as well as 273 273 on the initial connect, or to use a debugger proxy that allows an 274 274 unmodified gdb to do the debugging. 275 275 ··· 401 401 402 402 2. Enter the kernel debugger manually or by waiting for an oops or 403 403 fault. There are several ways you can enter the kernel debugger 404 404 - manually; all involve using the :kbd:`SysRq-G`, which means you must have 404 404 + manually; all involve using the `SysRq-G`, which means you must have 405 405 enabled ``CONFIG_MAGIC_SYSRQ=y`` in your kernel config. 406 406 407 407 - When logged in as root or with a super user session you can run:: ··· 410 410 411 411 - Example using minicom 2.2 412 412 413 413 - Press: :kbd:`CTRL-A` :kbd:`f` :kbd:`g` 413 413 + Press: `CTRL-A` `f` `g` 414 414 415 415 - When you have telneted to a terminal server that supports sending 416 416 a remote break 417 417 418 418 - Press: :kbd:`CTRL-]` 418 418 + Press: `CTRL-]` 419 419 420 420 Type in: ``send break`` 421 421 422 422 - Press: :kbd:`Enter` :kbd:`g` 422 422 + Press: `Enter` `g` 423 423 424 424 3. From the kdb prompt you can run the ``help`` command to see a complete 425 425 list of the commands that are available. ··· 460 460 461 461 2. Enter the kernel debugger manually or by waiting for an oops or 462 462 fault. There are several ways you can enter the kernel debugger 463 463 - manually; all involve using the :kbd:`SysRq-G`, which means you must have 463 463 + manually; all involve using the `SysRq-G`, which means you must have 464 464 enabled ``CONFIG_MAGIC_SYSRQ=y`` in your kernel config. 465 465 466 466 - When logged in as root or with a super user session you can run:: ··· 469 469 470 470 - Example using a laptop keyboard: 471 471 472 472 - Press and hold down: :kbd:`Alt` 472 472 + Press and hold down: `Alt` 473 473 474 474 - Press and hold down: :kbd:`Fn` 474 474 + Press and hold down: `Fn` 475 475 476 476 - Press and release the key with the label: :kbd:`SysRq` 476 476 + Press and release the key with the label: `SysRq` 477 477 478 478 - Release: :kbd:`Fn` 478 478 + Release: `Fn` 479 479 480 480 - Press and release: :kbd:`g` 480 480 + Press and release: `g` 481 481 482 482 - Release: :kbd:`Alt` 482 482 + Release: `Alt` 483 483 484 484 - Example using a PS/2 101-key keyboard 485 485 486 486 - Press and hold down: :kbd:`Alt` 486 486 + Press and hold down: `Alt` 487 487 488 488 - Press and release the key with the label: :kbd:`SysRq` 488 488 + Press and release the key with the label: `SysRq` 489 489 490 490 - Press and release: :kbd:`g` 490 490 + Press and release: `g` 491 491 492 492 - Release: :kbd:`Alt` 492 492 + Release: `Alt` 493 493 494 494 3. Now type in a kdb command such as ``help``, ``dmesg``, ``bt`` or ``go`` to 495 495 continue kernel execution. ··· 531 531 532 532 In order to connect to gdb via kgdboc, the kernel must first be 533 533 stopped. There are several ways to stop the kernel which include 534 534 - using kgdbwait as a boot argument, via a :kbd:`SysRq-G`, or running the 534 534 + using kgdbwait as a boot argument, via a `SysRq-G`, or running the 535 535 kernel until it takes an exception where it waits for the debugger to 536 536 attach. 537 537 ··· 541 541 542 542 - Example using minicom 2.2 543 543 544 544 - Press: :kbd:`CTRL-A` :kbd:`f` :kbd:`g` 544 544 + Press: `CTRL-A` `f` `g` 545 545 546 546 - When you have telneted to a terminal server that supports sending 547 547 a remote break 548 548 549 549 - Press: :kbd:`CTRL-]` 549 549 + Press: `CTRL-]` 550 550 551 551 Type in: ``send break`` 552 552 553 553 - Press: :kbd:`Enter` :kbd:`g` 553 553 + Press: `Enter` `g` 554 554 555 555 3. Connect from gdb 556 556 ··· 578 578 set debug remote 1 579 579 580 580 Remember if you continue in gdb, and need to "break in" again, you need 581 581 - to issue an other :kbd:`SysRq-G`. It is easy to create a simple entry point by 581 581 + to issue an other `SysRq-G`. It is easy to create a simple entry point by 582 582 putting a breakpoint at ``sys_sync`` and then you can run ``sync`` from a 583 583 shell or script to break into the debugger. 584 584 ··· 612 612 613 613 .. note:: 614 614 615 615 - Now you must kill gdb. Typically you press :kbd:`CTRL-Z` and issue 615 615 + Now you must kill gdb. Typically you press `CTRL-Z` and issue 616 616 the command:: 617 617 618 618 kill -9 %

+4 -4

Documentation/process/email-clients.rst

reviewed

··· 86 86 - :menuselection:`Strip Whitespace Before Sending` must be ``disabled`` 87 87 88 88 When composing the message, the cursor should be placed where the patch 89 89 - should appear, and then pressing :kbd:`CTRL-R` let you specify the patch file 89 89 + should appear, and then pressing `CTRL-R` let you specify the patch file 90 90 to insert into the message. 91 91 92 92 Claws Mail (GUI) ··· 94 94 95 95 Works. Some people use this successfully for patches. 96 96 97 97 - To insert a patch use :menuselection:`Message-->Insert File` (:kbd:`CTRL-I`) 97 97 + To insert a patch use :menuselection:`Message-->Insert File` (`CTRL-I`) 98 98 or an external editor. 99 99 100 100 If the inserted patch has to be edited in the Claws composition window ··· 108 108 Some people use this successfully for patches. 109 109 110 110 When composing mail select: Preformat 111 111 - from :menuselection:`Format-->Paragraph Style-->Preformatted` (:kbd:`CTRL-7`) 111 111 + from :menuselection:`Format-->Paragraph Style-->Preformatted` (`CTRL-7`) 112 112 or the toolbar 113 113 114 114 Then use: 115 115 - :menuselection:`Insert-->Text File...` (:kbd:`ALT-N x`) 115 115 + :menuselection:`Insert-->Text File...` (`ALT-N x`) 116 116 to insert the patch. 117 117 118 118 You can also ``diff -Nru old.c new.c | xclip``, select

+3 -3

Documentation/scheduler/sched-ext.rst

reviewed

··· 16 16 * The system integrity is maintained no matter what the BPF scheduler does. 17 17 The default scheduling behavior is restored anytime an error is detected, 18 18 a runnable task stalls, or on invoking the SysRq key sequence 19 19 - :kbd:`SysRq-S`. 19 19 + `SysRq-S`. 20 20 21 21 * When the BPF scheduler triggers an error, debug information is dumped to 22 22 aid debugging. The debug dump is passed to and printed out by the 23 23 scheduler binary. The debug dump can also be accessed through the 24 24 - `sched_ext_dump` tracepoint. The SysRq key sequence :kbd:`SysRq-D` 24 24 + `sched_ext_dump` tracepoint. The SysRq key sequence `SysRq-D` 25 25 triggers a debug dump. This doesn't terminate the BPF scheduler and can 26 26 only be read through the tracepoint. 27 27 ··· 59 59 by sched_ext, while tasks with ``SCHED_NORMAL``, ``SCHED_BATCH`` and 60 60 ``SCHED_IDLE`` policies are scheduled by CFS. 61 61 62 62 - Terminating the sched_ext scheduler program, triggering :kbd:`SysRq-S`, or 62 62 + Terminating the sched_ext scheduler program, triggering `SysRq-S`, or 63 63 detection of any internal error including stalled runnable tasks aborts the 64 64 BPF scheduler and reverts all tasks back to CFS. 65 65

+4 -4

Documentation/translations/it_IT/process/email-clients.rst

reviewed

··· 95 95 - :menuselection:`Strip Whitespace Before Sending` deve essere ``disabled`` 96 96 97 97 Quando state scrivendo un messaggio, il cursore dev'essere posizionato 98 98 - dove volete che la patch inizi, poi premendo :kbd:`CTRL-R` vi verrà chiesto 98 98 + dove volete che la patch inizi, poi premendo `CTRL-R` vi verrà chiesto 99 99 di selezionare il file patch da inserire nel messaggio. 100 100 101 101 Claws Mail (GUI) ··· 104 104 Funziona. Alcune persone riescono ad usarlo con successo per inviare le patch. 105 105 106 106 Per inserire una patch usate :menuselection:`Messaggio-->Inserisci file` 107 107 - (:kbd:`CTRL-I`) oppure un editor esterno. 107 107 + (`CTRL-I`) oppure un editor esterno. 108 108 109 109 Se la patch che avete inserito dev'essere modificata usando la finestra di 110 110 scrittura di Claws, allora assicuratevi che l'"auto-interruzione" sia ··· 117 117 118 118 Quando state scrivendo una lettera selezionate: Preformattato 119 119 da :menuselection:`Formato-->Stile del paragrafo-->Preformattato` 120 120 - (:kbd:`CTRL-7`) o dalla barra degli strumenti 120 120 + (`CTRL-7`) o dalla barra degli strumenti 121 121 122 122 Poi per inserire la patch usate: 123 123 - :menuselection:`Inserisci--> File di testo...` (:kbd:`ALT-N x`) 123 123 + :menuselection:`Inserisci--> File di testo...` (`ALT-N x`) 124 124 125 125 Potete anche eseguire ``diff -Nru old.c new.c | xclip``, selezionare 126 126 :menuselection:`Preformattato`, e poi usare il tasto centrale del mouse.

+4 -4

Documentation/translations/sp_SP/process/email-clients.rst

reviewed

··· 96 96 - :menuselection:`Strip Whitespace Before Sending` debe estar ``disabled`` 97 97 98 98 Al redactar el mensaje, el cursor debe colocarse donde el parche debería 99 99 - aparecer, y luego presionando :kbd:`CTRL-R` se le permite especificar e 99 99 + aparecer, y luego presionando `CTRL-R` se le permite especificar e 100 100 archivo de parche a insertar en el mensaje. 101 101 102 102 Claws Mail (GUI) ··· 104 104 105 105 Funciona. Algunos usan esto con éxito para los parches. 106 106 107 107 - Para insertar un parche haga :menuselection:`Message-->Insert File` (:kbd:`CTRL-I`) 107 107 + Para insertar un parche haga :menuselection:`Message-->Insert File` (`CTRL-I`) 108 108 o use un editor externo. 109 109 110 110 Si el parche insertado debe editarse en la ventana de composición de Claws ··· 118 118 Algunos usan esto con éxito para sus parches. 119 119 120 120 Cuando escriba un correo seleccione: Preformat 121 121 - desde :menuselection:`Format-->Paragraph Style-->Preformatted` (:kbd:`CTRL-7`) 121 121 + desde :menuselection:`Format-->Paragraph Style-->Preformatted` (`CTRL-7`) 122 122 o en la barra de herramientas 123 123 124 124 Luego haga: 125 125 - :menuselection:`Insert-->Text File...` (:kbd:`ALT-N x`) 125 125 + :menuselection:`Insert-->Text File...` (`ALT-N x`) 126 126 para insertar el parche. 127 127 128 128 También puede hacer ``diff -Nru old.c new.c | xclip``, seleccione

+11 -11

Documentation/translations/zh_CN/admin-guide/sysrq.rst

reviewed

··· 60 60 ~~~~~~~~~~~~~~~~~~~~~~~ 61 61 62 62 在 x86 架构上 63 63 - 你可以按下键盘组合键 :kbd:`ALT-SysRq-<command key>`。 63 63 + 你可以按下键盘组合键 `ALT-SysRq-<command key>`。 64 64 65 65 .. note:: 66 66 一些键盘可能没有标识 'SySRq' 键。'SySRq' 键也被当做 'Print Screen'键。 67 67 - 同时有些键盘无法处理同时按下这么多键，因此你可以先按下键盘 :kbd:`Alt` 键， 68 68 - 然后按下键盘 :kbd:`SysRq` 键，再释放键盘 :kbd:`SysRq` 键，之后按下键盘上命令键 69 69 - :kbd:`<command key>`，最后释放所有键。 67 67 + 同时有些键盘无法处理同时按下这么多键，因此你可以先按下键盘 `Alt` 键， 68 68 + 然后按下键盘 `SysRq` 键，再释放键盘 `SysRq` 键，之后按下键盘上命令键 69 69 + `<command key>`，最后释放所有键。 70 70 71 71 在 SPARC 架构上 72 72 - 你可以按下键盘组合键 :kbd:`ALT-STOP-<command key>` 。 72 72 + 你可以按下键盘组合键 `ALT-STOP-<command key>` 。 73 73 74 74 在串行控制台（只针对 PC 类型的标准串口） 75 75 你可以发一个 ``BREAK`` ，然后在 5 秒内发送一个命令键， 76 76 发送 ``BREAK`` 两次将被翻译为一个正常的 BREAK 操作。 77 77 78 78 在 PowerPC 架构上 79 79 - 按下键盘组合键 :kbd:`ALT - Print Screen` （或者 :kbd:`F13`） - :kbd:`<命令键>` 。 80 80 - :kbd:`Print Screen` （或者 :kbd:`F13`） - :kbd:`<命令键>` 或许也能实现。 79 79 + 按下键盘组合键 `ALT - Print Screen` （或者 `F13`） - `<命令键>` 。 80 80 + `Print Screen` （或者 `F13`） - `<命令键>` 或许也能实现。 81 81 82 82 在其他架构上 83 83 如果你知道其他架构的组合键，请告诉我，我可以把它们添加到这部分。 ··· 87 87 88 88 echo t > /proc/sysrq-trigger 89 89 90 90 - 这个命令键 :kbd:`<command key>` 是区分大小写的。 90 90 + 这个命令键 `<command key>` 是区分大小写的。 91 91 92 92 什么是命令键？ 93 93 ~~~~~~~~~~~~~~ ··· 203 203 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 204 204 205 205 这也会发生在我这，我发现轻敲键盘两侧的 shift、alt 和 control 键，然后再次敲击 206 206 - 一个无效的 SysRq 键序列可以解决问题。（比如，像键盘组合键 :kbd:`alt-sysrq-z` ） 207 207 - 切换到另一个虚拟控制台（键盘操作 :kbd:`ALT+Fn` ），然后再切回来应该也有帮助。 206 206 + 一个无效的 SysRq 键序列可以解决问题。（比如，像键盘组合键 `alt-sysrq-z` ） 207 207 + 切换到另一个虚拟控制台（键盘操作 `ALT+Fn` ），然后再切回来应该也有帮助。 208 208 209 209 我敲击了 SysRq 键，但像是什么都没发生，发生了什么错误？ 210 210 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ··· 259 259 文件的消费访问到。作为一个特例，来自 sysrq 命令的标题行将被传递给所有控制台 260 260 使用者，就好像当前日志级别是最大的一样。如果只发出标题头，则几乎可以肯定内核日志 261 261 级别太低。如果你需要控制台上的输出，那么你将需要临时提高控制台日志级别，通过使用 262 262 - 键盘组合键 :kbd:`alt-sysrq-8` 或者:: 262 262 + 键盘组合键 `alt-sysrq-8` 或者:: 263 263 264 264 echo 8 > /proc/sysrq-trigger 265 265

+4 -4

Documentation/translations/zh_CN/process/email-clients.rst

reviewed

··· 85 85 - :menuselection:`Do Not Send Flowed Text` 必须开启 86 86 - :menuselection:`Strip Whitespace Before Sending` 必须关闭 87 87 88 88 - 当写邮件时，光标应该放在补丁会出现的地方，然后按下 :kbd:`CTRL-R` 组合键，使指 88 88 + 当写邮件时，光标应该放在补丁会出现的地方，然后按下 `CTRL-R` 组合键，使指 89 89 定的补丁文件嵌入到邮件中。 90 90 91 91 Claws Mail (GUI) ··· 93 93 94 94 可以用，有人用它成功地发过补丁。 95 95 96 96 - 用 :menuselection:`Message-->Insert File` (:kbd:`CTRL-I`) 或外置编辑器插入补丁。 96 96 + 用 :menuselection:`Message-->Insert File` (`CTRL-I`) 或外置编辑器插入补丁。 97 97 98 98 若要在Claws编辑窗口重修改插入的补丁，需关闭 99 99 :menuselection:`Configuration-->Preferences-->Compose-->Wrapping` ··· 105 105 一些开发者成功的使用它发送补丁。 106 106 107 107 撰写邮件时： 108 108 - 从 :menuselection:`格式-->段落样式-->预格式化` (:kbd:`CTRL-7`) 108 108 + 从 :menuselection:`格式-->段落样式-->预格式化` (`CTRL-7`) 109 109 或工具栏选择 :menuselection:`预格式化` ； 110 110 111 111 然后使用： 112 112 - :menuselection:`插入-->文本文件...` (:kbd:`ALT-N x`) 插入补丁文件。 112 112 + :menuselection:`插入-->文本文件...` (`ALT-N x`) 插入补丁文件。 113 113 114 114 你还可以 ``diff -Nru old.c new.c | xclip`` ，选择 :menuselection:`预格式化` ， 115 115 然后使用鼠标中键进行粘帖。

+11 -11

Documentation/translations/zh_TW/admin-guide/sysrq.rst

reviewed

··· 60 60 ~~~~~~~~~~~~~~~~~~~~~~~ 61 61 62 62 在 x86 架構上 63 63 - 你可以按下鍵盤組合鍵 :kbd:`ALT-SysRq-<command key>`。 63 63 + 你可以按下鍵盤組合鍵 `ALT-SysRq-<command key>`。 64 64 65 65 .. note:: 66 66 一些鍵盤可能沒有標識 'SySRq' 鍵。'SySRq' 鍵也被當做 'Print Screen'鍵。 67 67 - 同時有些鍵盤無法處理同時按下這麼多鍵，因此你可以先按下鍵盤 :kbd:`Alt` 鍵， 68 68 - 然後按下鍵盤 :kbd:`SysRq` 鍵，再釋放鍵盤 :kbd:`SysRq` 鍵，之後按下鍵盤上命令鍵 69 69 - :kbd:`<command key>`，最後釋放所有鍵。 67 67 + 同時有些鍵盤無法處理同時按下這麼多鍵，因此你可以先按下鍵盤 `Alt` 鍵， 68 68 + 然後按下鍵盤 `SysRq` 鍵，再釋放鍵盤 `SysRq` 鍵，之後按下鍵盤上命令鍵 69 69 + `<command key>`，最後釋放所有鍵。 70 70 71 71 在 SPARC 架構上 72 72 - 你可以按下鍵盤組合鍵 :kbd:`ALT-STOP-<command key>` 。 72 72 + 你可以按下鍵盤組合鍵 `ALT-STOP-<command key>` 。 73 73 74 74 在串行控制檯（只針對 PC 類型的標準串口） 75 75 你可以發一個 ``BREAK`` ，然後在 5 秒內發送一個命令鍵， 76 76 發送 ``BREAK`` 兩次將被翻譯爲一個正常的 BREAK 操作。 77 77 78 78 在 PowerPC 架構上 79 79 - 按下鍵盤組合鍵 :kbd:`ALT - Print Screen` （或者 :kbd:`F13`） - :kbd:`<命令鍵>` 。 80 80 - :kbd:`Print Screen` （或者 :kbd:`F13`） - :kbd:`<命令鍵>` 或許也能實現。 79 79 + 按下鍵盤組合鍵 `ALT - Print Screen` （或者 `F13`） - `<命令鍵>` 。 80 80 + `Print Screen` （或者 `F13`） - `<命令鍵>` 或許也能實現。 81 81 82 82 在其他架構上 83 83 如果你知道其他架構的組合鍵，請告訴我，我可以把它們添加到這部分。 ··· 87 87 88 88 echo t > /proc/sysrq-trigger 89 89 90 90 - 這個命令鍵 :kbd:`<command key>` 是區分大小寫的。 90 90 + 這個命令鍵 `<command key>` 是區分大小寫的。 91 91 92 92 什麼是命令鍵？ 93 93 ~~~~~~~~~~~~~~ ··· 203 203 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 204 204 205 205 這也會發生在我這，我發現輕敲鍵盤兩側的 shift、alt 和 control 鍵，然後再次敲擊 206 206 - 一個無效的 SysRq 鍵序列可以解決問題。（比如，像鍵盤組合鍵 :kbd:`alt-sysrq-z` ） 207 207 - 切換到另一個虛擬控制檯（鍵盤操作 :kbd:`ALT+Fn` ），然後再切回來應該也有幫助。 206 206 + 一個無效的 SysRq 鍵序列可以解決問題。（比如，像鍵盤組合鍵 `alt-sysrq-z` ） 207 207 + 切換到另一個虛擬控制檯（鍵盤操作 `ALT+Fn` ），然後再切回來應該也有幫助。 208 208 209 209 我敲擊了 SysRq 鍵，但像是什麼都沒發生，發生了什麼錯誤？ 210 210 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ··· 259 259 文件的消費訪問到。作爲一個特例，來自 sysrq 命令的標題行將被傳遞給所有控制檯 260 260 使用者，就好像當前日誌級別是最大的一樣。如果只發出標題頭，則幾乎可以肯定內核日誌 261 261 級別太低。如果你需要控制檯上的輸出，那麼你將需要臨時提高控制檯日誌級別，通過使用 262 262 - 鍵盤組合鍵 :kbd:`alt-sysrq-8` 或者:: 262 262 + 鍵盤組合鍵 `alt-sysrq-8` 或者:: 263 263 264 264 echo 8 > /proc/sysrq-trigger 265 265

+4 -4

Documentation/translations/zh_TW/process/email-clients.rst

reviewed

··· 86 86 - :menuselection:`Do Not Send Flowed Text` 必須開啓 87 87 - :menuselection:`Strip Whitespace Before Sending` 必須關閉 88 88 89 89 - 當寫郵件時，光標應該放在補丁會出現的地方，然後按下 :kbd:`CTRL-R` 組合鍵，使指 89 89 + 當寫郵件時，光標應該放在補丁會出現的地方，然後按下 `CTRL-R` 組合鍵，使指 90 90 定的補丁文件嵌入到郵件中。 91 91 92 92 Claws Mail (GUI) ··· 94 94 95 95 可以用，有人用它成功地發過補丁。 96 96 97 97 - 用 :menuselection:`Message-->Insert File` (:kbd:`CTRL-I`) 或外置編輯器插入補丁。 97 97 + 用 :menuselection:`Message-->Insert File` (`CTRL-I`) 或外置編輯器插入補丁。 98 98 99 99 若要在Claws編輯窗口重修改插入的補丁，需關閉 100 100 :menuselection:`Configuration-->Preferences-->Compose-->Wrapping` ··· 106 106 一些開發者成功的使用它發送補丁。 107 107 108 108 撰寫郵件時： 109 109 - 從 :menuselection:`格式-->段落樣式-->預格式化` (:kbd:`CTRL-7`) 109 109 + 從 :menuselection:`格式-->段落樣式-->預格式化` (`CTRL-7`) 110 110 或工具欄選擇 :menuselection:`預格式化` ； 111 111 112 112 然後使用： 113 113 - :menuselection:`插入-->文本文件...` (:kbd:`ALT-N x`) 插入補丁文件。 113 113 + :menuselection:`插入-->文本文件...` (`ALT-N x`) 插入補丁文件。 114 114 115 115 你還可以 ``diff -Nru old.c new.c | xclip`` ，選擇 :menuselection:`預格式化` ， 116 116 然後使用鼠標中鍵進行粘帖。