David--
I am on OS X Mountain Lion, as originally noted.
It is implied, but I have been using colored account tabs for several years
myself; apparently, this feature has disappeared in the development release of
2.5.2.
Since this development release has only been out for a couple of days, I
On 5/29/2013 6:48 PM, David T. wrote:
> John--
>
> I pulled down 2.5.2 last night, and I see that the load time has improved.
> But it still takes over 30 seconds to load my checking register. That's too
> long.
>
> The colored tabs are still not displaying. (By this, I mean when one sets an
> a
On May 29, 2013, at 7:16 AM, Geert Janssens wrote:
> On Wednesday 29 May 2013 06:46:06 John Ralls wrote:
> > On Tue, 28 May 2013 16:02:14 -0400 Christian Stimming
> > wrote
> > > Author: cstim
> > > Date: 2013-05-28 16:02:12 -0400 (Tue, 28 May 2013)
> > > New Revision: 23018
> > > Trac: http://
John--
I pulled down 2.5.2 last night, and I see that the load time has improved. But
it still takes over 30 seconds to load my checking register. That's too long.
The colored tabs are still not displaying. (By this, I mean when one sets an
account color on the Edit Account page).
My comments
On 5/29/2013 3:26 PM, Christian Stimming wrote:
> Am Dienstag, 28. Mai 2013, 14:53:06 schrieb David T.:
>> Having loaded the new register, I see what folks have been saying about the
>> screen flag for future transactions. Personally I think it does not work.
>> Users looking at the register see it
On 05/29/2013 10:14 AM, Derek Atkins wrote:
> "Allen S. Rout" writes:
>> gnucash --run-customer-report="report-name"
>> --output-filename="/path/file.html" --customer-id="03"
>
> This is an extremely report-specific command-line.
You are correct; that was excruciatingly deliberate. It m
Am Dienstag, 28. Mai 2013, 14:53:06 schrieb David T.:
> Having loaded the new register, I see what folks have been saying about the
> screen flag for future transactions. Personally I think it does not work.
> Users looking at the register see it naturally as a flow of time from the
> top of the sc
I would be happy with the reports, including report options, being
available via Python bindings, or even Guile bindings. It may be easier to
make that interface generic than a command-line based one. In which case,
the particular command-line reporting Mr. Rout is looking for could be
easily wri
Ok, this mail and an equivalent mail regarding the master branch are the
result of my attempts to undo my first reset-beta-by-merging-with-master
experiment.
I have hard-reset the master and beta branch to the commits right before my
attempt. This gave me all kinds of small issues. Git (right-f
Hmm, I never really looked at those details. Isn't it odd to call a mailing-
list -patches and then don't send patches to it, but only change summaries ?
A historical issue I suppose... Would the move to git be a good moment to fix
this mistake ?
Or do you prefer to keep things as they currently
On Wednesday 29 May 2013 10:20:15 Derek Atkins wrote:
> Geert Janssens writes:
> > For those curious to what happened here:
> > This (and the next) push are part of an experiment to reset the beta
> > branch to the current master/trunk branch using git features.
> >
> > The following commands wer
I have found a way to do what I wanted. Most of my steps were ok, but I should
not have used the master branch directly. A temporary branch to the rescue !
Here are the steps I used for the second attempt:
1. git checkout master
2. git checkout -b tmp
3. git merge -s ours beta -m "Reset beta back
Geert,
It looks like we have the mail to -changes and -patches backwards. The
summary is going to -changes and the diffs are going to -patches. This
is the reverse of what we were doing with subversion.
-derek
Geert Janssens writes:
> The beta branch has been updated
>via https://gi
Geert Janssens writes:
> For those curious to what happened here:
> This (and the next) push are part of an experiment to reset the beta branch
> to the current
> master/trunk branch using git features.
>
> The following commands were executed:
> 1. git checkout master
> 2. git merge -s ours be
On Wednesday 29 May 2013 06:46:06 John Ralls wrote:
> On Tue, 28 May 2013 16:02:14 -0400 Christian Stimming
> wrote
> > Author: cstim
> > Date: 2013-05-28 16:02:12 -0400 (Tue, 28 May 2013)
> > New Revision: 23018
> > Trac: http://svn.gnucash.org/trac/changeset/23018
> >
> > Added:
> > gnucash/t
Geert Janssens writes:
> From what I can see the mythtv guys are using the same mail script :)
>
> Except that they use the subject line unaltered, where I made some changes to
> it based on faulty assumptions. The last part of their subject line is the
> untruncated version of our current "svn_l
Allen,
"Allen S. Rout" writes:
[snip]
> Simplest: "Fire a report from the command line". Absolute minimum data
> from the command line, no need to be able to tweak all the details.
> Customer ID, target filename and that's it
>
> gnucash --run-customer-report="report-name"
> --output-filename=
On Tue, 28 May 2013 16:02:14 -0400 Christian Stimming
wrote
> Author: cstim
> Date: 2013-05-28 16:02:12 -0400 (Tue, 28 May 2013)
> New Revision: 23018
> Trac: http://svn.gnucash.org/trac/changeset/23018
>
> Added:
> gnucash/tags/2.5.2/
> Log:
> Tag 2.5.2, now correctly from trunk r23012
How t
On 5/29/2013 3:10 AM, Geert Janssens wrote:
> On Tuesday 28 May 2013 14:59:04 John Ralls wrote:
>> On May 28, 2013, at 2:53 PM, David T. wrote:
>>> I was trying out 2.5.1 on my Mac (Mountain Lion) and was prepared to
>>> report that it was crashing when I tried closing and then re-opening my
>>> m
For those curious to what happened here:
This (and the next) push are part of an experiment to reset the beta branch to
the current
master/trunk branch using git features.
The following commands were executed:
1. git checkout master
2. git merge -s ours beta
(pushed the master branch to gitolite
Il 29/05/2013 10.27, Christian Stimming ha scritto:
Am Mittwoch, 29. Mai 2013, 10:20:40 schrieb Cristian Marchi:
Does it make sense to post this announcement on facebook and google+? If
I'm not mistaken that was already discussed but I can't find and
remember the conclusion.
Yes it does make s
Am Mittwoch, 29. Mai 2013, 10:20:40 schrieb Cristian Marchi:
> Does it make sense to post this announcement on facebook and google+? If
> I'm not mistaken that was already discussed but I can't find and
> remember the conclusion.
Yes it does make sense. However, I'd say you should wait until the w
Does it make sense to post this announcement on facebook and google+? If
I'm not mistaken that was already discussed but I can't find and
remember the conclusion.
Regards
Cristian
Il 29/05/2013 9.53, Christian Stimming ha scritto:
Dear Developers,
after some internal discussion we've decided
On Tuesday 28 May 2013 14:59:04 John Ralls wrote:
> On May 28, 2013, at 2:53 PM, David T. wrote:
> > I was trying out 2.5.1 on my Mac (Mountain Lion) and was prepared to
> > report that it was crashing when I tried closing and then re-opening my
> > main checking account register. Every time I did
Dear Developers,
after some internal discussion we've decided to use part of our available tip
jar funds for running the
GnuCash Bounty Program "GCBoP"
The program is described on the wiki page
http://wiki.gnucash.org/wiki/Bounty_Program , copied in part below. Feel free
to send me any comm
Am Montag, 27. Mai 2013, 08:23:02 schrieb Yawar Amin:
> Hi,
>
> On 2013-05-11, at 5:28, "Christian Stimming (mobil)"
wrote:
> > Dear Allen, I'm sorry to hear the program does not start. The error
> > during make check is caused because you don't have the French locale
> > installed. We discussed
26 matches
Mail list logo