Who Says Beancount Documentation Style is Boring !!!!

[Vinit Khandagle]

Well let me start by thanking @Martin for his awesome writing skills and 
explanation of Accounting. I am just getting into plain text accounting. 
When I saw that beancount documentation is on google docs, rather than a 
wiki style or something the usual way. I was like what a lame idea of not 
working towards getting the documentation in order coz when you have to ask 
something around most of the time the response is RTFM and if that's not 
pretty and quick its a disaster reading the docs. 

But as I started reading through the documents, it felt like I am reading a 
paperback copy of a book. No clutter no fancy coloring or distractions, 
just plain text to read and the focus is on the content and explanation of 
concepts rather than having a fancy doc site. I also got to read Martin's 
argument about using google docs as the platform for documentation and I 
must say I think the idea is really amazing. I think this is perfect for 
beancount.

I am really enjoying reading the docs, though I have just started and 
Martin has a very unique way of explaining the accounting concepts. I just 
put the browser in Darkmode and voila the text just pop out :)

So thanks to Martin and everyone contributing to the docs.


-- 
You received this message because you are subscribed to the Google Groups 
"Beancount" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beancount+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beancount/aa980a0d-05cf-4608-bccf-9623fe05275b%40googlegroups.com.

Re: Who Says Beancount Documentation Style is Boring !!!!

[Vinit Khandagle]

I Liked this explanation of credit cards "

*What we have is a meal sitting in our stomach (a positive number of $ of 
“Restaurant”)*." :)

On Sunday, May 17, 2020 at 3:17:03 AM UTC+5:30, Vinit Khandagle wrote:
>
> Well let me start by thanking @Martin for his awesome writing skills and 
> explanation of Accounting. I am just getting into plain text accounting. 
> When I saw that beancount documentation is on google docs, rather than a 
> wiki style or something the usual way. I was like what a lame idea of not 
> working towards getting the documentation in order coz when you have to ask 
> something around most of the time the response is RTFM and if that's not 
> pretty and quick its a disaster reading the docs. 
>
> But as I started reading through the documents, it felt like I am reading 
> a paperback copy of a book. No clutter no fancy coloring or distractions, 
> just plain text to read and the focus is on the content and explanation of 
> concepts rather than having a fancy doc site. I also got to read Martin's 
> argument about using google docs as the platform for documentation and I 
> must say I think the idea is really amazing. I think this is perfect for 
> beancount.
>
> I am really enjoying reading the docs, though I have just started and 
> Martin has a very unique way of explaining the accounting concepts. I just 
> put the browser in Darkmode and voila the text just pop out :)
>
> So thanks to Martin and everyone contributing to the docs.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Beancount" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beancount+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beancount/92bdb6d2-3702-4b0c-809e-54ffdce9b2bc%40googlegroups.com.

Re: Not linking through furius.ca

[Vinit Khandagle]

Well this a theme that is quite often used with MKdocs and I guess its 
quite popular too. Just for some info
https://squidfunk.github.io/mkdocs-material/


