Skip to content

Update bash completion options for --pdf-engine#11555

Closed
lodwicz wants to merge 1 commit intojgm:mainfrom
lodwicz:patch-1
Closed

Update bash completion options for --pdf-engine#11555
lodwicz wants to merge 1 commit intojgm:mainfrom
lodwicz:patch-1

Conversation

@lodwicz
Copy link
Copy Markdown
Contributor

@lodwicz lodwicz commented Mar 27, 2026

Removed 'pdfroff' from the list of options for --pdf-engine, to avoid lookup for pdfroff.exe win executable on cygwin, and enable native cygwin script...

The alternative groff -Tpdf groff engine is not enumerated, and runs perfectly well on cygwin without searching for a Win executable.

Removed 'pdfroff' from the list of options for --pdf-engine, to avoid lookup for `pdfroff.exe` win executable on cygwin, and enable native cygwin script...
Copy link
Copy Markdown
Contributor

@alerque alerque left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This completion script affects all platforms, no? It seems like you're trying to solve a platform and environment specific problem with a change that will affect many other scenarios that might already work properly as collateral damage.

@lodwicz
Copy link
Copy Markdown
Contributor Author

lodwicz commented Mar 27, 2026

it seems to me that this bash completion is redundant, since appending the .exe extension affects only windows executables, and windows does not support bash (for pdfroff) completion: being a shell script, there is no direct executable required on *ix, or it should be provided separately for windows, the same as gropdf, the script for the alternative groff pdf-engine, which is a perl script. Again: either (both) should be provided with bat or exe stubs to run on windows.

@alerque
Copy link
Copy Markdown
Contributor

alerque commented Mar 27, 2026

What are you talking about? The code you removed isn't adding or using an exe extension in the first place.

@lodwicz
Copy link
Copy Markdown
Contributor Author

lodwicz commented Mar 28, 2026

my apologies: the issue is that pdfroff is no longer distributed with groff 1.24.x (discussed 2024-11-15; announced 28 feb 2026), so it could be removed; the executable extension appended came from older code.

the engine supported now by default by groff is the option -Tpdf as currently documented.

@jgm
Copy link
Copy Markdown
Owner

jgm commented Mar 28, 2026

If we only had to support Windows, this change might make sense. But since there are other platforms that have pdfroff, it doesn't...

@jgm jgm closed this Mar 28, 2026
@lodwicz
Copy link
Copy Markdown
Contributor Author

lodwicz commented Mar 28, 2026

my apologies: the issue is that pdfroff is no longer distributed with groff 1.24.x (discussed 2024-11-15; announced 28 feb 2026), so it could be removed; the executable extension appended came from older code.

the engine supported now by default by groff is the option -Tpdf as currently documented.

perhaps the change should be to add the groff engine, which is now the supported engine by default by groff itself...

jgm added a commit that referenced this pull request Mar 28, 2026
@jgm
Copy link
Copy Markdown
Owner

jgm commented Mar 28, 2026

Good idea, I'll do that.

@lodwicz lodwicz deleted the patch-1 branch March 28, 2026 05:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants