simonmichael/hledger 1.50.4

on GitHub

hledger 1.50.4

Fixes

• An include directive with no argument now gives consistent error messages.

• journal format's include directive no longer excludes paths containing dotted directories/files.
  1.50-1.50.3 contained an overzealous workaround that sometimes wrongly excluded paths containing a dot dir or dot file.
  Now the pre-1.50 behaviour is restored
  (* and ** generally avoid dot files and dot directories, except ** will search non-top-level dot directories).
  #2498

• Symbolic links found by include directives are once again shown as-is, not dereferenced.
  (1.50-1.50.3 showed them dereferenced, eg in hledger files output.)

  There is some related new behaviour: each time an include directive is parsed,
  all the parent file paths and the new include file path(s) are re-canonicalised.
  Previous hledger versions did not do this; it's expected to be unnoticeable,
  but if you notice any slowdown caused by having many include directives and a slow filesystem,
  please report it.

hledger-ui 1.50.4

• Uses hledger 1.50.4.

hledger-web 1.50.4

• Uses hledger 1.50.4.

credits 1.50.4

Simon Michael.

For all install options, see hledger.org: Install.
You can install hledger from most package managers (but check for a green badge indicating it's up to date).
Or you can build it from source yourself.

Or you can install up to date binaries from this page, by following the appropriate instructions below.
If you find problems with these instructions, please let us know.

If you have eget, that's a convenient way to download the right binaries for your machine:

eget simonmichael/hledger --all

Otherwise:

At the command line:

curl -fLOC- https://github.com/simonmichael/hledger/releases/download/1.50.4/hledger-linux-x64.tar.gz | tar -xzv -f- -C/usr/local/bin hledger hledger-ui hledger-web
hledger --version; hledger-ui --version; hledger-web --version    # should show 1.50.4

In a terminal window (don't download the binaries with your web browser, they won't get authorised):

On ARM macs:

curl -fLOC- https://github.com/simonmichael/hledger/releases/download/1.50.4/hledger-mac-arm64.tar.gz | tar -xzv -f- -C/usr/local/bin hledger hledger-ui hledger-web
hledger --version; hledger-ui --version; hledger-web --version    # should show 1.50.4

On Intel macs:

curl -fLOC- https://github.com/simonmichael/hledger/releases/download/1.50.4/hledger-mac-x64.tar.gz | tar -xzv -f- -C/usr/local/bin hledger hledger-ui hledger-web
hledger --version; hledger-ui --version; hledger-web --version    # should show 1.50.4

In a powershell window (press WINDOWS-R, powershell, ENTER):

cd ~
curl https://github.com/simonmichael/hledger/releases/download/1.50.4/hledger-windows-x64.zip -OutFile hledger-windows-x64.zip
Expand-Archive hledger-windows-x64.zip -Force -DestinationPath AppData\Roaming\local\bin
hledger --version; hledger-ui --version; hledger-web --version    # should show 1.50.4

These instructions have not been tested recently, please let us know if they work for you:

• click hledger-windows-x64.zip below
• choose Open with Windows Explorer, OK
• click Extract all files
• choose a destination folder - ideally one that appears in echo %PATH%, like C:\Windows (though that one will require administrator permission); otherwise, your home directory (C:\Users\YOURNAME)
• check "Show extracted files when complete"
• click Extract, wait for the destination folder to open
• find the hledger, hledger-web icons (if you extracted to \Windows, you'll need to scroll down)
• for each icon: double-click, uncheck "Always ask before opening this file", click Run
• close those Explorer windows
• open a command window (press Windows-r, type CMD, press enter)
• hledger --version; hledger-ui --version; hledger-web --version should show 1.50.4
• echo # >> .hledger.journal to ensure a default journal file exists. (Important: the doubled >> is needed to avoid overwriting existing data.)

Problems:

• Starting hledger by double-clicking its icon won't work because it needs arguments; run it from the command window instead.
• Starting hledger-web by double-clicking its icon may fail eg because Explorer's command window is too small;
  configure that to be larger, or run hledger-web from a command window instead.
• hledger or hledger-web may fail to run if there is not enough memory available.

Next steps

Once installed, run hledger, and perhaps read hledger.org: Quick start.