On Saturday, May 23, 2020 at 5:57:26 PM UTC+5:30, Vinit Khandagle wrote:
>
> This is super cool. I think MKdocs is perfect fit. I believe Docker also 
> uses mkdos at the backend. Atleast they did when they were in their initial 
> years. I personally use it to track my own markdown files and stuff. 
>
> On Friday, May 22, 2020 at 9:09:18 PM UTC+5:30, Martin Blais wrote:
>>
>> Thanks to the work of Kirill Goncharov (and Dominik Aumayr's predecessor 
>> static codebase reference) the conversion of Google docs to HTML via 
>> Markdown works quite well. The final product is really slick: 
>> https://beancount.github.io/docs/. I think in terms of 
>> documentation this is the sweet spot I was hoping for: sources in gdocs 
>> that makes it possible to just go to a doc and start typing immediately 
>> (zero overhead to make fixes or rewrite portions), and for anyone else to 
>> insert a comment or suggestion, but with an output familiar for an open 
>> source project (familiar web pages with text). What we trade off for 
>> changes managed via commits and the associated history, we gain in 
>> collaboration and much more resultant documentation (I never would have 
>> written this much otherwise).
>>
>> As part of the Github migration, another thing I'd like to change about 
>> the documentation eventually is the conversion of links between Google docs 
>> from redirects through my website furius.ca, to use some other more 
>> permanent means of redirect.
>>
>> The history of it is that began to write the docs I wanted to have a way 
>> to refer to them by name, and the Google docs addresses aren't 
>> memorable (they include a long auto-generated "document id" root at 
>> docs.google.com/document/d/). I created a redirect configuration rooted 
>> at http://furius.ca/beancount/doc/. This way I could send links 
>> that were more or less self-explanatory and that I could remember, with a 
>> well-known public name (e.g., http://furius.ca/beancount/doc/install), I 
>> would just type them in without having to look them up while writing an 
>> email. I pretty much consistently inserted such a link at the top of every 
>> one of the documents below the title.  This would also allow me to change 
>> which document an existing link points to, a capability I did not have to 
>> use very often, but which was handy the few times I rewrote some of the 
>> documents, e.g. http://furius.ca/beancount/doc/export.
>>
>> Overall the system works well. Here's the problem though: my website is 
>> generously hosted by friends in their web design & development company. 
>> Occasionally - several times per year - there's a network configuration 
>> change or an outage and my server is inaccessible, sometimes for 1-2 days. 
>> This means the links also aren't resolvable (the server can't respond with 
>> a redirect) and if you're reaching the docs through an email thread or on 
>> the Google docs source, the links simply won't resolve. This isn't great. 
>> In Kirill's HTML conversion the links look like they have been mapped: 
>> https://github.com/beancount/docs/blob/master/index.json so they link 
>> within the generated site, but it would still be nice to be able to send 
>> links by name and not rely on e.g., the generated names of the markdown 
>> files.
>>
>> I'd like to move the link root over to something hosted at Github so the 
>> docs aren't reliant on my server, the future of which is unclear (I don't 
>> have plans to remove it but I don't really need it either). I wonder if 
>> it's possible to create redirects rooted at something like 
>> http://beancount.github.io/, http://beancount.github.io/docs/g/, 
>> or something like that. Maybe there could be a mapping to both the gdocs or 
>> the markdown generated docs with the same name, e.g.:
>> http://beancount.github.io/docs/g/export -> 
>> https://docs.google.com/document/d/1mNyE_ONuyEkF_I2l6V_AoAU5HJgI654AOBhHsnNPPqw/
>>  
>> <https://docs.google.com/document/d/1mNyE_ONuyEkF_I2l6V_AoAU5HJgI654AOBhHsnNPPqw/edit>
>> http://beancount.github.io/docs/m/export -> 
>> https://beancount.github.io/docs/12_exporting_your_portfolio.html
>> Given the scope this project has taken, I could even register a short 
>> domain name for this purpose (e.g. beandocs.io?). 
>>
>> This is just an idea. I know how to do this on an Apache web server.
>> But can it be done on something hosted at Github?
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Beancount" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beancount+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beancount/6f09fa27-20ea-48e7-8f00-81c7cf569a15%40googlegroups.com.

Re: Not linking through furius.ca

[Vinit Khandagle]

This is super cool. I think MKdocs is perfect fit. I believe Docker also 
uses mkdos at the backend. Atleast they did when they were in their initial 
years. I personally use it to track my own markdown files and stuff. 

