mirror of
https://github.com/gohugoio/hugo.git
synced 2024-11-14 20:37:55 -05:00
ec4e6f9df2
git-subtree-dir: docs git-subtree-split: f887bd7b4e3e7c7e76cd63951e5b0d37d8fe0ac7
1.7 KiB
1.7 KiB
title | linktitle | description | date | publishdate | lastmod | categories | menu | draft | weight | aliases | toc | ||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
EOF Error | EOF Error | If you find yourself seeing an EOF error in the console whenever you create a new content file from Hugo's archetype feature. | 2017-02-01 | 2017-02-01 | 2017-02-01 |
|
|
false |
|
true |
Trouble: hugo new
Aborts with EOF error
I'm running into an issue where I cannot get archetypes working, when running
hugo new showcase/test.md
, for example, I see anEOF
error thrown by Hugo.When I run Hugo with v0.12 via
hugo new -v showcase/test.md
, I see the following output:INFO: 2015/01/04 Using config file: /private/tmp/test/config.toml INFO: 2015/01/04 attempting to create showcase/test.md of showcase INFO: 2015/01/04 curpath: /private/tmp/test/archetypes/showcase.md ERROR: 2015/01/04 EOF
Is there something that I am blatantly missing?
Solution: Carriage Returns
The solution is to add a final newline (i.e., EOL
) to the end of your default.md archetype file of your theme. You can do this by adding a carriage return after the closing +++
or ---
of your TOML or YAML front matter, respectively.
{{% note "Final EOL Unnecessary in v0.13+" %}} As of v0.13, Hugo's parser has been enhanced to accommodate archetype files without final EOL thanks to the great work by @tatsushid. {{% /note %}}
Discussion Forum References
- http://discourse.gohugo.io/t/archetypes-not-properly-working-in-0-12/544
- http://discourse.gohugo.io/t/eol-f-in-archetype-files/554