Re: Moving ledger-mode out of the main ledger repository

[John Wiegley]

> "A" == Alexis   writes:

A> can you include the doc/ledger-mode.texi file in the ledger-mode repo
A> also? I think it makes sense to move the documentation to the sources.

Done, complete with the history for that file along the second merge parent.

-- 
John Wiegley  GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com  60E1 46C4 BD1A 7AC1 4BA2

-- 

--- 
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 use ledger in my (unusual) workflow?

[Marcin Borkowski]

On 2016-08-05, at 02:53, Simon Michael  wrote:

> Would envelope budgeting work ? See
> http://plaintextaccounting.org/#budgeting ->
> envelope budgeting with plain transactions
> for an example of what I mean.

Shameless plug: a simple example on my blog:
http://mbork.pl/2016-07-18_Ledger_%e2%80%93_virtual_postings_aka_envelopes

Hth,

-- 
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Faculty of Mathematics and Computer Science
Adam Mickiewicz University

-- 

--- 
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: Feature idea: custom named reports!

[Josh]

Seeing other people's input on this topic, I suppose that there are already
lots of other good ways to achieve the same thing. Shell aliases, shell
scripts, scripts in other languages, editor hacks, etc. are all far more
flexible, allowing multiple commands, parsing and processing of the output,
interactivity, and so on. Sure, they do tie you to a particular tool set,
limiting portability, but that's true no matter what: any system capable of
describing non-trivial reports is going to be so complex as to essentially
be a complete programming language, so we might as well just each pick an
existing language we like.

On Thu, Aug 4, 2016 at 11:13 AM, Simon Michael  wrote:

> Josh Hanson  writes:
> >>> The syntax for the directive might be:
> >>> *report  *To run the
> >> report,
> >>> you'd run at the command line: *ledger report *
>
> I think it's a pretty attractive idea.
>
> Pro:
>
> - report commands are detailed and hard to recall. Saving them
>   (in a standard, easily accessible, cross-platform way) is good.
>
> - they are often quite specific to a journal. Having them
> version-controlled and refactorable together is good.
>
> Con:
>
> - your proposal allows only single ledger commands. It could allow
> arbitrary command lines too I guess.
>
> - reports expressed as command lines are fairly specific to the cli, not
> so good for other uis (I'm thinking of hledger-ui and hledger-web). I
> wonder if there's a more portable way to describe them.
>
> - some report commands are generic and you may not want to redeclare them
> in every journal you work with, creating a maintenance task. Where to put
> those ?
>
> I was thinking of a different scheme: aliases (not just reports) defined
> in the user's config, which can run arbitrary command lines, just like git
> does it.
>
> Richard Lawrence  wrote:
> >> I do wonder if ledger itself is the best place to implement it, though.
> >> You can already mostly achieve what you want with shell aliases.  That's
> >> what I do.
>
> Me too. I have many shell aliases (and when I must, functions), defined in
> a single bashrc file kept alongside journals. I tend to forget what's in
> there and they get out of date easily. I suppose a more specific
> JOURNALFILE.bashrc might be good. Shell scripts are harder to share with
> others, eg windows and non-bash users.
>
> nx wrote:
>
>> Might be better to have a link to a repo on the plaintextaccounting.org
>> site with shellscripts for running complex reports.
>>
>
> +1
>
>
> --
>
> --- You received this message because you are subscribed to a topic in the
> Google Groups "Ledger" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/to
> pic/ledger-cli/A2GD2VKEsuw/unsubscribe.
> To unsubscribe from this group and all its topics, 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: "Imprecise" Transaction times

[Simon Michael]

On 7/28/16 11:18 PM, Scott Wallace wrote:

Currently, my initial thoughts would be to generate two versions of each
account to deal with different transaction timing (I'd probably use my own
format for entering the data and then generate the journal file from this
with a script).

Any other thoughts for me?


Interesting question. I think what you are thinking there (generate 
journals describing each scenario) is best, short of building a whole 
new command/tool for it.



--

--- 
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 use ledger in my (unusual) workflow?

[Simon Michael]

Would envelope budgeting work ? See
http://plaintextaccounting.org/#budgeting ->
envelope budgeting with plain transactions
for an example of what I mean.

On 7/27/16 8:17 AM, Alex wrote:

I'm trying to use ledger in a way that helps my wife and me budget. I tried
to do so last year, but we didn't end up sticking to it. We have settled on
allocating funds by month and further splitting by week; the difficulty is
that we often find ourselves needing flexibility, e.g. to get groceries at
the end of one week rather than at the beginning of the next, so purely
date-based methods don't work. We are currently using a Google Sheets
document, which is working reasonably well, but I'm missing the ability to
query like I would have with ledger.

I haven't found one yet, so I'm asking: is there a feature in ledger that
makes these kinds of "custom pay periods" easy, or even possible, to manage?

Thanks.




--

--- 
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: Moving ledger-mode out of the main ledger repository

[Alexis]

Hi John,

can you include the doc/ledger-mode.texi file in the ledger-mode repo
also? I think it makes sense to move the documentation to the sources.


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.

Re: Moving ledger-mode out of the main ledger repository

[Craig Earls]

I agree. I will work this this weekend.

On Thursday, August 4, 2016, Simon Michael  wrote:

> This is great. It will be clearer what's happening in each project. It's
> also nice that ledger-mode's commit history was preserved.
>
> Craig, how about moving ledger-mode issue tracking to github ? This seems
> like a great time.
>
> --
>
> --- 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.
>


-- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Moving ledger-mode out of the main ledger repository

[Jacob MacDonald]

Submitting a quick PR to MELPA here:
https://github.com/melpa/melpa/pull/4099, unless @purcell is watching this
mailing list?

On Thu, Aug 4, 2016 at 12:10 PM Simon Michael  wrote:

> This is great. It will be clearer what's happening in each project. It's
> also nice that ledger-mode's commit history was preserved.
>
> Craig, how about moving ledger-mode issue tracking to github ? This
> seems like a great time.
>
> --
>
> ---
> 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: Moving ledger-mode out of the main ledger repository

[Simon Michael]

This is great. It will be clearer what's happening in each project. It's 
also nice that ledger-mode's commit history was preserved.


Craig, how about moving ledger-mode issue tracking to github ? This 
seems like a great time.


--

--- 
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: Wrote some code to automatically sync pricedb

[Alexandre Rademaker]

I finally managed to integrate the configuration of Preet code with my .emacs 
file:

(eval-after-load 'flycheck
  '(require 'flycheck-ledger))

