1
0
mirror of https://github.com/mpv-player/mpv synced 2025-02-17 04:58:06 +00:00

github/issue_template: reword log file instructions

This commit is contained in:
der richter 2024-04-21 22:45:06 +02:00
parent 704863a016
commit 9f2590b6d1
5 changed files with 39 additions and 12 deletions

View File

@ -63,11 +63,17 @@ body:
label: "Log File" label: "Log File"
placeholder: "Drag and drop log file here (Don't paste content directly)" placeholder: "Drag and drop log file here (Don't paste content directly)"
description: > description: >
Make a log file made with `-v -v` or `--log-file=output.txt`, attach it to Make a log file with `--gpu-debug --log-file=output.txt`, which is our preferred way, and
the issue. attach it to the issue.
If you have trouble producing a log file, you can alternatively use `--gpu-debug -v -v`,
save the terminal output to a file, and attach it to the issue.
In the case of a crash, please provide a backtrace. In the case of a crash, please provide a backtrace.
Without the log file, this issue will be closed for ignoring the issue template. Without the log file, this issue will be closed for ignoring the issue template.
validations: validations:
required: true required: true

View File

@ -59,13 +59,18 @@ body:
label: "Log File" label: "Log File"
placeholder: "Drag and drop log file here (Don't paste content directly)" placeholder: "Drag and drop log file here (Don't paste content directly)"
description: > description: >
Make a log file made with `-v -v` or `--log-file=output.txt`, attach it to Make a log file with `--gpu-debug --log-file=output.txt`, which is our preferred way, and
the issue. If you use the Bundle, a default log is created for your last run at attach it to the issue. If you use the Bundle, a default log is created for your last run
`~/Library/Logs/mpv.log`. You can jump to that file via the `Help > Show log File…` at `~/Library/Logs/mpv.log`. You can jump to that file via the `Help > Show log File…` menu.
menu.
If you have trouble producing a log file, you can alternatively use `--gpu-debug -v -v`,
save the terminal output to a file, and attach it to the issue.
In the case of a crash, please provide the macOS Crash Report (Backtrace). In the case of a crash, please provide the macOS Crash Report (Backtrace).
Without the log file, this issue will be closed for ignoring the issue template. Without the log file, this issue will be closed for ignoring the issue template.
validations: validations:
required: true required: true

View File

@ -61,11 +61,17 @@ body:
label: "Log File" label: "Log File"
placeholder: "Drag and drop log file here (Don't paste content directly)" placeholder: "Drag and drop log file here (Don't paste content directly)"
description: > description: >
Make a log file made with `-v -v` or `--log-file=output.txt`, attach it to Make a log file with `--gpu-debug --log-file=output.txt`, which is our preferred way, and
the issue. attach it to the issue.
If you have trouble producing a log file, you can alternatively use `--gpu-debug -v -v`,
save the terminal output to a file, and attach it to the issue.
In the case of a crash, please provide a backtrace. In the case of a crash, please provide a backtrace.
Without the log file, this issue will be closed for ignoring the issue template. Without the log file, this issue will be closed for ignoring the issue template.
validations: validations:
required: true required: true

View File

@ -61,11 +61,17 @@ body:
label: "Log File" label: "Log File"
placeholder: "Drag and drop log file here (Don't paste content directly)" placeholder: "Drag and drop log file here (Don't paste content directly)"
description: > description: >
Make a log file made with `-v -v` or `--log-file=output.txt`, attach it to Make a log file with `--gpu-debug --log-file=output.txt`, which is our preferred way, and
the issue. attach it to the issue.
If you have trouble producing a log file, you can alternatively use `--gpu-debug -v -v`,
save the terminal output to a file, and attach it to the issue.
In the case of a crash, please provide a backtrace. In the case of a crash, please provide a backtrace.
Without the log file, this issue will be closed for ignoring the issue template. Without the log file, this issue will be closed for ignoring the issue template.
validations: validations:
required: true required: true

View File

@ -18,5 +18,9 @@ body:
label: "Log File" label: "Log File"
description: > description: >
Even if you think it's not necessary at first, it might help us later to find Even if you think it's not necessary at first, it might help us later to find
possible issues. Make a log file made with `-v -v` or `--log-file=output.txt` and possible issues. Make a log file with `--log-file=output.txt`, which is our preferred way,
attach it to the issue. and attach it to the issue.
If you have trouble producing a log file, you can alternatively use `-v -v`, save the
terminal output to a file, and attach it to the issue.