proposed addition to manual

[Richard Cobbe]

Hello, all.

What's the process for proposing a minor addition to the manual?  Submit a
pull request?

I recently archived transactions from previous years, following the
instructions at
.
Those instructions, as far as they go, are just fine.  However, there are
some subtleties if you want ledger's notion of the cleared balance of your
accounts to match your bank's, and if the archived transactions include a
mix of cleared and uncleared transactions.  I've worked through them, but
it would be nice to document these so that other people don't have to go
through this process (and I include myself the next time I want to do
this).

Thanks,

Richard

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Ledger" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ledger-cli+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: how to install 3.1 from source on MacOS?

[Richard Cobbe]

On Wed, Sep 02, 2015 at 05:48:27PM +0200, Alexis wrote:
> Hello Richard,
> > 1) What are the various branches in the 3.x release that I might reasonably
> > want to use, and what are the tradeoffs between them?
>
> master: The current stable branch, which is currently a bit stale
> doesn't build with boost >=1.59
> It moves slowly
>
> next: The branch where all development happens, may break occasionally,
>   but has been rather stable the last months
>
> release/*: The branches used for releases, currently abandoned
>
> I recommend you use next, it would help the community if you find and
> report bugs.
>
> > 2) Once I've decided which branch to use, what is the git command to check
> > out that branch?
>
> % git checkout -b next origin/next # where next is the branch you decide upon

Excellent; just what I needed.  Thanks!

I ran
$ git clone https://github.com/ledger/ledger.git
which succeeded, and then
$ git checkout -b next origin/next
which didn't:
fatal: A branch named 'next' already exists.

It *looks* like I'm already on the 'next' branch:
$ git branch
* next

Is that correct?

Thanks for your patience with these basic questions,

Richard

>
>
> Cheers,
> Alexis
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups 
> "Ledger" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to ledger-cli+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Ledger" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ledger-cli+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: how to install 3.1 from source on MacOS?

[Richard Cobbe]

On Tue, Sep 01, 2015 at 05:46:35PM +0200, Alexis wrote:
> Hello Richard,
> acprep is a convenience build script, which basically runs:
>
> % cmake . && make
>
> So that command should compile ledger for you using the dependencies
> from MacPorts.
>
> I'm working on improving and documenting the ledger CMake files,
> so that using cmake directly and knowing about the various
> configuration options will become easier.
>
> Here's a list of options ledger's cmake process understands:
> % grep option CMakeLists.txt
> option(USE_PYTHON "Build support for the Python scripting bridge" OFF)
> option(USE_DOXYGEN "Build reference documentation using Doxygen" OFF)
> option(DISABLE_ASSERTS "Build without any internal consistency checks" OFF)
> option(BUILD_DEBUG "Build support for runtime debugging" OFF)
> option(BUILD_LIBRARY "Build and install Ledger as a library" ON)
> option(BUILD_DOCS "Build and install documentation" OFF)
> option(BUILD_WEB_DOCS "Build version of documentation suitable for viewing 
> online" OFF)
> option(BUILD_EMACSLISP "Build and install ledger-mode for Emacs" OFF)
>
> So if you would like to use the ledger's Python module you would need to run:
> % cmake -DUSE_PYTHON=ON . && make # I recommend using make -j
>
> Please report back if certain dependencies such as boost, gmp or mpfr
> aren't found.

Thanks for your reply!

I have the dependencies installed (by hand, btw, because I don't really
want to have to install the +universal variants of all of the MacPorts
packages).

My questions at this point are rather more basic -- and I should have made
that clearer in my original email; sorry about that.

1) What are the various branches in the 3.x release that I might reasonably
want to use, and what are the tradeoffs between them?

2) Once I've decided which branch to use, what is the git command to check
out that branch?

That is, I'm looking for something like, "well, you could use either branch
X or branch Y: branch X gets you access to the latest features, but it's
occasionally broken; Y moves more slowly but is much more likely to build
and run."

And the git question isn't about version control in general -- I've been
using various version control tools for years; I'm just not familiar with
git.

Thanks much,

Richard

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Ledger" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ledger-cli+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: how to install 3.1 from source on MacOS?

[Richard Cobbe]

On Mon, Aug 31, 2015 at 09:28:57AM +0200, Alan Schmitt wrote:
> On 2015-08-31 00:22, Richard Cobbe <co...@ccs.neu.edu> writes:
>
> > Forgive some extremely basic questions, but what do I need to do to build
> > a reasonably stable version of Ledger 3.1 from source on MacOS 10.10?
>
> I install it using homebrew, and it works flawlessly.

Thanks for the suggestion, but I'm really not interested in switching from
MacPorts to Homebrew just at the moment, nor in attempting to get both of
them to play nicely together on the same system.

I really would like to be able to just check out the source from GitHub and
build it.

I perhaps should have mentioned that I had this working before, but due to
a hard drive replacement and an incomplete TimeMachine backup, I lost my
previous copy of the repository, so I'm having to start over from scratch.
(At least I had the binaries, so I can limp by for a bit.)

Thanks,

Ricahrd

-- 

--- 
You received this message because you are subscribed to the Google Groups 
"Ledger" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ledger-cli+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

how to install 3.1 from source on MacOS?

[Richard Cobbe]

Forgive some extremely basic questions, but what do I need to do to build
a reasonably stable version of Ledger 3.1 from source on MacOS 10.10?

I use MacPorts, but unfortunately the current ledger package there doesn't
build, due to an apparent incompability with Boost 1.59 (see Tim Smith's
email to this list on Aug 18).  Unfortunately, I don't seem to be able to
reach MacPort's bugDB website right now, so I can't check to see if there's
an open ticket on this.

I've checked out a copy of the repository with
git clone https://github.com/ledger/ledger.git
and that appears to have succeeded.

Unfortunately, I'm not sure what to do next -- I'm a little confused by the
instructions at https://github.com/ledger/ledger, and I'm not sure
exactly which branch I want to be using.  Not ALPHA, certainly, and
presumably not the default branch.  I'm guessing RELEASE?

Unfortunately, following the directions on the web page for checking out
the RELEASE branch doesn't seem to work.  Running git checkout -b stable
v3.1 appears to succeed:

[ridcully:~/installers/ledger]$ git checkout -b stable v3.1
Switched to a new branch 'stable'

But then I can't build:

[ridcully:~/installers/ledger]$ ./acprep update
acprep: INFO: Invoking primary phase: update
acprep: INFO: Executing phase: update
acprep: INFO: Executing phase: pull
There is no tracking information for the current branch.
Please specify which branch you want to merge with.
See git-pull(1) for details

git pull remote branch

If you wish to set tracking information for this branch you can do so with:

git branch --set-upstream-to=origin/branch stable

acprep: ERROR: Execution failed: git pull

It's quite possible that I'm overlooking something extremely basic,
especially since I've essentially never used git before; I'm used to Hg and
SVN.

Any and all suggestions welcome.

Thanks,

Richard

-- 

--- 
You received this message because you are subscribed to the Google Groups 
Ledger group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ledger-cli+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: ledger-mode upcoming transactions improvements

[Richard Cobbe]

On Wed, Nov 26, 2014 at 04:12:21PM -0700, Craig Earls wrote:
 I don't know if anyone is using the upcoming transactions feature of
 ledger-mode.  If you do, I have just finished completing the date
 interpreter.  You can now specify things like:

 Every other Thursday starting on 2014/11/27
 2014/11/27+2Th

Oh, lovely!  I'm looking forward to being able to use this.  Thanks for
your efforts on this feature!

Richard

-- 

--- 
You received this message because you are subscribed to the Google Groups 
Ledger group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ledger-cli+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Multiple file support for ledger mode

[Richard Cobbe]

On Sun, Jul 20, 2014 at 08:47:35PM +0200, Johann Klähn wrote:
 Just a thought: Can you maybe do M-x toggle-debug-on-error and show where
 it originates?

Ok -- very sorry for the significant delay on this, but I've been super
busy and then sick.

I finally had a chance to reproduce; here's the stack trace:

Debugger entered--Lisp error: (wrong-type-argument window-live-p nil)
  select-window(nil)
  ledger-reconcile-refresh-after-save()
  run-hooks(after-save-hook)
  basic-save-buffer()
  ledger-reconcile-save()
  ledger-reconcile-finish()
  call-interactively(ledger-reconcile-finish nil nil)

If it helps, I also happened to get the same error with a very similar
stack trace during reconciliation when I saved main.ledger after editing a
transaction while the reconciliation buffer was open.

Debugger entered--Lisp error: (wrong-type-argument window-live-p nil)
  select-window(nil)
  ledger-reconcile-refresh-after-save()
  run-hooks(after-save-hook)
  basic-save-buffer()
  save-buffer(1)
  call-interactively(save-buffer nil nil)

Also, I probably should have mentioned originally that I'm using
ledger-mode v3.0.0.

Richard

-- 

--- 
You received this message because you are subscribed to the Google Groups 
Ledger group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ledger-cli+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Multiple file support for ledger mode

[Richard Cobbe]

On Sun, Jul 20, 2014 at 08:47:35PM +0200, Johann Klähn wrote:
 Just a thought: Can you maybe do M-x toggle-debug-on-error and show where
 it originates?

Sure -- I should have done that originally.  I'll do that as soon as I get
a chance and report.

Richard

-- 

--- 
You received this message because you are subscribed to the Google Groups 
Ledger group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ledger-cli+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Multiple file support for ledger mode

[Richard Cobbe]

On Wed, Jul 16, 2014 at 06:19:34AM -0700, Craig Earls wrote:
 I would like to see the specific elisp error that reconciliation
 threw.  The reconcile window is populated by output from ledger
 itself, so the included transactions should be there.  Right now I
 don't track to see what file the transaction came from, so this is
 probably what threw the error.

Ok, I just reproduced the error -- thanks for your patience!

The actual error message I got, in the minibuffer, upon hitting C-c C-c in
the reconciliation window was
Wrong type argument: window-live-p, nil

However, I happened to discover that it's actually more complicated than
I'd originally thought, as it appears to depend on the width of the Emacs
frame in which I'm doing the reconciliations!  In particular, I only get
the error if the window showing the ledger file is wider than
split-width-threshold.

In my normal configuration, split-width-threshold is 160, and the frame is
80 characters wide.  So, if the frame contains a single window
(main.ledger), then when I hit C-c C-r, the frame is split so that the
reconciliation buffer is below the window that displays the transaction I'm
currently pointing at in the reconciliation buffer.  Under this
configuration, when I hit C-c C-c, I get the error above.

However, when I was reconciling my checking account, I'd resized the Emacs
frame halfway through, because the reconciliation buffer assumes a window
wider than 80 characters.  I don't know the precise width, but I'm pretty
sure it was over split-width-threshold.  When I finished reconciliation, I
had two windows in the frame, one over the other, with the *reconciliation*
buffer in the bottom window.  Upon hitting C-c C-c in the reconciliation
buffer, Emacs then split the upper window horizontally, displaying
main.ledger in one window and included-file.ledger in the other -- so there
are two windows, side-by-side, in the space previously occupied by the
upper window.  And I didn't get the error message in this case.

(Sorry for such a long-winded explanation, but I couldn't figure out how to
make it shorter and still be precise about what I observed.)

Brief note: I'm working on MacOS 10.9.4, using emacs 24.3.1, patched with
YAMAMOTO Mitsuharu's support for AppKit Unicode rendering.  This Emacs
binary is a native OSX application, not an X client.  I rather doubt that
these details are relevant here, but I mention them out of thoroughness.

Richard

-- 

--- 
You received this message because you are subscribed to the Google Groups 
Ledger group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ledger-cli+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Multiple file support for ledger mode

[Richard Cobbe]

On Wed, Jul 16, 2014 at 06:19:34AM -0700, Craig Earls wrote:
 I would like to see the specific elisp error that reconciliation
 threw.  The reconcile window is populated by output from ledger
 itself, so the included transactions should be there.  Right now I
 don't track to see what file the transaction came from, so this is
 probably what threw the error.

Sure.  I'll try to re-create, but the next couple of days are pretty busy
for me, so it may take me a while.

Richard

-- 

--- 
You received this message because you are subscribed to the Google Groups 
Ledger group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ledger-cli+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Multiple file support for ledger mode

[Richard Cobbe]

On Tue, Jul 15, 2014 at 12:37:46PM -0700, Craig Earls wrote:
 Thanks.  Did you use includes?

Yes, I did use includes.

 Would you like ledger mode to provide a consolidated view of all files?

Based on my limited experience with this, I think it would be more useful
if reconciliation worked better with transactions spread across multiple
files.  My primary motivation for using multiple files was to keep the main
file clean, so having ledger-mode recombine all of those wouldn't really
help me.

It's been a few (busy!) days since I tried this, but as best as I
can recall, this is what I did:

  - one main file, main.ledger, that contains most transactions, but
includes files that define transactions in other accounts.

  - While visiting main.ledger, hit C-c C-r to reconcile an account A.
Most of the transactions that affect A are in main.ledger, but a small
number are in other files.

  - Reconciliation worked quite well -- in particular, I was impressed
that, as I visited the various transactions in the reconciliation
buffer, ledger-mode was able to display the correct transactions in the
other window, regardless of which file they were in.

  - However, once I'd finished and hit C-c C-c in the reconciliation
buffer, I got some sort of elisp error.  Unfortunately, I don't
remember the precise message; I can try to reconstruct if you'd like
more detail.

This error message only arises if I'm reconciling an account whose
transactions are spread across multiple files.  If all of the account's
transactions are in main.ledger, then reconcilation works fine.

(BTW, if it matters, I have ledger-narrow-on-reconcile set to nil, because
it doesn't play well with account aliases -- separate issue.)

Richard

-- 

--- 
You received this message because you are subscribed to the Google Groups 
Ledger group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ledger-cli+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: specifying transaction schedules in ledger-mode

[Richard Cobbe]

I'd hate to see ledger-mode's support for scheduled transactions removed 
entirely in favor of cron -- not least because I tend not to have my 
computer running 24-7, so I'd be worried about missing transactions that 
fall due on a day when the computer's off (because I'm out of town or 
something).

Additionally, I'm not sure cron would fit my usage pattern well.  I chiefly 
use scheduled transactions for various transactions (monthly or bi-weekly) 
that take money out of my checking account -- and in GnuCash, I 
specifically had them set to appear a week before the transaction actually 
posts, so I could make sure I have enough in the checking account to cover 
them.  (These are payments for which I don't get bills in advance -- things 
like automatic monthly transfers from checking into investment accounts, 
and automatic bi-weekly mortgage payments, and so forth.)

Right now, I rely on the fact that I start GnuCash often enough that I see 
the transaction pretty close to a week in advance, and that seems to work 
pretty well, although of course it's not foolproof.  If I had to use cron 
for something like this, I'd have to put a mechanism in place to notify me 
somehow, probably via email, that a scheduled transaction has posted.  As 
it is, even with ledger-mode, I'll have to get into the habit of hitting 
C-c C-u every time I open the file.

Another option that I'm still considering is just sitting down on Jan 1 or 
whenever and writing up (probably programmatically) a year's worth of 
recurring transactions into the ledger file directly, and then just running 
ledger bal every morning with the appropriate options to display the 
projected balance 7 days out.

Richard
Richard

On Tuesday, July 8, 2014 8:26:11 PM UTC-4, Craig Earls wrote:

 cron, I never even thought of it.  Brilliant.  There is probably even 
 an elisp parser already written than I can steal... 

 On Tue, Jul 8, 2014 at 4:38 PM, Eric Abrahamsen er...@ericabrahamsen.net 
 javascript: wrote: 
  Craig Earls ende...@gmail.com javascript: writes: 
  
  I have been very slowly working on exactly that for a long time. I 
  keep dithering on how to represent that kind of recurrence. So, since 
  you are the first to ask, what would you like it to look like? 
  
  Cron has been around for ages and is just about as expressive as you can 
  get -- maybe something based on that? 
  
  I was think of something like: 
  anchor date+ perodicity 
  For example every o 
  Third Monday starting on 2014-07-14 would be: 
  2014-07-14+3w 
  
  I have thought of other ways and all have merits. What would you 
  like. Keep in mind the requirement for specifying a starting point 
  
  On Tuesday, July 8, 2014, Richard Cobbe  
  rco...@gmail.com javascript: wrote: 
  
  (Please forgive me if this is a duplicate post -- I'm fairly new 
  to Google groups, and my first attempt apparently went off into 
  the ether rather than showing up on this list.) 
  
  I'm trying to transition from GnuCash to ledger, and I'm looking 
  for an equivalent to GnuCash's scheduled transactions.  I see 
  from the ledger-mode manual that there's some support for this 
  feature in Emacs, and I've played around with it and figured out 
  how to do simple things, like scheduling a transaction to run 
  every month on the 13th, say, by supplying a date in the form [*/ 
  */13]. 
  
  Is there a way to schedule a transaction to run every other 
  Monday?  I don't see how to fit that into the date syntax that's 
  described in the manual.  I took a quick look at 
  ledger-schedule.el, and ledger-schedule-descriptor-regex appears 
  to support more expressive date specifications than just [*/*/ 
  13], but it's going to take me a while to figure out what's going 
  on here.  In particular, ledger-schedule-constrain-day appears 
  not to support all of the possible options that the regex appears 
  to allow. 
  
  Ledger 3.0.3-20140608 on MacOS 10.9.4, for what it's worth.  Oh, 
  and Emacs 24.3.1. 
  
  Thanks! 
  
  Richard 
  
  -- 
  
  --- 
  You received this message because you are subscribed to the 
  Google Groups Ledger group. 
  To unsubscribe from this group and stop receiving emails from it, 
  send an email to ledger-cli+...@googlegroups.com javascript:. 
  For more options, visit https://groups.google.com/d/optout. 
  
  
  
  -- 
  Craig, Corona De Tucson, AZ 
  enderw88.wordpress.com 
  
  -- 
  
  --- 
  You received this message because you are subscribed to the Google 
  Groups Ledger group. 
  To unsubscribe from this group and stop receiving emails from it, 
  send an email to ledger-cli+unsubscribe-/ 
  jypxa39uh5...@public.gmane.org javascript:. 
  For more options, visit https://groups.google.com/d/optout. 
  
  -- 
  
  --- 
  You received this message because you are subscribed to the Google 
 Groups Ledger group. 
  To unsubscribe from

Re: specifying transaction schedules in ledger-mode

[Richard Cobbe]

The initial impetus was the difficulty in keeping GnuCash running happily 
on MacOS, despite the efforts of the fine folks at MacPorts. [1]  In an 
interesting synchronicity, the most recent problem caused GnuCash to crash 
any time I tried to open the scheduled transaction editor.  :-)  This sort 
of thing (including that specific failure mode) has happened before, so 
I've decided not run GnuCash on MacOS any more and am now making do with an 
Ubuntu virtual machine, until I can get a replacement for GnuCash in 
place.  (That should continue to work basically indefinitely, but I find 
working in VMs to be annoying and prefer to do so as little as possible.)

More generally, I'm not a fan of GnuCash's bulk -- and since I have 
MacPorts configured to build everything from source on one of my computers 
(for reasons that have nothing to do with GnuCash), a GnuCash upgrade often 
takes a really long time.  (Any time I have to rebuild webkit-gtk, I know 
it's going to be a while.)

I also like Ledger's use of a more human-readable data file format, because 
it works better with version control and particuarly merging and conflict 
resolution.  (I do keep my Gnucash files, uncompressed, in version control, 
but I don't know of a version control system that really handles XML data 
particularly well -- certainly the odd merge and conflict have been pretty 
painful to resolve, both under SVN and Mercurial.)  Of course, XML does 
have benefits -- in particular, I may yet reach a point when I'm tired of 
migrating data using the 10-fingered-transfer method and start trying to 
programmatically convert the XML.  (At least it's 10 fingers, and not just 
2!)

Richard

[1] Given that ragging on MacPorts is fashionable in certain quarters, I 
should point out that this isn't irony; I'm generally quite happy with 
their system.

On Tuesday, July 8, 2014 8:46:08 PM UTC-4, Martin Blais wrote:

 Just curious... what are your reasons for switching away from GnuCash?



 On Tue, Jul 8, 2014 at 4:02 PM, Richard Cobbe rco...@gmail.com 
 javascript: wrote:

 (Please forgive me if this is a duplicate post -- I'm fairly new to 
 Google groups, and my first attempt apparently went off into the ether 
 rather than showing up on this list.)

 I'm trying to transition from GnuCash to ledger, and I'm looking for an 
 equivalent to GnuCash's scheduled transactions.  I see from the ledger-mode 
 manual that there's some support for this feature in Emacs, and I've played 
 around with it and figured out how to do simple things, like scheduling a 
 transaction to run every month on the 13th, say, by supplying a date in the 
 form [*/*/13].

 Is there a way to schedule a transaction to run every other Monday?  I 
 don't see how to fit that into the date syntax that's described in the 
 manual.  I took a quick look at ledger-schedule.el, and 
 ledger-schedule-descriptor-regex appears to support more expressive date 
 specifications than just [*/*/13], but it's going to take me a while to 
 figure out what's going on here.  In particular, 
 ledger-schedule-constrain-day appears not to support all of the possible 
 options that the regex appears to allow.

 Ledger 3.0.3-20140608 on MacOS 10.9.4, for what it's worth.  Oh, and 
 Emacs 24.3.1.

 Thanks!

 Richard

 -- 

 --- 
 You received this message because you are subscribed to the Google Groups 
 Ledger group.
 To unsubscribe from this group and stop receiving emails from it, send an 
 email to ledger-cli+...@googlegroups.com javascript:.
 For more options, visit https://groups.google.com/d/optout.




-- 

--- 
You received this message because you are subscribed to the Google Groups 
Ledger group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ledger-cli+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: specifying transaction schedules in ledger-mode

[Richard Cobbe]

On Wednesday, July 9, 2014 10:00:47 PM UTC-4, Richard Cobbe wrote:

 The initial impetus was the difficulty in keeping GnuCash running happily 
 on MacOS, despite the efforts of the fine folks at MacPorts. [1]  In an 
 interesting synchronicity, the most recent problem caused GnuCash to crash 
 any time I tried to open the scheduled transaction editor.  :-)  This sort 
 of thing (including that specific failure mode) has happened before, so 
 I've decided not run GnuCash on MacOS any more and am now making do with an 
 Ubuntu virtual machine, until I can get a replacement for GnuCash in 
 place.  (That should continue to work basically indefinitely, but I find 
 working in VMs to be annoying and prefer to do so as little as possible.)

 More generally, I'm not a fan of GnuCash's bulk -- and since I have 
 MacPorts configured to build everything from source on one of my computers 
 (for reasons that have nothing to do with GnuCash), a GnuCash upgrade often 
 takes a really long time.  (Any time I have to rebuild webkit-gtk, I know 
 it's going to be a while.)

 I also like Ledger's use of a more human-readable data file format, 
 because it works better with version control and particuarly merging and 
 conflict resolution.  (I do keep my Gnucash files, uncompressed, in version 
 control, but I don't know of a version control system that really handles 
 XML data particularly well -- certainly the odd merge and conflict have 
 been pretty painful to resolve, both under SVN and Mercurial.)  Of course, 
 XML does have benefits -- in particular, I may yet reach a point when I'm 
 tired of migrating data using the 10-fingered-transfer method and start 
 trying to programmatically convert the XML.  (At least it's 10 fingers, and 
 not just 2!)


Forgot to mention: another advantage of this is that it makes it much less 
likely that I'll add a scheduled transaction to the main ledger file twice, 
by mistake.

Richard

-- 

--- 
You received this message because you are subscribed to the Google Groups 
Ledger group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ledger-cli+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: specifying transaction schedules in ledger-mode

[Richard Cobbe]

On Tuesday, July 8, 2014 5:34:32 PM UTC-4, Craig Earls wrote:

 I have been very slowly working on exactly that for a long time. I keep 
 dithering on how to represent that kind of recurrence. So, since you are 
 the first to ask, what would you like it to look like?

 I was think of something like:
 anchor date+ perodicity
 For example every o
 Third Monday starting on 2014-07-14 would be:
 2014-07-14+3w

 I have thought of other ways and all have merits. What would you like. 
 Keep in mind the requirement for specifying a starting point 


Yeah, there's no obviously correct syntax, at least not that I can see, 
although the starting date clearly has to be part of the solution, as you 
say.  I'd be happy with your proposal.

Richard

-- 

--- 
You received this message because you are subscribed to the Google Groups 
Ledger group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ledger-cli+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

scheduling bi-weekly transactions in ledger-mode

[Richard Cobbe]

I'm in the process of transitioning from Gnucash to Ledger (as keeping 
Gnucash working consistently on MacOS is challenging, despite the best 
efforts of the MacPorts folks).

I will miss Gnucash's support for scheduled transactions, though, if I 
can't figure out a good way to do this in Ledger.  That is, I'd like to be 
able to set up a transaction that automatically charges a specific amount 
to my credit card every month on the 13th, say.  From the ledger-mode 
manual, I see that ledger-mode at least has some support for this, but this 
section is still a work in progress.

I've played around with the feature, and I see how to make it work for 
transactions that always occur on the same day of the month.  One question, 
though: is there support for scheduling transactions to occur, for example, 
every 2 weeks?  I don't see an obvious way to work that into the 
generalized date notation [*/*/13].  I took a look at ledger-schedule.el, 
and the definition of ledger-schedule-descriptor-regex appears to allow 
more sophisticated specifications than that, but it's going to take me a 
while to puzzle out exactly what's going on here.  A very superficial 
reading of ledger-schedule-constrain-day and related functions suggests 
that not all of the features allowed in the regex are currently supported.

