Open priyashpatil opened 1 week ago
@priyashpatil I think what's happening is that we're not recognizing cmd+L when the cursor is already inside of the input box. Is this consistent with what you're seeing?
@sestinj Can confirm: if input is focused then cmd+L doesn't work.
Also there another related bug, duplicating added context:
first bug fixed by https://github.com/continuedev/continue/pull/2834 second bug fixed by https://github.com/continuedev/continue/pull/2842
@RomneyDa the new pre-release has fixed the above mentioned bugs but there's another related bug:
This closes the chat sidebar and this seems to be issue on only new Chats.
@priyashpatil was able to duplicate
I kind of feel like this should be normal behavior, and that in this case if people want to clear the box they should just hit delete or cmd + delete
I guess the question is if you had just pulled some code into the chat with Cmd + shift + L and then you hit CMD + L, would you expect it to start a new session with no input? Or to start a new session without changing the input? My intuition is with the new input, because anything in the input feels "unsaved", and to delete it you should manually hit delete (cmd L saves last session)
Thoughts?
@RomneyDa if CMD+L is supposed to start a new chat but if already on a new chat, I think it should ignore the keystroke instead of closing the chat window.
Before submitting your bug report
Relevant environment info
Description
CMD+L doesn't work when you have already started a chat and then try to start another chat by adding block context.
To reproduce
Log output
No response