[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]
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!
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]
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'.
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
The following script makes it a no-brainer:
% NEXT_YEAR=2015; ag -l 'Copyright.*Wiegley' \
| xargs sed -i '' -e "s/\(Copyright.*\)-20[0-9]\{2\}/\1-${NEXT_YEAR}/"
