-
Notifications
You must be signed in to change notification settings - Fork 119
Support refreshing the page #91
Comments
Thanks for the suggestion, yes I would really like to support that, although it's not as straightforward as I'd like. Closest I can suggest at the moment is the Restart button, which is cmd+shift+f5. Not quite the same, it will restart the entire browser. It restarts the Node instance in Node debugging too. You could map this to ctrl+r like
|
@roblourens What makes this feature complicated? |
Just that a debug adapter can't customize the behavior of the restart button at the moment. We talked about this in the past month, and I filed this bug to discuss - microsoft/vscode#14189 |
@roblourens This has landed right? Should we update the README with instructions on how to bind the shortcut? |
Oh right, I had duplicate issues. |
@roblourens So mapping this will make the page refresh right?
|
Yes |
why can't my visual studio code view my html tags and launch my browser. |
Can you be more specific? What is the problem? |
visual studio code is not debugging my html tags even after installation of
the view in default application hope you are understanding me now am using
mac OS X..... How can i go past this. am waiting on thanks Rob.
…On Thu, Feb 2, 2017 at 9:19 PM, Rob Lourens ***@***.***> wrote:
Can you be more specific? What is the problem?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#91 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ATXREVR9LngYHJVCUre_kxCfBqVINm5jks5rYh5CgaJpZM4J0JfK>
.
|
The other day I really wanted to refresh my page after saving a change in VSCode. Can you make ctrl-R work?
(jam3/devtool does have ctrl-r hooked up to restart the node.js instance, too. I love it.)
The text was updated successfully, but these errors were encountered: