New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add option to open "current" content file in a browser #3643

Closed
bep opened this Issue Jun 25, 2017 · 1 comment

Comments

Projects
None yet
2 participants
@bep
Member

bep commented Jun 25, 2017

I saw this question asked somewhere and it would be really useful:

  • I guess it would be triggered on the first save of a new content file, but that would be OK.
  • It should have a hugo server flag (browserOpen ?) + config so it is easy to turn on.
  • Default OFF.
  • It should handle situations with "mass edits", but I guess that is also an issue with the current?

@bep bep self-assigned this Jun 25, 2017

@bep bep added the Enhancement label Jun 25, 2017

@bep bep added this to the v0.25 milestone Jun 25, 2017

@bep bep changed the title from Add a way to open "current" content file in a browser to Add option to open "current" content file in a browser Jun 25, 2017

bep added a commit to bep/hugo that referenced this issue Jun 25, 2017

@bep bep closed this in #3645 Jun 26, 2017

bep added a commit that referenced this issue Jun 26, 2017

Support open "current content page" in browser
This commit adds a new `--navigateToChanged` and config setting with the same name, that, when running the Hugo server with live reload enabled, will navigate to the current content file's URL on save. 

This is really useful for site-wide content changes (copyedits etc.).
Fixes #3643
@jhabdas

This comment has been minimized.

Show comment
Hide comment
@jhabdas

jhabdas Sep 17, 2017

Contributor

This little feature, is having so much positive impact on my workflow. I'd like to state for the record stopping my React development and moving to Hugo has been one of the best choices I've made in the last 5 years.

Contributor

jhabdas commented Sep 17, 2017

This little feature, is having so much positive impact on my workflow. I'd like to state for the record stopping my React development and moving to Hugo has been one of the best choices I've made in the last 5 years.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment