[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: parsing loginfo

From: Rob Helmer
Subject: Re: parsing loginfo
Date: Fri, 15 Feb 2002 14:15:50 -0800
User-agent: Mutt/1.2.5i

On Fri, Feb 15, 2002 at 03:58:03PM -0500, Larry Jones wrote:
> Rob Helmer writes:
> > 
> > All the info I want is actually in %s. Anyone have examples where
> > they have successfully parsed this data if it contains spaces
> > in the subdirs leading to the filename and/or the filename itself?
> Just one more reason why rational people don't use filenames with spaces


> in them.  ;-)  If you haven't also used commas in your filenames, you
> can use %{sV} or %{sv} and look for the comma between the filename and
> the version number to determine the end of the filename.

Thanks for the info, I'm already doing that part.

I've noticed the main problem though is that I can't tell the 
directory apart from the filename, see this example of %s output
where the dir is named "blah test" and the file is named "space file.txt" :

sandbox/blah test space file.txt

Nasty. I don't really see a way around that.

What I'd like to do is this : when a file is committed, I want
to get the full path w/ filename, current revision, previous revision
and run a diff to put up on a webpage.

This works great except for a space issue like the one above.

I don't think I can get people to stop using spaces in filenames
for this particular repository, but I guess I could workaround by
not allowing spaces in dir names and in my loginfo parsing script
split on the first space I see. Ack.

Rob Helmer

reply via email to

[Prev in Thread] Current Thread [Next in Thread]