mercurial - How do I stop getting a parse error when setting up a Hg Subrepo? -
i'm having difficulties creating hg-subrepo local hg repository.
i've created "core" repository subrepository inside repo. i'm able clone "core" repo inside target when go create/checkin .hgsub file, parse error prohibits me committing file.
ps c:\temp\subrepo_experiments\target01> hg status ps c:\temp\subrepo_experiments\target01> hg clone c:\temp\subrepo_experiments\core destination directory: core updating branch default resolving manifests getting core_001.txt getting core_002.txt getting core_003.txt 3 files updated, 0 files merged, 0 files removed, 0 files unresolved ps c:\temp\subrepo_experiments\target01> echo core = c:\temp\subrepo_experiments\core > .hgsub ps c:\temp\subrepo_experiments\target01> hg status ? .hgsub ps c:\temp\subrepo_experiments\target01> hg add .hgsub adding .hgsub ps c:\temp\subrepo_experiments\target01> hg commit hg: parse error @ .hgsub:1: ■c o r e ps c:\temp\subrepo_experiments\target01>
whatever editor used create .hgsub
file has created abomination. appears using 16-bit utf-16 encoding , has bom (byte order mark) @ front. use creates utf-8 or ascii text without bom, , you'll in shape. can see problem in output:
hg: parse error @ .hgsub:1: ■c o r e
it's telling "hey, there's piece of nonsense @ front , non-printable character (nul / 0x00 in case) in between every character!
Comments
Post a Comment