You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PROBLEM:
Multiline input In Aider is really cumbersome. The {} syntax is messy and many times one forgets about it and presses ENTER to write a new line, with the effect of sending an incomplete and easy-to-misunderstand message to the LLM, that would start to do its job in the wrong way messing many lines of code before we can stop it. Not only that, but the use of {} mixes with the {} in the javascript code, causing a mess.
SOLUTION:
Drop the {} syntax completely, and use SHIFT+ENTER to send the input to the LLM instead of ENTER. ENTER should simply add a line break without sending, allowing the user to write multiline input.
Why not use SHIFT+ENTER to send, you ask? The most common (and wrong) solution for implementing multiline input is to use SHIFT+ENTER to send a new line character or line break, leaving to the normal ENTER key the function to send the text. BUT THAT IS THE WRONG APPROACH. Because with that solution, if I PASTE a text with few lines of code, only the first line is sent, then it returns the control to the LLM, leaving out all the remaining lines of code. Sometimes those lines of code remain in the buffer and are sent one line at a time every time the prompt returns to the user, blocking the user interaction until all the LLM responses are done. A disaster. This is why SHIFT+ENTER is the best choice to send, while ENTER should simply add a line break without sending. Simple and effective, since it also mitigates accidental sends.
The text was updated successfully, but these errors were encountered:
Note that there is no portable way for a CLI tool to receive SHIFT+ENTER. Aider uses META+ENTER, which is often Esc ENTER in many terminal environments.
PROBLEM:
Multiline input In Aider is really cumbersome. The {} syntax is messy and many times one forgets about it and presses ENTER to write a new line, with the effect of sending an incomplete and easy-to-misunderstand message to the LLM, that would start to do its job in the wrong way messing many lines of code before we can stop it. Not only that, but the use of {} mixes with the {} in the javascript code, causing a mess.
SOLUTION:
Drop the {} syntax completely, and use SHIFT+ENTER to send the input to the LLM instead of ENTER. ENTER should simply add a line break without sending, allowing the user to write multiline input.
Why not use SHIFT+ENTER to send, you ask? The most common (and wrong) solution for implementing multiline input is to use SHIFT+ENTER to send a new line character or line break, leaving to the normal ENTER key the function to send the text. BUT THAT IS THE WRONG APPROACH. Because with that solution, if I PASTE a text with few lines of code, only the first line is sent, then it returns the control to the LLM, leaving out all the remaining lines of code. Sometimes those lines of code remain in the buffer and are sent one line at a time every time the prompt returns to the user, blocking the user interaction until all the LLM responses are done. A disaster.
This is why SHIFT+ENTER is the best choice to send, while ENTER should simply add a line break without sending. Simple and effective, since it also mitigates accidental sends.
The text was updated successfully, but these errors were encountered: