hledger/tests/journal/blank-description.test

# 1. accept a blank description
hledger -f- print
<<<
2010/1/1 
  a  1
  b

>>>=0

# 2. same, but no separator space after the date
hledger -f- print
<<<
2010/1/1
  a  1
  b

>>>=0
parsing: if there is no description, don't require a space after the transaction date 2010-04-16 00:44:04 +04:00			`# 1. accept a blank description`
tests: make functional tests use "hledger" again Using "hledgerdev" was a hack to help ensure that tests used a fresh developer build by default. Now they specify "hledger" again, which fits better with stack. It's up to the tester to make sure the desired executable is first in PATH or specified with -w. (Note a couple of tests currently don't obey -w and will always run "hledger", see addons.test). 2015-07-12 21:54:08 +03:00			`hledger -f- print`
parsing: if there is no description, don't require a space after the transaction date 2010-04-16 00:44:04 +04:00			`<<<`
			`2010/1/1`
			`a 1`
			`b`
update shell tests for latest shelltestrunner 2011-03-12 23:55:49 +03:00
			`>>>=0`

parsing: if there is no description, don't require a space after the transaction date 2010-04-16 00:44:04 +04:00			`# 2. same, but no separator space after the date`
tests: make functional tests use "hledger" again Using "hledgerdev" was a hack to help ensure that tests used a fresh developer build by default. Now they specify "hledger" again, which fits better with stack. It's up to the tester to make sure the desired executable is first in PATH or specified with -w. (Note a couple of tests currently don't obey -w and will always run "hledger", see addons.test). 2015-07-12 21:54:08 +03:00			`hledger -f- print`
parsing: if there is no description, don't require a space after the transaction date 2010-04-16 00:44:04 +04:00			`<<<`
			`2010/1/1`
			`a 1`
			`b`
update shell tests for latest shelltestrunner 2011-03-12 23:55:49 +03:00
			`>>>=0`