github/hugo
1
0
Fork 0
mirror of https://github.com/gohugoio/hugo.git synced 2024-11-21 20:46:30 -05:00
Code Issues Projects Releases Packages Wiki Activity
hugo/docs/content/troubleshooting/strange-eof-error.md
Anthony Fok 190964c57b [Docs] New Troubleshooting section 
With two entries of frequently encountered or obscured troubles so far:

- "Categories with accented characters" Unicode NFC/NFD mismatch
   on Mac OS X (See #739)
- `hugo new` aborts with cryptic EOF error (See #776)
2015-01-08 18:29:05 -07:00

1.9 KiB
Raw Blame History

date menu title weight
2015-01-08T16:11:23-07:00
main
parent
troubleshooting
Strange EOF error 5

Trouble: hugo new aborts with cryptic 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 an EOF error thrown by Hugo.

I have set up this test repository to show exactly what I've done, but it is essentially a vanilla installation of Hugo. https://github.com/polds/hugo-archetypes-test

When in that repository, using Hugo v0.12 to run 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

Thank you for reporting this issue. The solution is to add a final newline (or EOL) to the end of your default.md archetype file of your theme. More discussions happened on the forum here:

So yes, we do need to fix this. We need to do the following:

  1. Add warnings about this in the Hugo documentation, as several people have run into the same problem already. (Users of editors like Vim, nano and gedit are immune to this because these editors enforce an EOL at the end of the file by default, but other editors like Emacs don't do that.)
  2. Improve the error message. It is difficult to determine what went wrong with just three characters "EOF"
  3. Allow archetype files without the final EOL to compile anyway, but do give an appropriate and detailed warning. (optional, to be discussed) https://github.com/spf13/hugo/issues/776

References