| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
for --period synonyms like --monthly, et al.
[ci skip]
|
|\
| |
| |
| |
| | |
[emacs] Fontification should work independentily on where the point currently is
Nice catch. This was clearly an error since beg was never used in this form.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is a subtle bug that happens only when org-src-fontify-natively is
enabled:
(setq org-src-fontify-natively t)
If then you create a Babel block with ledger text, it won't be
fontified.
This happens because the 'ledger-fontify-buffer-part' starts
fontification from the current 'point', which in case of
org-src-font-lock-fontify-block happens to _not_ point to the beginning
of buffer. Instead it points to the original org-mode buffer.
This doesn't happen when one opens regular files, because the
'point' is almost always at the beginning of the file.
To reproduce the bug, you can do the following:
(defun fontify-test()
(let ((lang-mode 'ledger-mode) pos next)
(with-current-buffer
(get-buffer-create
"ledger-fontification-bug")
(unless (eq major-mode lang-mode) (funcall lang-mode))
(erase-buffer)
(insert "2015/01/09 asdf\n foo\n bar\n" " ")
(font-lock-fontify-buffer)
(switch-to-buffer "ledger-fontification-bug")
)))
Call 'fontify-test' and see that the buffer is not fontified.
[ci skip]
|
| |
| |
| |
| | |
[ci skip]
|
| |
| |
| |
| |
| |
| | |
to highlight only the xact keyword
[ci skip]
|
| |
| |
| |
| |
| |
| |
| | |
since "troff can be confused by blank space characters
at the end of a line." -- mdoc (7)
[ci skip]
|
| | |
|
| | |
|
| |
| |
| |
| | |
[ci skip]
|
|\|
| |
| |
| | |
[ci skip]
|
| |\
| | |
| | | |
Small doc typo fixes
|
| |/ |
|
| | |
|
| | |
|
| | |
|
|/
|
|
| |
Switch to single job builds
|
|
|
|
|
|
| |
Currently the path to install the python library in is determined by
running the python interpreter. We do not want to end up installing a
library built for python2 in the python3 library path!
|
|
|
|
| |
[ci skip]
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It would be great to use texinfo variables to set the current Ledger
version, e.g. @value{Ledger_VERSION_MAJOR} and pass the CMake variables
to texi2pdf via --command='@set Ledger_VERSION_MAJOR ${Ledger_VERSION_MAJOR}'.
Unfortunately texi2pdf will err with:
Argument of @parseargline has an extra }.
<inserted text>
@par
<to be read again>
}
@\subtitle ...epage {@subtitlefont @rightline {#1}
}
l.153 @subtitle For Version @value{Ledger_VERSION_MAJOR} of Ledger
[ci skip]
|
| |
|
|
|
|
| |
[ci skip]
|
|
|
|
|
|
| |
better from one another in the item list
[ci skip]
|
|
|
|
|
|
|
| |
using ag --nogroup '^[ ]*debug\(' | cut -d '"' -f2 | sort -u | column
[ci skip]
|
| |
|
|\
| |
| |
| |
| |
| |
| | |
lowdef/ledger-mode-bug-1089-auto-refresh-sticky-cursor
ledger-mode bug 1089 introduce sticky cursor for report auto refresh
Thanks.
|
| | |
|
|\ \
| |/
|/| |
cygwin build: cleanup after overlapping pull requests 360 & 361 + make changes minimalistic
|
|/ |
|
|\
| |
| | |
automating ledger build on Cygwin
|
| | |
|
| | |
|
| | |
|
| | |
|
|\ \
| | |
| | | |
Fix for BUG 985
|
|/ /
| |
| |
| |
| |
| |
| |
| | |
http://bugs.ledger-cli.org/show_bug.cgi?id=985
Fix compilation issue on Cygwin by adding the '-U__STRICT_ANSI__' flag
to GCC. This avoids GCC disabling some stdlib functions like 'setenv'
and 'popen'.
|
| | |
|
|/ |
|
| |
|
|\ |
|
| |\
| | |
| | | |
Set CMake policy CMP0042
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
to remove the warning below when running cmake.
In the long run changing the CMake rules to set MACOSX_RPATH
might be the better option.
CMake Warning (dev):
Policy CMP0042 is not set: MACOSX_RPATH is enabled by default. Run "cmake
--help-policy CMP0042" for policy details. Use the cmake_policy
command to set the policy and suppress this warning.
MACOSX_RPATH is not specified for the following targets:
libledger
This warning is for project developers. Use -Wno-dev to suppress it.
|
| |\ \
| | | |
| | | | |
[tests] Add examples parameter to DocTests
|
| | | |
| | | |
| | | | |
to test the given examples only instead of every example.
|
| |\ \ \
| | |/ /
| |/| | |
Fix bug 1038; Improve error handling when parsing year directives
|
| | | |
| | | |
| | | |
| | | |
| | | | |
when year was specified with literal Y or year directive, but not
when using apply year.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
A literal Y directive or ‘year’ directive with an empty or invalid
argument, e.g. ‘2o14’ (that is a small letter ‘oh’ instead of a zero)
would fail with the following rather unhelpful error message:
Error: bad lexical cast: source type value could not be interpreted as target
|
| |/ /
| | |
| | |
| | | |
Only Y2014 or apply year 2014 would actually set the year for the
following transactions; year 2014 would silently do nothing.
|
| |\ \
| | | |
| | | | |
Update copyright
|
| | | | |
|