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.

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

Remove the file logging flags (log, logFile, verboseLog) #9648

Closed
bep opened this issue Mar 10, 2022 · 3 comments · Fixed by #11088
Closed

Remove the file logging flags (log, logFile, verboseLog) #9648

bep opened this issue Mar 10, 2022 · 3 comments · Fixed by #11088
Assignees
Milestone

Comments

@bep
Copy link
Member

bep commented Mar 10, 2022

Also the debug flag, which isn't useful.

These have been there since the early days, and I'm not even sure they work. If people want to log to file, they need to pipe the output.

@bep bep added this to the v0.94.0 milestone Mar 10, 2022
@bep bep self-assigned this Mar 10, 2022
@bep bep modified the milestones: v0.94.0, v0.95.0 Mar 10, 2022
@bep bep changed the title Remove the file loggin flags (log, logFile, debug) Remove the file loggin flags (log, logFile, verboseLog) Mar 10, 2022
@bep bep changed the title Remove the file loggin flags (log, logFile, verboseLog) Remove the file logging flags (log, logFile, verboseLog) Mar 10, 2022
bep added a commit to bep/hugo that referenced this issue Mar 10, 2022
@davidsneighbour
Copy link
Contributor

They work(ed). Not really an enhancement if those features are gone ;) But piping is ok I guess. Does Hugo use STDERR and STDOUT or only STDOUT? That seems to be of help in deciding how to pipe in Bash.

@bep bep modified the milestones: v0.95.0, v0.96.0 Mar 15, 2022
@davidsneighbour
Copy link
Contributor

I am back, please re-consider. Running hugo for instance via npm-run-all will result in piping of Hugo-only output to be impossible. I have a case where I run multiple scripts/apps/servers in parallel with one command. Doing that with removed logging options will have a lot of output in that piped file and there is no indicator which lines are by Hugo.

@bep bep modified the milestones: v0.96.0, v0.97.0 Mar 24, 2022
@bep bep modified the milestones: v0.97.0, v0.98.0 Apr 13, 2022
@bep bep modified the milestones: v0.98.0, v0.99.0 Apr 28, 2022
@bep bep modified the milestones: v0.99.0, v0.100.0 May 24, 2022
@bep bep modified the milestones: v0.100.0, v0.101.0 May 31, 2022
@bep bep modified the milestones: v0.101.0, v0.102.0 Jun 16, 2022
@bep bep modified the milestones: v0.102.0, v0.103.0 Aug 28, 2022
@bep bep modified the milestones: v0.103.0, v0.104.0 Sep 15, 2022
@bep bep removed this from the v0.104.0 milestone Sep 23, 2022
@bep bep added this to the v0.105.0 milestone Sep 23, 2022
@bep bep modified the milestones: v0.105.0, v0.106.0 Oct 26, 2022
@bep bep modified the milestones: v0.106.0, v0.107.0 Nov 18, 2022
@bep bep modified the milestones: v0.107.0, v0.108.0 Dec 3, 2022
@bep bep modified the milestones: v0.108.0, v0.109.0 Dec 14, 2022
@bep bep modified the milestones: v0.109.0, v0.111.0, v0.110.0 Jan 26, 2023
@bep bep modified the milestones: v0.111.0, v0.112.0 Feb 15, 2023
@bep bep modified the milestones: v0.112.0, v0.113.0 Apr 15, 2023
bep added a commit to bep/hugo that referenced this issue Jun 12, 2023
@bep bep modified the milestones: v0.113.0, v0.115.0 Jun 13, 2023
bep added a commit that referenced this issue Jun 13, 2023
@github-actions
Copy link

github-actions bot commented Jul 5, 2023

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 Jul 5, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.