On Friday, May 22, 2020 at 9:09:18 PM UTC+5:30, Martin Blais wrote:
>
> Thanks to the work of Kirill Goncharov (and Dominik Aumayr's predecessor 
> static codebase reference) the conversion of Google docs to HTML via 
> Markdown works quite well. The final product is really slick: 
> https://beancount.github.io/docs/. I think in terms of documentation this 
> is the sweet spot I was hoping for: sources in gdocs that makes it possible 
> to just go to a doc and start typing immediately (zero overhead to make 
> fixes or rewrite portions), and for anyone else to insert a comment or 
> suggestion, but with an output familiar for an open source project 
> (familiar web pages with text). What we trade off for changes managed via 
> commits and the associated history, we gain in collaboration and much more 
> resultant documentation (I never would have written this much otherwise).
>
> As part of the Github migration, another thing I'd like to change about 
> the documentation eventually is the conversion of links between Google docs 
> from redirects through my website furius.ca, to use some other more 
> permanent means of redirect.
>
> The history of it is that began to write the docs I wanted to have a way 
> to refer to them by name, and the Google docs addresses aren't 
> memorable (they include a long auto-generated "document id" root at 
> docs.google.com/document/d/). I created a redirect configuration rooted 
> at http://furius.ca/beancount/doc/. This way I could send links 
> that were more or less self-explanatory and that I could remember, with a 
> well-known public name (e.g., http://furius.ca/beancount/doc/install), I 
> would just type them in without having to look them up while writing an 
> email. I pretty much consistently inserted such a link at the top of every 
> one of the documents below the title.  This would also allow me to change 
> which document an existing link points to, a capability I did not have to 
> use very often, but which was handy the few times I rewrote some of the 
> documents, e.g. http://furius.ca/beancount/doc/export.
>
> Overall the system works well. Here's the problem though: my website is 
> generously hosted by friends in their web design & development company. 
> Occasionally - several times per year - there's a network configuration 
> change or an outage and my server is inaccessible, sometimes for 1-2 days. 
> This means the links also aren't resolvable (the server can't respond with 
> a redirect) and if you're reaching the docs through an email thread or on 
> the Google docs source, the links simply won't resolve. This isn't great. 
> In Kirill's HTML conversion the links look like they have been mapped: 
> https://github.com/beancount/docs/blob/master/index.json so they link 
> within the generated site, but it would still be nice to be able to send 
> links by name and not rely on e.g., the generated names of the markdown 
> files.
>
> I'd like to move the link root over to something hosted at Github so the 
> docs aren't reliant on my server, the future of which is unclear (I don't 
> have plans to remove it but I don't really need it either). I wonder if 
> it's possible to create redirects rooted at something like 
> http://beancount.github.io/, http://beancount.github.io/docs/g/, 
> or something like that. Maybe there could be a mapping to both the gdocs or 
> the markdown generated docs with the same name, e.g.:
> http://beancount.github.io/docs/g/export -> 
> https://docs.google.com/document/d/1mNyE_ONuyEkF_I2l6V_AoAU5HJgI654AOBhHsnNPPqw/
>  
> 
> http://beancount.github.io/docs/m/export -> 
> https://beancount.github.io/docs/12_exporting_your_portfolio.html
> Given the scope this project has taken, I could even register a short 
> domain name for this purpose (e.g. beandocs.io?). 
>
> This is just an idea. I know how to do this on an Apache web server.
> But can it be done on something hosted at Github?
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Beancount" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beancount+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beancount/28055b2c-7df9-424b-b816-0aff53bf12d7%40googlegroups.com.

Re: Who Says Beancount Documentation Style is Boring !!!!

[Vinit Khandagle]

Wow!!! That's gona be interesting. Looking forward to it. 

On Sunday, May 17, 2020 at 6:42:16 AM UTC+5:30, Martin Blais wrote:
>
> Thanks for the nice words Vinit, it's always nice to hear from people who 
> are enjoying the production
> Though the source will remain in gdocs, I'd like to integrate Kirill 
> Goncharov's super nice conversion eventually
> Probably the next version (I'm already making some secret motions and 
> steps toward that... more to come soon, very likely)
>
>
>
> On Sat, May 16, 2020 at 5:47 PM Vinit Khandagle  > wrote:
>
>> Well let me start by thanking @Martin for his awesome writing skills and 
>> explanation of Accounting. I am just getting into plain text accounting. 
>> When I saw that beancount documentation is on google docs, rather than a 
>> wiki style or something the usual way. I was like what a lame idea of not 
>> working towards getting the documentation in order coz when you have to ask 
>> something around most of the time the response is RTFM and if that's not 
>> pretty and quick its a disaster reading the docs. 
>>
>> But as I started reading through the documents, it felt like I am reading 
>> a paperback copy of a book. No clutter no fancy coloring or distractions, 
>> just plain text to read and the focus is on the content and explanation of 
>> concepts rather than having a fancy doc site. I also got to read Martin's 
>> argument about using google docs as the platform for documentation and I 
>> must say I think the idea is really amazing. I think this is perfect for 
>> beancount.
>>
>> I am really enjoying reading the docs, though I have just started and 
>> Martin has a very unique way of explaining the accounting concepts. I just 
>> put the browser in Darkmode and voila the text just pop out :)
>>
>> So thanks to Martin and everyone contributing to the docs.
>>
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Beancount" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to bean...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/beancount/aa980a0d-05cf-4608-bccf-9623fe05275b%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/beancount/aa980a0d-05cf-4608-bccf-9623fe05275b%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Beancount" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beancount+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beancount/a351661c-7ea0-499e-a535-f7fde3d22457%40googlegroups.com.