(use-package ledger-mode
  :mode "\\.dat"
  :init
  (setq ledger-reports
'(("mes" "ledger -f %(ledger-file) -M reg ^expenses")
  ("bal" "ledger -f %(ledger-file) bal")
  ("reg" "ledger -f %(ledger-file) reg")
  ("payee"   "ledger -f %(ledger-file) reg @%(payee)")
  ("account" "ledger -f %(ledger-file) reg %(account)")))
  :config
  (load-file "~/.emacs.d/ledger-pricedb/ledger-pricedb.el")
  (setq ledger-binary-path "~/ledger/ledger")
  (set 'ledger-pricedb--stocks '("IBM" "NFLX"))
  (set 'ledger-pricedb--pricedb "~/ledger/.pricedb")
  (setq ledger-post-amount-alignment-at :decimal)
  :bind ("C-c u" . ledger-pricedb-save-pricedb))


Does anyone knows how to make sure that flycheck-ledger is loaded and if it is 
running? I tried to write some invalid entries and nothing came up. 

Best,

--
Alexandre Rademaker
http://arademaker.github.io 
http://researcher.ibm.com/person/br-alexrad 






> On Aug 4, 2016, at 11:47 AM, Alexandre Rademaker  wrote:
> 
> Manuel, these are two very different projects! Preet presented un iterative 
> approach for fill the buffer automatically, completely integrated with Emacs, 
> you suggest some python scripts as wrappers to the ledger cli, right? I would 
> advise you to add examples of how to use your code. 
> 
> Anyway, I  prefer the Preet approach! ;-)
> 
> []s
> Alexandre
> 
>> On Aug 3, 2016, at 11:55 PM, Manuel Amador (Rudd-O)  
>> wrote:
>> 
>> On 08/01/2016 01:20 AM, Preet Bhinder wrote:
>>> I started using ledger for tracking investments and net worth. It was
>>> becoming a bit painful keeping the .pricedb file upto date so I wrote
>>> some code to do it automatically through Yahoo! Finance.
>>> 
>>> Posting in the hopes of it being useful for somebody
>>> else: https://github.com/mbhinder/ledger-pricedb
>>> 
>>> I taught myself a little elisp while writing this today so I'm sure
>>> the code is atrocious - please be gentle. Any cleanup/feature addition
>>> work is welcome, please submit PRs to github.
>> 
>> Nice project.  Can I ask you to contribute to updateprices in
>> https://github.com/Rudd-O/ledgerhelpers?  It would mean the world to me.
>> 
>> -- 
>>   Rudd-O
>>   http://rudd-o.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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Feature idea: custom named reports!

[Simon Michael]

Josh Hanson  
writes:

>>> The syntax for the directive might be:
>>> *report  *To run the
>> report,
>>> you'd run at the command line: *ledger report *

I think it's a pretty attractive idea.

Pro:

- report commands are detailed and hard to recall. Saving them
  (in a standard, easily accessible, cross-platform way) is good.

- they are often quite specific to a journal. Having them 
version-controlled and refactorable together is good.


Con:

- your proposal allows only single ledger commands. It could allow 
arbitrary command lines too I guess.


- reports expressed as command lines are fairly specific to the cli, not 
so good for other uis (I'm thinking of hledger-ui and hledger-web). I 
wonder if there's a more portable way to describe them.


- some report commands are generic and you may not want to redeclare 
them in every journal you work with, creating a maintenance task. Where 
to put those ?


I was thinking of a different scheme: aliases (not just reports) defined 
in the user's config, which can run arbitrary command lines, just like 
git does it.


Richard Lawrence  wrote:
>> I do wonder if ledger itself is the best place to implement it, though.
>> You can already mostly achieve what you want with shell aliases.  That's
>> what I do.

Me too. I have many shell aliases (and when I must, functions), defined 
in a single bashrc file kept alongside journals. I tend to forget what's 
in there and they get out of date easily. I suppose a more specific 
JOURNALFILE.bashrc might be good. Shell scripts are harder to share with 
others, eg windows and non-bash users.


nx wrote:

Might be better to have a link to a repo on the plaintextaccounting.org
site with shellscripts for running complex reports.


+1


--

--- 
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.