Balsa Problem SOLVED!!! Re: balsa generates a bad .balsarc

["Jesse D . Sightler" <jsight pair com>]

Note that I am running RH 5.2 and had the problem, so it was not a distribution issue.  The problem seems to be with the version of libPropList that is in CVS (and has been in CVS for several weeks now).  Deleting this from my system and using "rpmfind --latest libPropList" to get a stable version completely solved the problem for me.

I hope that helps some of you that are still having difficulties with this.

BTW, I also managed to get IMAP working for the first time ever on this Linux box with Balsa.  It is really quite a slick little app now that it works!  :)

-------------
Jesse D. Sightler
http://www3.pair.com/jsight/

On Thu, 25 Feb 1999 20:38:32 Mohammad A. Haque wrote:
> FYI
> 
> Running RH5.2 with gnome 0.99.8. No problems.
> 
> Mohammad
> 
> PS: anyone know how to make the ummm....the tab that has the names of
> the open mailboxes...appear along the top instead of along the side?
> 
> 
> blackie@sfcc.net wrote:
> > 
> > > 2. Start up balsa again. I see the following message:
> > > bash-2.02$ balsa
> > > /home/wade/.balsarc:line 2: parse error, expecting `error' or `STRING' or `'}'
> > > *** Could not load config file .balsarc!
> > 
> > I've got a Debian Potato system too and I get the same error.  I *didn't*
> > get it two weeks ago.  Balsa has barely changed in those two weeks from
> > looking at the CVS-COMMITS list.   The m4 macro stuff keeps moving around
> > globally so my guess is that it's either that or something in Debian.