Re: [coldsync-hackers] Variables in Coldsync.conf

[Andrew Arensburger <arensb+CShackers@ooblick.com>]

On Thu, Feb 07, 2002 at 10:53:54AM -0500, Brian Johnson wrote:
> >	Tilde-expansion ("~/foo") isn't implemented. However, you
> should be able to use "${HOME}/foo". How exactly is this not working
> for you?
> 
> Are those round brackets or parenthesis around HOME?  That may be my
> problem.

	Either one. It shouldn't matter. Heck, the code even checks
for
	${HOME)
and
	$(HOME}

> So if I set up a user in /etc/palms, the pda block in /etc/coldsync can
> include
> directory: "${HOME}/.palm";

	That should work, yes.

> I also have
> options {
>         CONDUITDIR:
> "$(CONDUITDIR):$(HOME)/.palm/conduits:/usr/share/coldsync-2.2.5/conduits";
> }
> 
> but when I use
> path: ./send-mail;
> or
> path: send-mail;
> in a conduit block, the log file shows that coldsync can't find it - but it
> can find it if I put in the full path

	I think you want to change the first "CONDUITDIR" above to
"CONDUIT_PATH". $(CONDUITDIR) is a single directory; $(CONDUIT_PATH)
is a set of directories.
	So in the options{} block you've given, you're telling
ColdSync to look in the directory
	/foo:/homes/bjohnson/.palm/conduits:/usr/share/coldsync-2.2.5/conduits
and in all likelihood, this directory doesn't exist.
	See the bit about $(CONDUITDIR) and $(CONDUIT_PATH) in the man
page.

-- 
Andrew Arensburger                      This message *does* represent the
arensb@ooblick.com                      views of ooblick.com
A mushroom cloud on the horizon, 24 empty missile tubes--now it's Miller time.

-- 
This message was sent through the coldsync-hackers mailing list.  To remove
yourself from this mailing list, send a message to majordomo@thedotin.net
with the words "unsubscribe coldsync-hackers" in the message body.  For more
information on Coldsync, send mail to coldsync-hackers-owner@thedotin.net.