Koichi Murase

The pathname completions are originally processed by [`_comp_xfunc_ssh_scp_local_files`](https://github.com/scop/bash-completion/blob/b85b88e55c15790a6e87933b7633f26992ce56e1/completions/ssh#L592). With this PR, filenames are doubly generated. ```bash $ scp ./COPYING[TAB twice] COPYING COPYING ```

I'm sorry. I just made a mistake. I intended to open a PR in my local repository for testing purpose.

Ah, sorry for confusing you. I reopened this on purpose, rebased it, and planned to add a description, but I became busy and left it in the current status [Note:...

I have converted this to Draft PR. I'll later add the description and make it again a (normal) PR. The original reason that I decided to reopen the PR at...

@carbongreat13 Thanks for checking!

Sorry for the delay. I'm a bit busy this week, so it may delay further.

I think the descriptions of the existing rules are fine. In addition, I have questions about the naming rules for the following cases (I have created separate threads in #539):...

This is because just the list hardcoded in `completions/cryptsetup` is not up to date: https://github.com/scop/bash-completion/blob/9cde158077ba70edecf2898696692a52d844d858/completions/cryptsetup#L43-L46 The upstream option parser is found here: https://gitlab.com/cryptsetup/cryptsetup/-/blob/main/src/cryptsetup.c#L3155-3208 https://gitlab.com/cryptsetup/cryptsetup/-/blob/main/src/cryptsetup.c#L2831-2867 https://gitlab.com/cryptsetup/cryptsetup/-/blob/main/src/cryptsetup_args.h#L28-53 The differences are ```diff ---...

@calestyo Could you review it?

Thanks for your review. @scop Sorry for making long discussion. You can just skip the section of "Bash language discussion". Bash language discussion First, for the comments on `eval` and...