Improve Autocompletion

[GerdP]

When tagging guidepost I often have to enter several tag keys like
direction_north=*, direction_north:route=*, and direction_north:symbol, followed by similar tags for other directions. Sometimes I only need direction=*
Autocompletion too often suggests the longest match, e.g. when I start typing dir it may suggest key direction_northwest:symbol instead of only direction.
I typically have to either type a lot more characters or I use the cursor to get to wanted position. Both are time consuming.
Is there an option to tell JOSM that it should use the shortest match instead? So, e.g. suggest
direction when typing dir, and then, after typing "_n" it should suggest direction_north.
I think I have the same problem with tag keys like bicycle:left:surface, bicycle:left:traffic_sign etc.

If there is no such option: Wouldn't it be better to do this by default?

I think the same is true for tag values, e.g. the value for direction_northwest:symbol can be
train_station;none;train_station. Now, when I tag a differnt guidepost and enter the value for tag direction_northwest:symbol JOSM might suggest train_station;none;train_station instead of only train_station when I start typing "t" assuming that there is a tag direction_northwest:symbol=train_station in the data or in the presets.

[stoecker]

I think it's taking the first suggestion in the list and the longer ones with _ are probably before the shorter ones. Solution to this would be to change sorting or allow different sorting methods.

• alphabetical
• personal use count
• use count in database
• somehow weighted (i.e. is in presets, usage, ...)

[GerdP]

I'll have a closer look at the current implementation. Another approach is to change the way how Ctrl+Cursor left/right moves to the next position. It would help to stop at the special characters like ":" and "_".