I am currently working on expression evaluator for Godot debugger and I implemented a command history feature that is present pretty much in any console type of application. For those who aren't sure what I have in mind, when you enter the command in the console, I store it in history that I can browse later, in my case pressing up and down arrow keys, user can get back to previously entered commands.
I implemented this as a custom Control for the tool only. However, I wanted to ask whether this would be feature that other users would find useful too. If yes, I could move this to LineEdit.

_Illustration of current usage_
If you coded an already working feature, it would be probably better to create a PR, not an issue. Whether we need it also depends on how complex code it introduces. (feature-alone, looks useful to me, e.g. for chats)
I don't think this will be merged, the use case is too specific and is not needed in the editor.
@KoBeWi I implemented the feature as a custom Control node, not in the LineEdit. Moreover, I implemented it specifivally for my usecase, so I did not implement full generic API for it, only what I needed. Talking to Juan, he suggested opening an issue for this.
@groud Well, it is used in the editor now - it will be, better said. 馃榾 But I agree that the use case is quite specific. That's why I opened this issue, to see opinion of other users and contributors.
this is why gdscript exists! the power of gdscript interweaving with ui nodes is at full force in this thread! great job, it looks nice!
i also use this for my chat system. for example, in some games, you can cycle your past messages with the up arrow. store them in an array, cycle through with a counter, and set the lineedit's text. BAM!
Feature and improvement proposals for the Godot Engine are now being discussed and reviewed in a dedicated Godot Improvement Proposals (GIP) (godotengine/godot-proposals) issue tracker. The GIP tracker has a detailed issue template designed so that proposals include all the relevant information to start a productive discussion and help the community assess the validity of the proposal for the engine.
The main (godotengine/godot) tracker is now solely dedicated to bug reports and Pull Requests, enabling contributors to have a better focus on bug fixing work. Therefore, we are now closing all older feature proposals on the main issue tracker.
If you are interested in this feature proposal, please open a new proposal on the GIP tracker following the given issue template (after checking that it doesn't exist already). Be sure to reference this closed issue if it includes any relevant discussion (which you are also encouraged to summarize in the new proposal). Thanks in advance!
Most helpful comment
_Illustration of current usage_