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
Since this issue is #1 on google, I have exact same questions:
what is Smart send?
how to turn it off?
Looks like it invokes randomly, but has no traces in command palette or keyboard shortcuts.. and has a sneaky name also, like is my code sent somewhere based on some involuntarily invoked condition? So many questions without answers.
Smart send is triggered via key binding shift+enter
You may find little description of it in the settings itself where you could also turn off the setting.
If you turn off the setting for smart send, every instance of shift+enter will send things to terminal exactly as you specify/highlight or just a single line if you shift enter on a blank line.
Feel free to turn off this setting in by easily clicking on your settings icon and then searching for 'smart send'
tldr; I have tried on several occasions to find the documentation that matches the explanation provide by anthonykim1. Finally, I know how to activate/deactivate it.
I like the Smart Send. I have accidentally turned it off before. I could find nothing that explained how to change it's status. I just got the message referenced by OP, recognized it, and searched for it, and ended up here. This is the first time I have found anything approaching documentation that explains how to change it. I have looked all over stackoverflow for answers and tried different macros and other JSON settings and couldn't figure out how to turn it back on. Maybe because I couldn't remember the exact name of the feature after turning it off by accident, but the VS Code documentation could do a better job at addressing this feature.
John Polo (@John-Polo) Thanks for feedback here. I would bring this up to the team so we can provide better documentation on smart send.
Coming back to this sort of message/warning for sending commands to REPL (both terminal and native REPL), wondering what people think about the way Julia extension is handling things. When you shift+enter on a julia file, it sort of blinks and shows little hint on what is being sent to the REPL as well as the colorization depending on the success/failure output.
Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on, then we will be happy to re-open this issue to pick up where we left off.
A smart send warning pop up arose during coding and I changed the settings in a way I did not understand and did not want, which took some time to resolve, as it changed the VScode setting more than I wanted. I would have preferred to have received the pop up inviting change, when the current settings were functioning correctly. Such changes to VScode settings should, I think, be more guarded,
Thank you
Activity
movy commentedon Jun 7, 2024
Since this issue is #1 on google, I have exact same questions:
Looks like it invokes randomly, but has no traces in command palette or keyboard shortcuts.. and has a sneaky name also, like is my code sent somewhere based on some involuntarily invoked condition? So many questions without answers.
anthonykim1 commentedon Jun 7, 2024
Smart send is triggered via key binding

shift+enterYou may find little description of it in the settings itself where you could also turn off the setting.
If you turn off the setting for smart send, every instance of
shift+enterwill send things to terminal exactly as you specify/highlight or just a single line if you shift enter on a blank line.Feel free to turn off this setting in by easily clicking on your settings icon and then searching for 'smart send'
John-Polo commentedon Jun 11, 2024
tldr; I have tried on several occasions to find the documentation that matches the explanation provide by anthonykim1. Finally, I know how to activate/deactivate it.
I like the Smart Send. I have accidentally turned it off before. I could find nothing that explained how to change it's status. I just got the message referenced by OP, recognized it, and searched for it, and ended up here. This is the first time I have found anything approaching documentation that explains how to change it. I have looked all over stackoverflow for answers and tried different macros and other JSON settings and couldn't figure out how to turn it back on. Maybe because I couldn't remember the exact name of the feature after turning it off by accident, but the VS Code documentation could do a better job at addressing this feature.
github-actions commentedon Jul 13, 2024
Hey Anthony Kim (@anthonykim1), this issue might need further attention.
Matt Bierner (@mjbvz), you can help us out by closing this issue if the problem no longer exists, or adding more information.
anthonykim1 commentedon Jul 25, 2024
John Polo (@John-Polo) Thanks for feedback here. I would bring this up to the team so we can provide better documentation on smart send.
Coming back to this sort of message/warning for sending commands to REPL (both terminal and native REPL), wondering what people think about the way Julia extension is handling things. When you shift+enter on a julia file, it sort of blinks and shows little hint on what is being sent to the REPL as well as the colorization depending on the success/failure output.

github-actions commentedon Aug 25, 2024
Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on, then we will be happy to re-open this issue to pick up where we left off.
Happy Coding!
anthonykim1 commentedon Aug 26, 2024
Reopening this since this is fair/valid.
AttaData750 commentedon Feb 24, 2026
A smart send warning pop up arose during coding and I changed the settings in a way I did not understand and did not want, which took some time to resolve, as it changed the VScode setting more than I wanted. I would have preferred to have received the pop up inviting change, when the current settings were functioning correctly. Such changes to VScode settings should, I think, be more guarded,
Thank you