Mike or Penny Novack <[EMAIL PROTECTED]> writes:
> account name with an asterisk in it. Can anybody here identify the
> address of the team working on "gnome for Windows" because they should
> be made aware that there is a problem affecting their project.
>
> The implication is that the problem i
Hi,
Am Mittwoch, den 08.08.2007, 12:16 -0400 schrieb Mike or Penny Novack:
[snip]
> The implication is that the problem isn't FIXABLE (can't make GnuCash
> work completely properly for all legal Windows user account names) but
> that doesn't mean it should be "no action". One possibility would b
>>
>>
>[[Maybe a bit off-topic for this mailinglist, but I thought it could give some
>additional background]]
>
>... and some are already. A fine example is The Gimp (http://www.gimp.org),
>an alternative image manipulation program for Photoshop. Whether it truly can
>replace Photoshop is
On Wednesday 8 August 2007 14:55, Dan Widyono wrote:
> > What "leverage"? You imagine that any of these would be there in a
> > Windows user's c:\documents and setting\userID (the Windows XP
> > equivalent of $HOME/ ) for some other purpose than holding GnuCash data?
> > I think I see what the prob
> What "leverage"? You imagine that any of these would be there in a
> Windows user's c:\documents and setting\userID (the Windows XP
> equivalent of $HOME/ ) for some other purpose than holding GnuCash data?
> I think I see what the problem might be and why hard to fix. This .gconf
> stuff isn
>
>Uh, I'm not sure exactly what you mean, but GnuCash does (should) create a
>$HOME/.gnucash/ dir for its own storage, as well as leveraging the
>$HOME/.gconf/ storage we've talked about.
>
>
>
Sorry -- but I don't understand.
Yes, I see that GnuCash has created a directory named .gnucash
(pr
Mike or Penny Novack <[EMAIL PROTECTED]> writes:
> I have asked there whether this problem is "top level directory name" or
> "anywhere in the path" because if the former, there may be a
> (relatively) easy fix. GnuCash is the first "open app for Windows" that
> I have encountered so far that di
Mike or Penny Novack <[EMAIL PROTECTED]> writes:
>>There are two approaches to book closing:
>>
>>
> Maybe stop right there. As soon as there appear to be difficulties with the
> "only" approaches step back one level of the process and maybe more
> alternatives will appear.
I wasn't really sayin
>
> Very interesting observation. Does the directory ".gnucash" get
> created on both account names? If it does, gnucash's handling of
> account names and paths is correctly implemented. In that case we'd
> have to forward the bugreport about the ".gconf" directory to the
> GConf project:
Josh Sled wrote:
>The developer who started that work hasn't had a lot of time for GnuCash in
>the last few years. I really hope he does respond, but I don't feel out of
>order responding on his behalf.
>
>
>There are two approaches to book closing:
>
>
Maybe stop right there. As soon as there
Quoting Mike or Penny Novack <[EMAIL PROTECTED]>:
> I would like to do a little more than simply report any problems I find
> from the point of view of an "end user" because with a little help, I
> could.
Welcome to the developer list. Sounds very good.
> Here's the first one. I am of necessity t
Mike or Penny Novack <[EMAIL PROTECTED]> writes:
> Meanwhile, I understand that "close the books" isn't working. If whoever
> is the developer on that portion wants a hand, please get in touch.
The developer who started that work hasn't had a lot of time for GnuCash in
the last few years. I rea
It was suggested that I join this list in addition to the users list. I
am a retired senior systems analyst with a few decades experience in
software for a "financial". Well call that semi-retired as they
sometimes tempt me back into the "cypher mines" for a little juicy
consulting. At the mome
13 matches
Mail list logo
