mirror of
https://github.com/simonmichael/hledger.git
synced 2024-09-18 17:57:11 +03:00
docs: document web reloading and handling of parse errors
This commit is contained in:
parent
4093e7d36e
commit
b3f996544a
@ -583,6 +583,22 @@ need to be upgraded too, probably by removing them and letting them be
|
||||
recreated. So if you do customise them, remember what you changed; a
|
||||
version control system such as darcs will work well here.
|
||||
|
||||
###### detecting changes
|
||||
|
||||
As noted, changes to the support files will take effect immediately,
|
||||
without a restart. This applies to the journal data too; you can directly
|
||||
edit the journal file(s) (or, eg, commit a change within a version control
|
||||
system) while the web UI is running, and the changes will be visible on
|
||||
the next page reload.
|
||||
|
||||
###### malformed edits
|
||||
|
||||
The journal file must remain in good [hledger format](#journal-file) so
|
||||
that hledger can parse it. The web add and edit forms ensure this by not
|
||||
allowing edits which would introduce parse errors. If a direct edit makes
|
||||
the journal file unparseable, the web UI will show the error instead of
|
||||
data, until the file has been fixed.
|
||||
|
||||
There are some web-specific options:
|
||||
|
||||
###### --port
|
||||
|
2
Makefile
2
Makefile
@ -754,7 +754,7 @@ stats: showlastreleasedate showreleaseauthors showloc showcov showlocalchanges s
|
||||
|
||||
showreleaseauthors:
|
||||
@echo Patch authors since last release:
|
||||
@darcs changes --from-tag . |grep '^\w' |cut -c 31- |sort |uniq
|
||||
@darcs changes --from-tag 0.12 |grep '^\w' |cut -c 31- |sort |uniq
|
||||
@echo
|
||||
|
||||
showloc:
|
||||
|
Loading…
Reference in New Issue
Block a user