I think 'lisp/CMakeLists.txt' still has to be updated to include the new
file names. I can take a look at it this evening.
On Sep 18, 2014 7:17 AM, Eric Abrahamsen e...@ericabrahamsen.net wrote:
Craig Earls ender...@gmail.com writes:
I have spent the last month overhauling ledger
Craig Earls ender...@gmail.com writes:
I have spent the last month overhauling ledger fontification. I gave
up on using the standard REGEX based methods that most font lockers
use. Instead I wrote a few functions that actually understand the
semantics of a ledger xact then had jit-lock and
Hi Craig,
Nice work.
I found one issue, in the following posting:
2014/08/23 demo fontification error
Expense:AAA € 10,00
Expense:BBB € 20,00
cash
Expense:CCC € 10,00
card
Thanks. I have seen this as well. I will look into it.
On Sun, Sep 14, 2014 at 9:29 AM, Hans Erik van Elburg
hanserik.van.elb...@gmail.com wrote:
Hi Craig,
Nice work.
I found one issue, in the following posting:
2014/08/23 demo fontification error
Expense:AAA
in between)
--
john2x.com | @john2x
On Friday, September 12, 2014 at 9:10 PM, Craig Earls wrote:
The new fontification scheme requires an empty line between transactions to
tell where they begin and end.
I actually thought that was a requirement for the ledger input file. If it
isn't I
, September 12, 2014 at 9:10 PM, Craig Earls wrote:
The new fontification scheme requires an empty line between transactions to
tell where they begin and end.
I actually thought that was a requirement for the ledger input file. If it
isn't I will see if I can get another way working
Awesome work. Thanks!
Not sure if it's a bug or intentional, but I like to group my transactions
by day. With the recent changes, payees without an empty line before them
aren't highlighted correctly anymore.
Screenshot: http://i.imgur.com/EeSsh7z.png (The top one has an empty line
before
The new fontification scheme requires an empty line between transactions to
tell where they begin and end.
I actually thought that was a requirement for the ledger input file. If it
isn't I will see if I can get another way working.
On Thursday, September 11, 2014, John Louis Del Rosario joh
Hmm afaik it's explicitly mentioned in the docs that there should be an empty
line between transactions. (Although all examples in the docs do have empty
lines in between)
--
john2x.com | @john2x
On Friday, September 12, 2014 at 9:10 PM, Craig Earls wrote:
The new fontification scheme
PM, Craig Earls wrote:
The new fontification scheme requires an empty line between transactions to
tell where they begin and end.
I actually thought that was a requirement for the ledger input file. If it
isn't I will see if I can get another way working.
On Thursday, September 11, 2014
at 9:10 PM, Craig Earls wrote:
The new fontification scheme requires an empty line between transactions to
tell where they begin and end.
I actually thought that was a requirement for the ledger input file. If it
isn't I will see if I can get another way working.
On Thursday
Nice work Craig!
One thing I noticed, though: In the following transaction the account name
in the second line (B) is highlighted using
`ledger-font-posting-amount-face`.
And the 0 in the first posting is highlighted as if it was part of the
account name.
2014/03/11 Whatever
A
I will look into this, but I think single character account names and
single digit amounts are not realistic.
On Wed, Sep 10, 2014 at 6:48 AM, Johann Klähn kljoh...@gmail.com wrote:
Nice work Craig!
One thing I noticed, though: In the following transaction the account name
in the second line
I just stripped this down, I noticed it in my own journal where I use
normal account names but happened to have a zero in some auto-generated
postings. I agree that this is a corner case and very low priority, as I
can just modify my journal. Just wanted to let you know.
On Wed, Sep 10, 2014 at
Thanks, I ran a quick check and the single digit amount is getting by
the filter. It turns out that it doesn't like pure integer amounts so
it isn't as far in the corner as I would like. I will get it fixed.
On Wed, Sep 10, 2014 at 6:54 AM, Johann Klähn kljoh...@gmail.com wrote:
I just
This has been fixed. Thanks for finding it.
On Wed, Sep 10, 2014 at 6:48 AM, Johann Klähn kljoh...@gmail.com wrote:
Nice work Craig!
One thing I noticed, though: In the following transaction the account name
in the second line (B) is highlighted using
`ledger-font-posting-amount-face`.
And
I have spent the last month overhauling ledger fontification. I gave
up on using the standard REGEX based methods that most font lockers
use. Instead I wrote a few functions that actually understand the
semantics of a ledger xact then had jit-lock and font-lock call those.
Overall there is much
On Sep 8, 2014, at 8:49 PM, Craig Earls ender...@gmail.com wrote:
I have spent the last month overhauling ledger fontification. I gave
up on using the standard REGEX based methods that most font lockers
use. Instead I wrote a few functions that actually understand the
semantics of a ledger
Indentation is totally independent of font-lock. There is a bug noted
already. I just haven't gotten to it.
On Monday, September 8, 2014, Andrew Schwartzmeyer and...@schwartzmeyer.com
wrote:
On Sep 8, 2014, at 8:49 PM, Craig Earls ender...@gmail.com javascript:;
wrote:
I have spent the
19 matches
Mail list logo