uru changes order of options once one is selected
The list of options seems to be affected by the selection of versions.
See the following output for a real-life example:
C:\Users\Luis>uru 214
---> these rubies match your `214` tag:
[1] 214p265-x64 : ruby 2.1.4p265 (2014-10-27 revision 48166) [x64-mingw32]
Home: C:\Users\Luis\Tools\Ruby\ruby-2.1.4-x64-mingw32\bin
[2] 214p265 : ruby 2.1.4p265 (2014-10-27 revision 48166) [i386-mingw32]
Home: C:\Users\Luis\Tools\Ruby\ruby-2.1.4-i386-mingw32\bin
select [1]-[2] to use that specific ruby (0 to exit) [0]: 2
---> Now using ruby 2.1.4-p265 tagged as `214p265`
C:\Users\Luis>uru 214
---> these rubies match your `214` tag:
[1] 214p265 : ruby 2.1.4p265 (2014-10-27 revision 48166) [i386-mingw32]
Home: C:\Users\Luis\Tools\Ruby\ruby-2.1.4-i386-mingw32\bin
[2] 214p265-x64 : ruby 2.1.4p265 (2014-10-27 revision 48166) [x64-mingw32]
Home: C:\Users\Luis\Tools\Ruby\ruby-2.1.4-x64-mingw32\bin
select [1]-[2] to use that specific ruby (0 to exit) [0]:
Every time one option is selected, the order in which the options are offered is altered, not allowing you to use mnemonic memory to consistently choose one version of Ruby :-)
It will be great if uru kept the order of the versions to avoid these changes.
Thank you!
Comments (7)
-
repo owner -
repo owner -
assigned issue to
-
assigned issue to
-
repo owner Please try this version and let me know if behaves as you would like.
EDIT: removed link to outdated testing release
-
repo owner Skip my previous
0.7.6.alpha.2
and try out this0.7.6.alpha.3
version.The selection display is stable and now uses the same sorting code as
uru ls
; it sorts by the user provided tag label rather than the internal tag identifier as in0.7.6.alpha.2
. -
reporter Hello, sorry for the delay.
Wanted to let you know this version works consistently!
C:\Users\Luis>uru 214 ---> these rubies match your `214` tag: [1] 214p265 : ruby 2.1.4p265 (2014-10-27 revision 48166) [i386-mingw32] Home: C:\Users\Luis\Tools\Ruby\ruby-2.1.4-i386-mingw32\bin [2] 214p265-x64 : ruby 2.1.4p265 (2014-10-27 revision 48166) [x64-mingw32] Home: C:\Users\Luis\Tools\Ruby\ruby-2.1.4-x64-mingw32\bin select [1]-[2] to use that specific ruby (0 to exit) [0]: 2 ---> Now using ruby 2.1.4-p265 tagged as `214p265-x64` C:\Users\Luis>uru 214 ---> these rubies match your `214` tag: [1] 214p265 : ruby 2.1.4p265 (2014-10-27 revision 48166) [i386-mingw32] Home: C:\Users\Luis\Tools\Ruby\ruby-2.1.4-i386-mingw32\bin [2] 214p265-x64 : ruby 2.1.4p265 (2014-10-27 revision 48166) [x64-mingw32] Home: C:\Users\Luis\Tools\Ruby\ruby-2.1.4-x64-mingw32\bin select [1]-[2] to use that specific ruby (0 to exit) [0]: 1 ---> Now using ruby 2.1.4-p265 tagged as `214p265`
Thank you!
-
reporter - edited description
-
repo owner - changed status to closed
Make SortTagsByTagLabel reusable. Closes
#64→ <<cset aac66cba4147>>
- Log in to comment
That is irritating behavior ;) I'm guessing it is due to how go does not guarantee order when iterating its map structures.
I'll look into making things more sane.