| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| |
| |
| |
| |
| |
| | |
ecraven-fix-warning
# Conflicts:
# lisp/ledger-occur.el
# lisp/ledger-report.el
# lisp/ledger-schedule.el
# lisp/ledger-sort.el
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | | |
When a transaction is being added the previous one is highlighted.
Solve the problem checking that the highlighted region contains the
point.
|
| | |
| | |
| | |
| | |
| | | |
Extend the highlighting of the last line in the transaction to the
right margin of the buffer. Do not highlight empty lines.
|
| | |
| | |
| | |
| | | |
[ci skip]
|
| | | |
|
|\| | |
|
| |\ \
| | | |
| | | | |
Fix amount regexp in context computation.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Before the fix the amount required decimal point even when the decimal
digits were optional. Now both are optional.
The separator regexp didn't have capture group so all the further fields
shifted one field back (amount went into separator, commodity into
amount etc.)
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | | |
Make the default alignment behaviour the same as before 767ab3e, that
is, align on the last digit by default. A new option
`ledger-post-amount-alignment-at' now exists to adjust alignment
preference.
|
| | |
| | |
| | |
| | |
| | | |
The function `ledger-display-balance-at-point' called with the prefix
argument will now ask for the target commodity.
|
| | |
| | |
| | |
| | |
| | | |
The function provides completing read with all available commodities as
gathered by "ledger commodities".
|
|\| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
That is:
A $10.00
B $5
C -$15.00
Before the numbers aligned at the end of the last digit.
|
| |\ \
| | | |
| | | | |
Fill comment paragraph with ledger-post-align-dwim
|
| | | |
| | | |
| | | |
| | | |
| | | | |
In addition to re-aligning postings, if the point is in a comment, just
fill that comment as regular plaintext.
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
If the integer part was 2 digits, because the integer part was
non-greedy, it only captured as much as necessary, namely one digit.
The other digit was captured by the 5th group's [:word:] not 4th because
that one is also optional. This results in incorrect reporting of
amount length and broken aligning.
Also move the decimal dot matching from 3rd group to 4th, and quote the
dot.
|
| | |
| | |
| | |
| | |
| | | |
There is very little reason to have M-q bound to fill-paragraph in
ledger, so let's use it for aligning instead.
|
| | |
| | |
| | |
| | |
| | | |
If no region is active, align the current transaction. If a region is
active, align all postings in the region.
|
|\| | |
|
| | | |
|
|\| |
| | |
| | |
| | |
| | | |
Conflicts:
lisp/ledger-xact.el
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Using `ledger-add-transaction` to add a transaction with a date that
places it at the end of the buffer will "forget" to insert the newline
between it and the previous transaction. This error occurs in
`ledger-xact-find-slot` where the `(when (and (eobp) last-xact-start)`
is entered, but subsequently the `(if (eobp))` is false because the
point has been moved to the end of the prior exact, which is not the end
of the buffer.
The `if` expression is superfluous because the `when` expression has
already been entered, and it is broken becase the point gets
moved. Removing it fixes the behavior for transactions added at the end
of the buffer, and does not break the behavior for transactions added
elsewhere.
This was observed with Emacs 24.5.50.1 and Ledger 3.1.0-20141005.
[ci skip]
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
month and year scheduling.
|
|\| | |
|
| | |
| | |
| | | |
ledger-post-align-postings expects (beg end) not to be optional
|
|\| | |
|
| | |
| | |
| | |
| | |
| | | |
Use standard method (interactive "r") to get the current active region
for use in ledger-post-align-postings.
|
|\| | |
|
| |\ \
| | | |
| | | | |
[emacs] Fix bug 1060.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Set as an option to kill (or not) the reconcile buffer after
ledger-reconcile-finish. The default is set to *not* kill the
buffer. This is justified as the facts that:
1. In old ledger mode (the one from Ledger 2.6), the default is to *not*
kill the buffer. Also for the ones who will migrate from 2.6 to 3 when
package will be available in their linux distribution, this will be the
path of least surprise.
2. The current documentation does state that the buffer is to be killed
with 'q' after 'C-c C-c'.
This has been made configurable, as killing buffer may already be part
of the workflow of some persons.
[ci skip]
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The old way of working was keeping spaces before and after the
account. Now the space before is associated to the "status" and
"separator" is enlarged to not be maxed to 2 chars
[ci skip]
|
|\| |
| | |
| | |
| | |
| | | |
Conflicts:
lisp/ledger-reconcile.el
|
| |/
| |
| |
| |
| |
| | |
C-x h M-x indent-region RET
[ci skip]
|
| |
| |
| |
| | |
original s.el
|
| |
| |
| |
| | |
ledger-reconcile.el and ledger-mode.texi.
|
| |
| |
| |
| |
| | |
You can now maximize the number of characters displayed for payee name
and account name in the reconcile buffer.
|
| | |
|
|/ |
|
|
|
| |
ledger-xact.el:ledger-copy-transaction-at-point (C-c C-k) led to a confusing change in the ledger file for the case when the target date was smaller than last date in the ledger.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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]
|
| |
|
| |
|