When autocomplete list opens, sometimes is faster go to the last item moving UP instead of rolling all itens to down... It you are at the first and moves up, I think that it should go to the LAST item (as a cicle)
Not sure its a good idea because when the list possible items is longer than the menu a wraparound is to the last of an unknown number of items. There is no way of knowing if its shorter or not.
The cursor behaviour in the autocomplete menu is provided by the Scintilla editing widget, so it has to be added there, not to Geany.
Every good editor has this behaviour, for instance Netbeans. Supose you have 5 itens in autocomplete. with one key press you can reach the last or 5 hits, what is more efficient? If we go to the LAST you can return to the first, only press DOWN as it will wraps again the boundary, to first. Are you user or developer??
As I said, the behaviour of the autocomplete list movement is determined by the [Scintilla editing widget](https://www.scintilla.org/). This is a separate project and any change in the behaviour must be added there first and will be included in Geany when the appropriate version of Scintilla is included in Geany.
Other than scope based autocomplete, if you only have six items in the autocomplete list you are very lucky in my experience. Large amounts of "junk" options is very common making the list of options longer than the displayed menu. So if a user moves up they would wrap to an unknown item past the end of the displayed list.
Because of this a heroic heuristic has been added to try to order C/C++ autocompletes with the most likely first eg local variables, and that will be available at the next release of Geany. So the most likely should be at or near the top.
But if Scintilla adds the wraparound thats ok, nobody has to scroll up, I just don't think it will be very useful in real life.
How old are you? I program since the year 2000 and all you post is negative, shows bad will. NETBEANS USES THIS BEHAVIOR, so I don't think Netbeans developers had a less inteligent decision.
It seems you didn't understand the point. The example of a shor autocomplete with 6 items is when you type part of a VARIABLE NAME that you are creating.
It is inappropriate to abuse anybody contributing to any project no matter what their status in the project. An opinion is a personal position based on the contributors experience, just because that does not agree with your personal opinion is not an excuse for abuse.
If you had read my posts with less emotion you would have seen that they do __not__ say that the option should not be added, in fact I have pointed out the mechanism by which that has to happen, adding it to Scintilla first, and pointing out that will make it available when that version of Scintilla is imported.
type part of a VARIABLE NAME that you are creating.
Geany can't distinguish what type of name is being typed, it will show variables, functions, types, enumerations etc, anything with the same prefix. And if the autocomplete word option is on then the list will be all words in the document with the currently typed prefix. In my experience that tends to result in long lists. Your experience may differ.
Even Microsoft Code uses this behavior. I found abusive you saying that this feature may not be important or useful.
It is inappropriate to abuse anybody contributing to any project no matter what their status in the project. An opinion is a personal position based on the contributors experience, just because that does not agree with your personal opinion is not an excuse for abuse.
If you had read my posts with less emotion you would have seen that they do **not** say that the option should not be added, in fact I have pointed out the mechanism by which that has to happen, adding it to Scintilla first, and pointing out that will make it available when that version of Scintilla is imported.
type part of a VARIABLE NAME that you are creating.
Geany can't distinguish what type of name is being typed, it will show variables, functions, types, enumerations etc, anything with the same prefix. And if the autocomplete word option is on then the list will be all words in the document with the currently typed prefix. In my experience that tends to result in long lists. Your experience may differ.
_"tends to result in Long lists"_ = Your comment is in my favor, if the autocomplete has a long list we have one more reason to have a shortcut to navigate quickly the entire list edges.
tends to result in long lists
The maximum size of the autocomplete menu is set (default 10) but the list can be longer than that, so you can't see the end items. That is the issue with long lists, because a wrap will be blind to items that are not visible yet.
I am aware that VScode behaves this way, and when I accidentally scroll up too far and wrap it switches to some item that is not visible in the menu and is usually some rubbish system library thing that has no relationship to what I am typing, contributing to my opinion that wrapping autocompletes, especially prioritised ones, may not be very useful in unscoped situations.
I already said that the list is likely to be shorter in scoped autocompletes, but those tend to resolve to one very quickly in my experience, yours may differ.
As stated it is my opinion that it will not be very useful, it is entirely reasonable to state an opinion, even if it disagrees with yours. Accepting that others may have differing opinions is part of open source software development where people have significantly differing experiences and use-cases. Even someone with your limited experience (half of mine) is listened to and engaged with, even if disagreed with.
from the staff
There are no staff here, Geany is an entirely volunteer project, people contribute what they wish to use their own personal "spare" time for.
For me, after trying many good editors, for years, I found that it is fundamental !
Since all Geany contributors are volunteers they are likely to contribute what they find is important to them, irrespective of how important it is to you. So far nobody has found it so fundamental in either the Geany or Scintilla projects that they have contributed it.
But if it is so important to you then you can create a pull request to Scintilla to add the capability as I posted above, and then everybody can use it if they find it useful. At no time have I said it should not be implemented, just that I am of the opinion that it will not be very useful.
Scintilla [1495](https://sourceforge.net/p/scintilla/feature-requests/1495/) marked as `won't implement`. This can be reopened if that changes.
Closed #3546 as completed.
github-comments@lists.geany.org