(Ledger 3.0.3-20140608, MacOS 10.9.4, for what it's worth.)

Thanks!

Richard

-- 

--- 
You received this message because you are subscribed to the Google Groups 
Ledger group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ledger-cli+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

specifying transaction schedules in ledger-mode

[Richard Cobbe]

(Please forgive me if this is a duplicate post -- I'm fairly new to Google 
groups, and my first attempt apparently went off into the ether rather than 
showing up on this list.)

I'm trying to transition from GnuCash to ledger, and I'm looking for an 
equivalent to GnuCash's scheduled transactions.  I see from the ledger-mode 
manual that there's some support for this feature in Emacs, and I've played 
around with it and figured out how to do simple things, like scheduling a 
transaction to run every month on the 13th, say, by supplying a date in the 
form [*/*/13].

Is there a way to schedule a transaction to run every other Monday?  I 
don't see how to fit that into the date syntax that's described in the 
manual.  I took a quick look at ledger-schedule.el, and 
ledger-schedule-descriptor-regex appears to support more expressive date 
specifications than just [*/*/13], but it's going to take me a while to 
figure out what's going on here.  In particular, 
ledger-schedule-constrain-day appears not to support all of the possible 
options that the regex appears to allow.

Ledger 3.0.3-20140608 on MacOS 10.9.4, for what it's worth.  Oh, and Emacs 
24.3.1.

Thanks!

Richard

-- 

--- 
You received this message because you are subscribed to the Google Groups 
Ledger group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to ledger-cli+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.