Bazaar

Possible arguments to config --scope are not documented

Bug #788991 reported by Eli Zaretskii
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Bazaar
Confirmed
Medium
Unassigned

Bug Description

The help text for the --scope option of "bzr config" does not say enough about what arguments are accepted. It says "Reduce the scope to the specified configuration file", but that doesn't mean I need to specify a file name
there, does it?

By experimenting, I found that 3 possible arguments are "bazaar", "locations", and "branch". But are these the only ones? In any case, I suggest that a full list of the possible arguments be part of the help text. Or maybe say that the argument can be any name of a supported .conf file with its leading directories and the extension stripped (and give one or two examples).

Revision history for this message
John A Meinel (jameinel) wrote :

I'm thinking this is just a dupe of bug #730905. At least, if we fix that one, it should fix this one. Though this one could be fixed independently by just updating the help text for config and inlining the possible options.

Revision history for this message
Vincent Ladeuil (vila) wrote :

Alsmot a dupe but not quite, this one requires not only a RegistryOption for the config command but also a proper registry to get the possible values from ;)

There is a work in progress towards both of these goals, tagging appropriately.

Changed in bzr:
importance: Undecided → Medium
status: New → Confirmed
tags: added: config doc
Revision history for this message
Vincent Ladeuil (vila) wrote :

> By experimenting, I found that 3 possible arguments are "bazaar", "locations", and "branch".

Out of curiosity, what did you try ? Why ? What would you consider obvious ?

> But are these the only ones?

So far, yes.

Revision history for this message
Eli Zaretskii (eliz) wrote :

> Out of curiosity, what did you try ?

I also tried "branch.conf" and "/path/to/branch.conf".

> Why ?

Because the documentation says "Reduce the scope to the specified configuration file". This could be interpreted as meaning that the option expects me to specify a file name.

> What would you consider obvious ?

Nothing is obvious here, at least not for me.

Jelmer Vernooij (jelmer)
tags: added: check-for-breezy
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.