0000572: When `file` is used on a path that doesn't exist, the output contains both a backtick and quotation mark.

ID	Project	Category	View Status	Date Submitted	Last Update

0000572	file	General	public	2024-12-01 19:09	2024-12-19 15:29

Reporter	BEEDELLROKEJULIANLOCKHART	Assigned To	christos
Priority	low	Severity	text	Reproducibility	always
Status	assigned	Resolution	open
Product Version	5.45

Summary	0000572: When `file` is used on a path that doesn't exist, the output contains both a backtick and quotation mark.
Description	When `file` is used on a path that doesn't exist, the output (as undermentioned) contains both a backtick and quotation mark: > non-existent: cannot open `non-existent' (No such file or directory) It should only contain one. This matters because it breaks in-line Markdown (and isn't syntactically correct in English).
Steps To Reproduce	~~~bash #!/usr/bin/env -S bash file 'non-existent' ~~~
Additional Information	1. `dnf5 repoquery --whatprovides 'file'` returns `file-0:5.45-7.fc41.x86_64`. 2. `rpm -qa file` returns `file-5.45-7.fc41.x86_64` too.
Tags	No tags attached.

christos 2024-12-05 19:46 manager ~0004120	This is what many Unix programs do: cd /usr/bin && strings '`%s' * (in some fonts the quote is right quote and they are trying to be cute and print <left-quote>name<right-quote>)

BEEDELLROKEJULIANLOCKHART 2024-12-05 21:56 reporter ~0004121	I presume it's a pre-Unicode hack? In UTF-8, "‘" and "’" provide this, semantically.

christos 2024-12-19 15:29 manager ~0004136	Yup, it is from the US ASCII only days.

Date Modified	Username	Field	Change
2024-12-01 19:09	BEEDELLROKEJULIANLOCKHART	New Issue
2024-12-05 19:44	christos	Assigned To	=> christos
2024-12-05 19:44	christos	Status	new => assigned
2024-12-05 19:46	christos	Status	assigned => feedback
2024-12-05 19:46	christos	Note Added: 0004120
2024-12-05 21:56	BEEDELLROKEJULIANLOCKHART	Note Added: 0004121
2024-12-05 21:56	BEEDELLROKEJULIANLOCKHART	Status	feedback => assigned
2024-12-19 15:29	christos	Note Added: 0004136