Skip to content

Default value of always_complete_options #538

@exploide

Description

@exploide

When I first triggered tab completions for a tool using argcomplete I was confused why it always suggests --option arguments. Later I discovered by accident that argcomplete.autocomplete() takes an optional parameter always_complete_options which by default is set to True.

This made me think: Is there any specific reason why it defaults to True? This is contrary to almost all other completion engines I know. Usually it requires you to type a - first before it completes options.

I think users are used to this behavior and I'm wondering why argcomplete does it different. This is half a question and half a suggestions. Feel free to reject if you prefer the current behavior. But I'm curious how that came. (My guess is that most developers incorporating argcomplete don't even know that they can alter this behavior.)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions