Planning for ledger 3.2

2019-12-10 Thread Martin Michlmayr
I think it's time to start planning for a ledger 3.2 release. Dimitri John Ledkov has recently completed the port of the Python API to Python 3, which is something Alexis started a long time ago. Python 2 support is ending in 2020, and lack of Python 3 support is already a problem for some distros

Re: Planning for ledger 3.2

2019-12-10 Thread John Wiegley
> "MM" == Martin Michlmayr writes: MM> Anyway, I'm hoping everything can help: MM> - point out issues that should be fixed before 3.2. I'm talking MM>about *critical* stuff MM> - help fix as many things as possible MM> - test Python3 support and report issues Thank you, Martin! I wou

Re: Planning for ledger 3.2

2019-12-12 Thread psionl0
I would like to see formatted output (coloured text, paging etc) made on an opt-in basis rather than an opt-out basis. This is supposed to be a text based reporting system and all of the formatting characters play havoc on text based editors. -- --- You received this message because you are

Re: Planning for ledger 3.2

2019-12-12 Thread John Wiegley
> "p" == psionl0 writes: p> This is supposed to be a text based reporting system and all of the p> formatting characters play havoc on text based editors. In ~/.ledgerrc you can put: --no-color John -- --- You received this message because you are subscribed to the Google Groups "L

Re: Planning for ledger 3.2

2019-12-13 Thread psionl0
On Friday, December 13, 2019 at 12:23:47 AM UTC+8, John Wiegley wrote: > > In ~/.ledgerrc you can put: > > --no-color > > John > That's my point. In ~/.ledgerrc it should be --color --pager I expected this to be a text based program. After the nasty formatting surprises, I had to res

Re: Planning for ledger 3.2

2019-12-13 Thread Yuri Khan
On Sat, 14 Dec 2019 at 08:33, psionl0 wrote: > I expected this to be a text based program. After the nasty formatting > surprises, I had to research how to strip all of these formatting characters > out of the output stream. Otherwise, it is useless if I want to feed the > output into another

Re: Planning for ledger 3.2

2019-12-15 Thread psionl0
Does it work for all piping commands? I shouldn't have to research how to output unformatted text. Let those who want special formatting include those options in their command line. -- --- You received this message because you are subscribed to the Google Groups "Ledger" group. To unsubscrib

Re: Planning for ledger 3.2

2019-12-15 Thread Michael Cooper
Hey psion, Every well behaving command line app should only use color at interactive colors that can render them. If you are seeing raw formatting codes, I think we can all agree there is a problem somewhere. It would be great if you could give some specific examples of times this goes wrong. In

Re: Planning for ledger 3.2

2020-03-27 Thread Martin Michlmayr
* Martin Michlmayr [2019-12-10 15:21]: > Dimitri John Ledkov has recently completed the port of the Python API > to Python 3, which is something Alexis started a long time ago. > Python 2 support is ending in 2020, and lack of Python 3 support is > already a problem for some distros. > > There ar

Re: Planning for ledger 3.2

2020-04-27 Thread Martin Michlmayr
* Martin Michlmayr [2020-03-27 15:01]: > > Anyway, I'm hoping everything can help: > > - point out issues that should be fixed before 3.2. I'm talking > >about *critical* stuff > > - help fix as many things as possible > > - test Python3 support and report issues > > Unfortunately I didn'

Re: Planning for ledger 3.2

2020-04-27 Thread John Wiegley
> "MM" == Martin Michlmayr writes: MM> Unfortunately still no reponse from anyone. I think it's time to make a MM> ledger 3.2 release in a few days from current Git. Python 2 is officially MM> dead now and the lack of Python 3 support is a major problem for the Linux MM> distros. MM> If ther