Re: Beancount Migration to Github

[Stefano Zacchiroli]

On Fri, May 22, 2020 at 05:56:33PM -0400, Martin Blais wrote:
> The Beancount repository and issue tracker has been migrated to Github, at
> this location:
[...]
> Special thanks to Martin Michlmayr, Kirill Goncharov and Dominik Aumayr for
> figuring out most of the details to make this happen smoothly. This
> wouldn't have happened so quickly without your input.

Great work. Thanks a lot to bot you personally and all the people who
have helped to make this happen.

Cheers
-- 
Stefano Zacchiroli . z...@upsilon.cc . upsilon.cc/zack . . o . . . o . o
Computer Science Professor . CTO Software Heritage . . . . . o . . . o o
Former Debian Project Leader & OSI Board Director  . . . o o o . . . o .
« the first rule of tautology club is the first rule of tautology club »

-- 
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/20200523081201.cgdn2se35fbmhuen%40upsilon.cc.

Re: Envelope Plugin for Fava

[Red S]

In case this helps debug:

If you see this in the Fava error page: "Importing module "mymodule" failed."

That usually means the module was not able to be loaded. Try running python3 
interactively and typing:

import mymodule

That should succeed, or tell you what the failure was.

-- 
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/b73aba31-af7d-48ef-a07e-9da1a68dddcb%40googlegroups.com.

Re: Envelope Plugin for Fava

[Red S]

FWIW, what I've learned working with Fava extensions:
1. Understand failure to load the module by importing the module in an 
interactive python shell

2. If the module loads, error reporting on the console is easy and works well 
(print statements, logging)

-- 
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/84228eeb-50da-4ff6-810a-cb4e6376edef%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
>>  
>> 
>> .
>>
>

-- 
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: 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: 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/
>>  
>> 
>> 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: Beancount Migration to Github

[Stefano Zacchiroli]

Hi again Martin,

On Fri, May 22, 2020 at 05:56:33PM -0400, Martin Blais wrote:
> The Beancount repository and issue tracker has been migrated to Github, at
> this location:

as far as I can tell from:

  https://travis-ci.org/github/beancount/beancount/pull_requests

CI builds are not enabled for pull requests. Can you enable them?

It's gonna help both you and PR submitters in shortening feedback loops,
I think. To enable them all that should be needed is going here:

  https://travis-ci.org/github/beancount/beancount/settings

and flipping the switch "Build pushed pull requests" (there's also
"Build pushed branches", but that concerns only the people with direct
push access).

Thanks for considering,
Cheers
-- 
Stefano Zacchiroli . z...@upsilon.cc . upsilon.cc/zack . . o . . . o . o
Computer Science Professor . CTO Software Heritage . . . . . o . . . o o
Former Debian Project Leader & OSI Board Director  . . . o o o . . . o .
« the first rule of tautology club is the first rule of tautology club »

-- 
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/20200523155310.hxufpc4fg5praz5v%40upsilon.cc.

Re: Beancount Migration to Github

[Martin Blais]

On Sat, May 23, 2020 at 11:53 AM Stefano Zacchiroli  wrote:

> Hi again Martin,
>
> On Fri, May 22, 2020 at 05:56:33PM -0400, Martin Blais wrote:
> > The Beancount repository and issue tracker has been migrated to Github,
> at
> > this location:
>
> as far as I can tell from:
>
>   https://travis-ci.org/github/beancount/beancount/pull_requests
>
> CI builds are not enabled for pull requests. Can you enable them?
>

I agree, but "Build pushed pull requests" is already enabled.
I changed the settings this morning so it's possible previous PRs haven't
been built.
I disabled "build pushed branches" because most branches aren't clean in
that way at the moment.



> It's gonna help both you and PR submitters in shortening feedback loops,
> I think. To enable them all that should be needed is going here:
>
>   https://travis-ci.org/github/beancount/beancount/settings
>
> and flipping the switch "Build pushed pull requests" (there's also
> "Build pushed branches", but that concerns only the people with direct
> push access).
>
> Thanks for considering,
> Cheers
> --
> Stefano Zacchiroli . z...@upsilon.cc . upsilon.cc/zack . . o . . . o . o
> Computer Science Professor . CTO Software Heritage . . . . . o . . . o o
> Former Debian Project Leader & OSI Board Director  . . . o o o . . . o .
> « the first rule of tautology club is the first rule of tautology club »
>
> --
> 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/20200523155310.hxufpc4fg5praz5v%40upsilon.cc
> .
>

-- 
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/CAK21%2BhOOS6k%2BTc7W-ZyLNuFdhPV7D-8anEvUXEScYedQ6HYJ-w%40mail.gmail.com.