github-mirror/fish-shell
2
0
Fork 0
mirror of https://github.com/fish-shell/fish-shell.git synced 2024-11-29 05:03:46 +08:00
Code Issues Actions 4 Packages Projects Releases Wiki Activity
4c46faea99
fish-shell/share/functions/fish_job_summary.fish

57 lines
2.8 KiB
Fish
Raw Normal View History

Also call `fish_job_summary` for foreground sigint The default implementation will not print any output in that case, but this provides users with additional flexibility when it comes to customising the shell's behaviour.
2020-05-01 03:15:29 +08:00
function fish_job_summary -a job_id is_foreground cmd_line signal_or_end_name signal_desc proc_pid proc_name
Add `fish_job_summary`, called whenever a job ends, stops, or is signalled This allows users to customise the behaviour of the shell by redefining the function. This is similar to how fish_title or fish_greeting behave, where the default implementation can be easily overridden. The function receives as arguments the job id, command line, signal name and signal description.
2020-04-30 12:14:12 +08:00
# job_id: ID of the job that stopped/terminated/ended.
Also call `fish_job_summary` for foreground sigint The default implementation will not print any output in that case, but this provides users with additional flexibility when it comes to customising the shell's behaviour.
2020-05-01 03:15:29 +08:00
# is_foreground: 1 if the job was running in the foreground, 0 otherwise.
Add `fish_job_summary`, called whenever a job ends, stops, or is signalled This allows users to customise the behaviour of the shell by redefining the function. This is similar to how fish_title or fish_greeting behave, where the default implementation can be easily overridden. The function receives as arguments the job id, command line, signal name and signal description.
2020-04-30 12:14:12 +08:00
# cmd_line: The command line of the job.
# signal_or_end_name: If terminated by signal, the name of the signal (e.g. SIGTERM).
# If ended, the string "ENDED". If stopped, the string "STOPPED".
# signal_desc: A description of the signal (e.g. "Polite quite request").
# Not provided if the job stopped or ended without a signal.
# If the job has more than one process:
# proc_pid: the pid of the process affected.
# proc_name: the name of that process.
# If the job has only one process, these two arguments will not be provided.
Also call `fish_job_summary` for foreground sigint The default implementation will not print any output in that case, but this provides users with additional flexibility when it comes to customising the shell's behaviour.
2020-05-01 03:15:29 +08:00
# Print nothing if we get SIGINT in the foreground process group, to avoid spamming
# obvious stuff on the console (#1119). If we get SIGINT for the foreground
# process, assume the user typed ^C and can see it working. It's possible they
# didn't, and the signal was delivered via pkill, etc., but the SIGINT/SIGTERM
# distinction is precisely to allow INT to be from a UI
# and TERM to be programmatic, so this assumption is keeping with the design of
# signals. If echoctl is on, then the terminal will have written ^C to the console.
# If off, it won't have. We don't echo ^C either way, so as to respect the user's
# preference.
git completions: undo mistaken `set -f` usage and fix issue in __fish_git_needs_command
2022-10-28 16:14:45 +08:00
if test "$signal_or_end_name" = SIGINT; and test $is_foreground -eq 1
Also call `fish_job_summary` for foreground sigint The default implementation will not print any output in that case, but this provides users with additional flexibility when it comes to customising the shell's behaviour.
2020-05-01 03:15:29 +08:00
return
end
Add `fish_job_summary`, called whenever a job ends, stops, or is signalled This allows users to customise the behaviour of the shell by redefining the function. This is similar to how fish_title or fish_greeting behave, where the default implementation can be easily overridden. The function receives as arguments the job id, command line, signal name and signal description.
2020-04-30 12:14:12 +08:00
set -l max_cmd_len 32
Also convert fish_job_summary
2022-08-20 02:26:10 +08:00
set cmd_line (string shorten -m$max_cmd_len -- $cmd_line)
Add `fish_job_summary`, called whenever a job ends, stops, or is signalled This allows users to customise the behaviour of the shell by redefining the function. This is similar to how fish_title or fish_greeting behave, where the default implementation can be easily overridden. The function receives as arguments the job id, command line, signal name and signal description.
2020-04-30 12:14:12 +08:00
fish_job_summary: Format message better for multiline prompts This was supposed to be number of lines in the prompt minus 1, but string repeat added one. Also it triggered even in case of the stopped job message, which is already repainted differently. So we add it when we need to repaint ourselves. As a bonus add a newline before in that case so the message isn't awkwardly printed into the commandline. Fixes #9044.
2022-06-28 23:53:39 +08:00
if test $is_foreground -eq 0; and test $signal_or_end_name != STOPPED
# Add a newline *before* our message so we get the message after the commandline.
echo >&2
end
Add `fish_job_summary`, called whenever a job ends, stops, or is signalled This allows users to customise the behaviour of the shell by redefining the function. This is similar to how fish_title or fish_greeting behave, where the default implementation can be easily overridden. The function receives as arguments the job id, command line, signal name and signal description.
2020-04-30 12:14:12 +08:00
switch $signal_or_end_name
Run fish_indent on all fish files in share/
2020-05-20 02:41:47 +08:00
case STOPPED
Add `fish_job_summary`, called whenever a job ends, stops, or is signalled This allows users to customise the behaviour of the shell by redefining the function. This is similar to how fish_title or fish_greeting behave, where the default implementation can be easily overridden. The function receives as arguments the job id, command line, signal name and signal description.
2020-04-30 12:14:12 +08:00
printf ( _ "fish: Job %s, '%s' has stopped\n" ) $job_id $cmd_line
Run fish_indent on all fish files in share/
2020-05-20 02:41:47 +08:00
case ENDED
Add `fish_job_summary`, called whenever a job ends, stops, or is signalled This allows users to customise the behaviour of the shell by redefining the function. This is similar to how fish_title or fish_greeting behave, where the default implementation can be easily overridden. The function receives as arguments the job id, command line, signal name and signal description.
2020-04-30 12:14:12 +08:00
printf ( _ "fish: Job %s, '%s' has ended\n" ) $job_id $cmd_line
case 'SIG*'
if test -n "$proc_pid"
printf ( _ "fish: Process %s, '%s' from job %s, '%s' terminated by signal %s (%s)\n" ) \
$proc_pid $proc_name $job_id $cmd_line $signal_or_end_name $signal_desc
else
printf ( _ "fish: Job %s, '%s' terminated by signal %s (%s)\n" ) \
$job_id $cmd_line $signal_or_end_name $signal_desc
end
end >&2
Call fish_prompt after background job finishes We don't need to call it if a job was stopped, because in that case read_i() will fire fish_prompt already, because the newly stopped job was probably a foreground job. Fixes #1018
2020-05-22 23:45:40 +08:00
if test $is_foreground -eq 0; and test $signal_or_end_name != STOPPED
fish_job_summary: Format message better for multiline prompts This was supposed to be number of lines in the prompt minus 1, but string repeat added one. Also it triggered even in case of the stopped job message, which is already repainted differently. So we add it when we need to repaint ourselves. As a bonus add a newline before in that case so the message isn't awkwardly printed into the commandline. Fixes #9044.
2022-06-28 23:53:39 +08:00
# We want one newline per line in the prompt after the first.
# To ensure that, don't let `string repeat` add a newline. See #9044.
string repeat -N \n --count=(math (count (fish_prompt)) - 1) >&2
Call fish_prompt after background job finishes We don't need to call it if a job was stopped, because in that case read_i() will fire fish_prompt already, because the newly stopped job was probably a foreground job. Fixes #1018
2020-05-22 23:45:40 +08:00
commandline -f repaint
end
Add `fish_job_summary`, called whenever a job ends, stops, or is signalled This allows users to customise the behaviour of the shell by redefining the function. This is similar to how fish_title or fish_greeting behave, where the default implementation can be easily overridden. The function receives as arguments the job id, command line, signal name and signal description.
2020-04-30 12:14:12 +08:00
end
Reference in New Issue Copy Permalink