Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Fix inconsistent "Watching for changes in [path]" output with hugo server #1721

Closed
anthonyfok opened this issue Dec 19, 2015 · 1 comment
Closed

Fix inconsistent "Watching for changes in [path]" output with hugo server #1721

anthonyfok opened this issue Dec 19, 2015 · 1 comment
Labels
Outdated

Comments

@anthonyfok
Copy link
Member

The printed watched paths look kind of weird when --source is a relative directory. For example:

foka@debian:~/git/hugo$ hugo server -s docs
0 draft content
0 future content
166 pages created
0 paginator pages created
41 tags created
0 groups created
in 409 ms
Watching for changes in docs/docs/{..}
Serving pages from memory
Web Server is available at http://localhost:1313/ (bind address 127.0.0.1)
Press Ctrl+C to stop
foka@debian:~/git/hugo$ cd docs
foka@debian:~/git/hugo/docs$ hugo server 
0 draft content
0 future content
166 pages created
0 paginator pages created
41 tags created
0 groups created
in 425 ms
Watching for changes in /home/foka/git/hugo/docs/{data,content,layouts,static}
Serving pages from memory
Web Server is available at http://localhost:1313/ (bind address 127.0.0.1)
Press Ctrl+C to stop
tychoish pushed a commit to tychoish/hugo that referenced this issue Aug 13, 2017
@anthonyfok @tychoish
Fix hugo server "Watching for changes" path display
85231b0 
especially when the given `--source` path is a relative directory.

Also, when `--source` is specified, make WorkingDir an absolute path
from the very beginning, to be consistent with the case when `--source`
is not given.  Otherwise, the function name helpers.AbsPathify(), which
prepends WorkingDir to a relative path, does not really make sense.

Fixes gohugoio#1721
@github-actions
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 10, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
Outdated
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@anthonyfok