File: SIGNALS.txt

package info (click to toggle)
tuxpaint 1%3A0.9.35-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 64,512 kB
  • sloc: ansic: 62,209; makefile: 1,425; sh: 790; objc: 303; cpp: 186; python: 182; php: 43
file content (57 lines) | stat: -rw-r--r-- 2,422 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
                                   Tux Paint
                               バージョン 0.9.35
                             Signals Documentation

       Copyright © 2019-2022 by various contributors; AUTHORS.txt 参照.
                             https://tuxpaint.org/

                                 2022年6月 4日

Tux Paint responds to the following signals (which can be sent to the program's
process via `kill` or `killall`, for example).

→ SIGTERM (also, [Control] + [C] from a terminal running `tuxpaint`) ←

    Tux Paint responds as if the "Quit" button were pressed, or the desktop
    environment was told to close Tux Paint (e.g., by clicking a window close
    button, or pressing [Alt] + [F4] on most systems).

    From the main interface, Tux Paint will prompt whether or not you wish to
    quit, and (unless overridden by the auto-save option, e.g. "--autosave") if
    you'd like to save the current drawing (if unsaved), and if so, and it's a
    modified version of an existing drawing (unless overridden by the options
    to save over old images, or always save new images; e.g. "--saveover" and
    "--saveovernew", respectively), whether or not to overwrite the existing
    drawing, or save to a new file.

    例: killall tuxpaint

    💡 Note: From other parts of the interface, the signal is currently
    interpreted as a request to go back (e.g., from the "New" dialog back to
    the main interface), as if a "Back" button in Tux Paint were clicked, or
    the [Esc] was key pressed.


     
→ SIGUSR1 & SIGUSR2 ←

    Tux Paint responds by setting its auto-save option (as if it had been
    launched with "--autosave"), as well as either the option to always save
    new images (as if launched with "--saveovernew") in the case of receiving a
    SIGUSR1 signal, or to always save over the existing image (as if launched
    with "--saveover") in the case of receiving SIGUSR2. Then Tux Paint sends
    itself a SIGTERM signal, in an attempt to quit. (See above.)

    So, from the main interface, Tux Paint should quit almost immediately, with
    no questions asked.

    例: killall -s SIGUSR1 tuxpaint

    💡 Note: From other parts of the interface, unfortunately, Tux Paint will go
    back one level in the interface. Therefore, at this time, it may be
    necessary to send this signal to Tux Paint a few times, for it to quit
    completely.