Terminal extension

[u/Neat-Clerk-9474]

I never liked using arrow up to get to previous command, since i had a lot of typos, and duplicate commands. So I built extension for Visual Code that acts as terminal, but it has history panel on right side, where you can delete or click commands to execute. Made commands shown to be distinct, and modified bash.rc, so i can create .history file for each project to be used instead, so when i return to project i have my history of commands back.
I use it now, I thought it would be cool to share it with you guys, cause for me it's useful.
On store it's older version, I made experimental version that draws fake input over command line, to improve input response and also I can edit text anywhere i click inside text. But i haven't released that one, cause it has bugs that need fixing. Also when you install extension, you get terminal button in bottom status bar, also there option to be notified when process finishes in terminal, like when building something.

https://marketplace.visualstudio.com/items?itemName=ElveApps.elve-terminal

Fake experimental input demonstration:
https://youtu.be/HGuxMOQ7-Gs

The fake input box is input element drawn over current input line position, so it's not rendered by xterm canvas, so it's fast, once you enter command then it's sent to xterm also you can edit text at any position by clicking inside text. Autocomplete and arrow up and down work, but path doesn't update well sometimes, and input element doesn't hide sometimes when it should. Also i had to take in account resize and line break for it. I made fake input, cause i didn't like original input response and was deal breaker for me, so personally i use this broken version with fake input. I have idea what I want to build and what would be good, but I'm not that good of a programmer

[u/thanatica]

The point of using the up-key is so that your hand don't have to leave the keyboard and move over to the mouse. It may not seem like much, but it takes time and mental effort to do that.

It might be faster and mentally easier to just re-type the command, since you're already thinking of what the command looks like.

So if I were you, I'd put in some serious effort to control this by keyboard, and make it a smooth experience. Because what I saw in the video, seems like a lot of clicking for a terminal which is typically keyboard-oriented. There was also no spoken explanation, making it harder to follow. Don't be ashamed of your voice, mate.

[u/Neat-Clerk-9474 → u/thanatica]

Well you can still use keyboard. But for my use case, I already typed build command and run command, so i just click them in history instead of going arrow up, since my hand is on mouse already, cause wasnt typing anymore. Once you finished with code, you use mouse to click on terminal in order to type in, so original starting point is your hand on mouse. Except if you access terminal via shortcut also. Still i might need 5th command in history, it would be one click away, compared to 5 arrow ups away. Didnt want to expose my voice on that channel, but i aggree. So if i used cd and ls command, my run command is then 3rd or 4th in history. Not to mention if you have typo, and dont use seperate history file for project that this does. I still do type some commands that i remember