Re: Envelope Plugin for Fava

[Vinit Khandagle]

Well I think this could be a possible thing happening is that the Flask 
route is not happening correctly for some reason

```

> curl http://localhost:5000/beancount/extension/EnvelopeBudget/
> 
> 404 Not Found
> Not Found
> The requested URL was not found on the server. If you entered the URL 
> manually please check your spelling and try again.


```

On Sunday, May 10, 2020 at 12:03:56 AM UTC+5:30, Brian Ryall wrote:
>
>
> Github Project Link: https://github.com/bryall/fava-envelope
>
> I am creating an envelope budgeting plugin for fava. I have finished the 
> initial prototype (also uploaded to pypi) and I am looking for alpha 
> testers and contributors to help improve this functionality. I know this 
> has been a highly requested feature in the beancount community that I want 
> to. I would love comments and suggestions to help improve this plugin
>
> Thanks
>
>
> About the plugin:
> * It builds upon your beancount journal by using custom directives
> * You specify which accounts you want in your budget
> * You can map expenses to a new name
>
>
> Future Additions:
> * Charts (income/Expenses for budget accounts, etc)
> * Output beancount report?
>

-- 
You received this message because you are subscribed to the Google Groups 
"Beancount" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beancount+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beancount/d201c0b7-ccd3-4dbc-aae1-196fbae6fefa%40googlegroups.com.

Re: Envelope Plugin for Fava

[Vinit Khandagle]

This is gona be really useful. I definitely would like to see this mature 
in Beancount. I used and tested MoneyDance and it has a good way to the 
envelope system. I really want to use this for beancount. I tried the steps 
mentioned on the git repo but I am not able to get this working. Fava keeps 
complaining that it failed to load the plugin looks like a very generic 
error. 



On Sunday, May 10, 2020 at 12:03:56 AM UTC+5:30, Brian Ryall wrote:
>
>
> Github Project Link: https://github.com/bryall/fava-envelope
>
> I am creating an envelope budgeting plugin for fava. I have finished the 
> initial prototype (also uploaded to pypi) and I am looking for alpha 
> testers and contributors to help improve this functionality. I know this 
> has been a highly requested feature in the beancount community that I want 
> to. I would love comments and suggestions to help improve this plugin
>
> Thanks
>
>
> About the plugin:
> * It builds upon your beancount journal by using custom directives
> * You specify which accounts you want in your budget
> * You can map expenses to a new name
>
>
> Future Additions:
> * Charts (income/Expenses for budget accounts, etc)
> * Output beancount report?
>

-- 
You received this message because you are subscribed to the Google Groups 
"Beancount" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beancount+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beancount/b11f03d6-b4b0-4560-ac1b-311644686819%40googlegroups.com.

bean-price fetching issue with yahoo

[Vinit Khandagle]

I am seeing the below error while trying to fetch prices from yahoo, not 
sure how to solve this issues

bean-price -e "USD:yahoo/AAPL" --no-cache
```
File 
"/Users/vkbytes/miniforge3/lib/python3.9/site-packages/beanprice/sources/yahoo.py",
 
line 129, in get_latest_price
raise YahooError("%s (ticker: %s)" % (error, ticker)) from error
beanprice.sources.yahoo.YahooError: Status 401: {'code': 'Unauthorized', 
'description': 'Invalid Cookie'} (ticker: AAPL)
```

-- 
You received this message because you are subscribed to the Google Groups 
"Beancount" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beancount+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beancount/ac412bb4-a6b0-429f-9e9f-913a205eca4dn%40googlegroups.com.

Re: How should I define linked documents when using includes?

[Vinit Khandagle]

One way I solved this problem was that after the entering the transaction I 
dragged and dropped the file on the Payee Entry this creates the correct 
linking and creates the account structure in the documents section 
correctly. 

On Saturday, May 6, 2023 at 1:43:44 AM UTC+5:30 Daniel Schultz wrote:

