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
Describe the bug
F3 and F8 would previously "Run Selected or All Code" and "Run All Code", respectively. It looks like these were accidentally removed (in commit 799515b). We just need to put these keybindings back.
Steps to reproduce
Open any SAS program or create a new one.
Hover over the running man icon, so that the tooltip appears.
Notice that it says, "Run Selected or All SAS Code" -- it no longer has the "F3" shortcut on the end, indicating that F3 is no longer a keyboard shortcut for that command.
Similarly, right-click in the SAS program editor to bring up the context menu and notice that F3 and F8 are no longer displayed next to "Run Selected or All SAS Code" nor "Run All SAS Code", again, reflecting these keyboard shortcuts are gone.
With focus in the SAS program editor, press F3 and then F8 to confirm neither Run the SAS code anymore. (F3 brings up the Find popup.)
Expected behavior
F3 should be associated with the "Run Selected or All SAS Code" command and F8 associated with the "Run All SAS Code" command again.
Again, it appears the keybindings were simply accidentally removed in commit 799515b and just need to be added back.
Screenshots
Environment (please complete the following information):
Client OS: Windows 10
Extension version: v0.1.3
SAS version: Viya 2023.04
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
F3 and F8 would previously "Run Selected or All Code" and "Run All Code", respectively. It looks like these were accidentally removed (in commit 799515b). We just need to put these keybindings back.
Steps to reproduce
Expected behavior
F3 should be associated with the "Run Selected or All SAS Code" command and F8 associated with the "Run All SAS Code" command again.
Again, it appears the keybindings were simply accidentally removed in commit 799515b and just need to be added back.
Screenshots
Environment (please complete the following information):
Client OS: Windows 10
Extension version: v0.1.3
SAS version: Viya 2023.04
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: