Oops--pushing it off for real this time.

I don't remember if we fixed it or not, but I'm going to push this off until
after 1.5.

Funky. I'm not sure which is "correct". Blosxom (which we pull some
behavioral specification from) doesn't have a file_path variable and I'm
not entirely sure where it came from.

I suspect the documentation is wrong, but I'm not entirely sure. I'll
look into it. Thanks for the heads-up!

----

Date:   2007-04-12 20:17:47 UTC
Sender: willg

Hi,

pyblosxom has a broken behaviour according to the documentation. On 
manual/x315.html#AEN436 the variable name 'file_path' is defined as: 'just the 
filename and extensions of the entry' and as example, you have 'index.txt'. 
That's not true, you get there 'index', just like 'fn' and looking at the code, 
it would get the path also appended.


Either the implementation or the documentation need to be updated. IMHO, being 
able to get the filename with it's right extension is a good thing, being able 
to link to the raw entry is helpful sometimes.

----

SF url: http://sourceforge.net/tracker/?
func=detail&aid=1695838&group_id=67445&atid=517918
Submitted by: Carlos Perelló Marín ( carlosperello ) - 2007-04-06 21:17:53 UTC