> I'm trying my hand at reorganizing my books so that I have separate 
> ledgers for each client, and finding that `document`s are not properly 
> linking
>
> I use fava with the plugin "fava.plugins.link_documents"
>
> My file structure is something like this:
>
> ```
> | - files
> | | - Assets
> | | | - MyClient
> | | | | - 2022-01-01-invoice-1.pdf
> | - ledgers
> | | - myClient.beancount
> | - ledger.beancount
> ```
>
> In my `ledger.beancount` I have the documents setting set:
>
> ```
> option "documents" "files"
> ```
>
> In `myClient.beancount` I have a transaction:
>
> ```
> 2022-01-01 * "My Client" "client invoice"
>   document: "files/Assets/MyClient/2022-01-01-invoice-1.pdf"
>   Assets:MyClient1234.00 USD
>   Income:ClientServices -1234.00 USD
> ```
>
> This setup triggers an error in the `Errors` tab of fava:
>
> ```
> Document not found: 'files/Assets/MyClient/2022-01-01-invoice-1.pdf'
> ```
>
> If I update the `document:` path to be relative (`../files/...`) the error 
> goes away, but then clicking the file's link in fava's UX takes me to an 
> error page saying:
>
> ```
> Statement not found.
> ```
>
> If I move the entire transaction to the base `ledger.beancount` everything 
> works just fine (but I'd like to be able to organize my transactions)
>
> Anybody have ideas what might be going on and how I might be able to 
> resolve it?
>
> Best,
>   Dan
> --
> Daniel Schultz (he / him)
> P: (215) 400-1233
> T: @slifty
> W: http://www.slifty.com
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Beancount" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beancount+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beancount/602b9216-5a1d-4965-a99e-ac80a67f797en%40googlegroups.com.

How to effeciently use Documents in beancount.

['Vinit Khandagle' via Beancount]

Hello Everyone, 

So I am trying to understand how to use document directive efficiently. 
They way I do is:
have an "option" directive pointing to the directories lets say 
"beancoount/Expenses". But the declaration of the "option" directive alone 
does not populate the document section in fava. 

Then for each transaction I have to point it explicitly to the scanned copy 
in the sub directories in the expense folder for the document to show up in 
the documents section on Fava. This seems quite tedious to do for every 
transcation esp if have lots of accounts in Expenses with 4-5 levels deep. 

What is the efficient way of using documents so that you don't spend too 
much time recording the entries and you still see the documents in the 
documents section in fava. 

-- 
You received this message because you are subscribed to the Google Groups 
"Beancount" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beancount+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beancount/82da3624-626b-42a0-8e8f-7971c3f1942bn%40googlegroups.com.

Re: How to effeciently use Documents in beancount.

['Vinit Khandagle' via Beancount]

Yes, that exactly what I do, I have subdirectories with files in it with 
the date as the prefix.  Yet, Unless I give the explicit path to the 
document I don't see the files in the document setion. 

On Saturday, December 4, 2021 at 9:08:27 PM UTC+5:30 bl...@furius.ca wrote:

> You may have to prefix your documents with a date in order for them to be 
> found.
>
> OptGroup("""   
>  
>   A list of directory roots, relative to the CWD, which should be 
> searched  
>   for document files. For the document files to be automatically found 
> they 
>   must have the following filename format: -MM-DD.(.*) 
>  
> """, [Opt("documents", [], "/path/to/your/documents/archive")]),
>
> The source code is located here:
>
> https://github.com/beancount/beancount/blob/master/beancount/ops/documents.py#L78
>
>
>
>
>
> On Sat, Dec 4, 2021 at 4:48 AM 'Vinit Khandagle' via Beancount <
> bean...@googlegroups.com> wrote:
>
>> Hello Everyone, 
>>
>> So I am trying to understand how to use document directive efficiently. 
>> They way I do is:
>> have an "option" directive pointing to the directories lets say 
>> "beancoount/Expenses". But the declaration of the "option" directive alone 
>> does not populate the document section in fava. 
>>
>> Then for each transaction I have to point it explicitly to the scanned 
>> copy in the sub directories in the expense folder for the document to show 
>> up in the documents section on Fava. This seems quite tedious to do for 
>> every transcation esp if have lots of accounts in Expenses with 4-5 levels 
>> deep. 
>>
>> What is the efficient way of using documents so that you don't spend too 
>> much time recording the entries and you still see the documents in the 
>> documents section in fava. 
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Beancount" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to beancount+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/beancount/82da3624-626b-42a0-8e8f-7971c3f1942bn%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/beancount/82da3624-626b-42a0-8e8f-7971c3f1942bn%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Beancount" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beancount+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beancount/10ed6949-4521-433c-ae3c-85a732b9bcc3n%40googlegroups.com.