qswitch: Branch compleater should suggest relative paths.
Bug #412089 reported by
Gary van der Merwe
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
QBzr |
Confirmed
|
Medium
|
Unassigned |
Bug Description
If this is my directory structure:
~/qbzr/
trunk/
feature1/
feature2/
workingarea/
qbzr/
and I am in ~/qbzr/
I can pass bzr switch a path relative to the current directory:
bzr switch ../../feature1
or relative to the repository:
bzr switch feature1
The branch completer should be able to suggest these.
Changed in qbzr: | |
importance: | Undecided → Medium |
status: | New → Confirmed |
To post a comment you must log in.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Gary van der Merwe wrote: workingarea/ qbzr/,
> Public bug reported:
>
> If this is my directory structure:
>
> ~/qbzr/
> trunk/
> feature1/
> feature2/
> workingarea/
> qbzr/
>
> and I am in ~/qbzr/
>
> I can pass bzr switch a path relative to the current directory:
> bzr switch ../../feature1
>
> or relative to the repository:
> bzr switch feature1
>
> The branch completer should be able to suggest these.
>
Actually, not relative to the repository, it is actually locally
relative to the current branch.
So if you have:
~/qbzr/
trunk/
branches/
feature1
feature2
weird-feature3
work => ../trunk
I believe you can then do:
bzr switch weird-feature3
or
bzr switch branches/feature1
note that if we change the target to '../branches/ feature1' then you can do:
bzr switch feature2
but there is no short form to supply 'trunk' or 'weird-feature3' because
they are up a level, and passing ".." would trigger the local path
check. (of course, '../trunk' is still valid, but that is because it is
relative to 'work' not 'feature1')
John enigmail. mozdev. org/
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://
iEYEARECAAYFAkq DIeAACgkQJdeBCY SNAAOOmACbBd8kt PbZezMjfMRi288B D+gj rsdDjBwkMBV5gxv nq
sEYAnAkONSTfyiU
=oADu
-----END PGP SIGNATURE-----