config doesn't provide a --section parameter

Depending on the option, the user may want to decide in which section of locations.conf (or any other config file with sections) he wants the option to be defined in.

The plan is to provide a '--section' parameter once the sections themselves are clearly defined (most use cases use paths as section identifiers but regexps or user names or host names or whatever have also been mentioned).

I wonder if the user really directly wants to ask for a section.
Perhaps more likely is 'config --location PATH_GLOB ...'

Certainly being able to get at the functionality somehow would be good.

Martin

My assumption is that a section is not necessarily a location. A location is (at least in locations.conf) a glob that could match *several* sections and what is needed here is to identify *one* section without ambiguity.

And there can be other usages for section names than paths/locations.

On 4 April 2011 18:11, Vincent Ladeuil <email address hidden> wrote:
> My assumption is that a section is not necessarily a location. A
> location is (at least in locations.conf) a glob that could match
> *several* sections and what is needed here is to identify *one* section
> without ambiguity.
>
> And there can be other usages for section names than paths/locations.

I agree with all that. I think, perhaps separately from this bug, it
may be useful for the user to say "for everything under ~/work, set
foo=bar" without so much getting into that being one section in the
locations config.

> I agree with all that. I think, perhaps separately from this bug, it
> may be useful for the user to say "for everything under ~/work, set
> foo=bar" without so much getting into that being one section in the
> locations config.

'bzr config -d ~/work --scope locations foo=bar' works with bzr @ revno 6278 by adding:

   [/home/vila/work]
  foo = bar

At the end of locations.conf if the section doesn't exist yet.

This bug still applies though.