[OpenAFS-devel] Exploring approach for OpenAFS shell completion support

[Vaibhav Sharma]

--0000000000001e722b064c947f9d
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hello,

I recently joined the mailing list and I=E2=80=99m interested in contributi=
ng to
OpenAFS, particularly the proposed project on implementing shell completion
for OpenAFS commands (GSOC-2026, Idea list).

I have experience working with C and shell environments, and recently built
an offline AI-based shell assistant that interacts with CLI tools. Because
of that, the idea of improving the usability of OpenAFS command-line tools
caught my attention.

I=E2=80=99ve started exploring the OpenAFS repository and the available CLI=
 tools
to understand how command parsing and options are currently implemented.

Before going deeper, I wanted to ask:

1. Which command implementations would be the best starting point for
studying how CLI arguments and subcommands are defined?
2. Is there any existing work or discussion around generating shell
completions automatically from the command definitions?

Any pointers on where to start in the codebase would be greatly appreciated=
.

Thanks for your time.

Best regards,
Vaibhav Sharma

--0000000000001e722b064c947f9d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br>Hello,<br><br>I recently joined the mailing list and I=
=E2=80=99m interested in contributing to OpenAFS, particularly the proposed=
 project on implementing shell completion for OpenAFS commands (GSOC-2026, =
Idea list).<br><br>I have experience working with C and shell environments,=
 and recently built an offline AI-based shell assistant that interacts with=
 CLI tools. Because of that, the idea of improving the usability of OpenAFS=
 command-line tools caught my attention.<br><br>I=E2=80=99ve started explor=
ing the OpenAFS repository and the available CLI tools to understand how co=
mmand parsing and options are currently implemented.<br><br>Before going de=
eper, I wanted to ask:<br><br>1. Which command implementations would be the=
 best starting point for studying how CLI arguments and subcommands are def=
ined?<br>2. Is there any existing work or discussion around generating shel=
l completions automatically from the command definitions?<br><br>Any pointe=
rs on where to start in the codebase would be greatly appreciated.<br><br>T=
hanks for your time.<br><br>Best regards,<br>Vaibhav Sharma<br></div>

--0000000000001e722b064c947f9d--