notgne2/tuxpaint-pencil-sharpener
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Sync SIGNALS doc after style updates

Browse source
This commit is contained in:
Bill Kendrick 2022-03-31 22:51:19 -07:00
parent 799670ac24
commit 084adab616
10 changed files with 689 additions and 351 deletions
Download patch file Download diff file Expand all files Collapse all files

20
docs/es_ES.UTF-8/SIGNALS.txt
View file

@ -5,9 +5,7 @@
Copyright © 2019-2022 by various contributors; see AUTHORS.txt.
https://tuxpaint.org/
enero 20, 2022
----------------------------------------------------------------------
marzo 31, 2022
Tux Paint responds to the following signals (which can be sent to the
program's process via `kill` or `killall`, for example).
@ -27,13 +25,13 @@
respectively), whether or not to overwrite the existing drawing,
or save to a new file.
Note: From other parts of the interface, the signal is currently
Example: 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.
Example: killall tuxpaint
SIGUSR1 & SIGUSR2
Tux Paint responds by setting its auto-save option (as if it had
@ -47,9 +45,9 @@
So, from the main interface, Tux Paint should quit almost
immediately, with no questions asked.
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.
Example: 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.