precedence order for aliases
Bug #235432 reported by
Saša Janiška
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Hi!
I'm noticing some strange behaviour how Bazaar handles user-defined aliases and I'm not sure whether it is a bug or feature...
I defined one alias in ~/.bazaar/
[ALIASES]
checkout=checkout --lightweight
Invoking 'bzr help checkout' gives:
[...]
Aliases: co
See also: branch, checkouts
'bzr checkout' is an alias for 'bzr checkout --lightweight'.
and, therefore I'd expect that 'bzr co' would expand to 'bzr checkout' first and then to 'bzr checkout --lightweight', but it does not so.
Maybe it's a feature, but, imho, it's not orthogonal and I'd expect that user-defined alias is expanded as the last. Finally, the above help file output implies so ;)
Sincerely,
Gour
Changed in bzr: | |
status: | New → Invalid |
To post a comment you must log in.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Gour wrote:
> Public bug reported:
>
> Hi!
>
> I'm noticing some strange behaviour how Bazaar handles user-defined
> aliases and I'm not sure whether it is a bug or feature...
It's a feature. It keeps the model simple. It allows the aliases to
vary independently. It allows the original command be given an alias,
while an alias is created for the original name.
> [...]
> Aliases: co
> See also: branch, checkouts
> 'bzr checkout' is an alias for 'bzr checkout --lightweight'.
> Maybe it's a feature, but, imho, it's not orthogonal and I'd expect that
> user-defined alias is expanded as the last. Finally, the above help file
> output implies so ;)
I don't think so. User aliases and built-in aliases are completely
different.
Aaron enigmail. mozdev. org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://
iD8DBQFIPdy+ 0F+nu1YWqI0RAh1 kAJ9ag0Ail2ww3u 7SHUwW8pGxoQQEx wCffz83 toNW7SZ0=
iFO0EktI0SQhTZk
=m9wj
-----END PGP SIGNATURE-----