I see three possibly easy solutions:
1. An SQL SELECT on the tag and keyword list decides whether to treat a word
that has no slash as keyword/tag (exists), or filename (not exists). If
there is a slash it is always a filename.
2. A possibly faster executing way (without having to run SQL to check
tags), but less user-friendly due to the required extra typing, is to
consider a filename a word that has to either include a slash anywhere
inside it, or be just the single/double dot special notation -- anything
else it's considered a keyword/tag:
. (current directory)
.. (parent directory)
/ (root directory)
trunk (tag)
./trunk (file or subdirectory named 'trunk')
now (keyword)
./now (file or subdirectory named 'now')
3. Use a special prefix (like @) to denote you need to refer to a filename
(example: @filename) instead of keyword/tag. This is possible the easiest
to implement as it requires a simple check of the first character of a word.
But, I'm sure someone will be able to come up with better ones.
-----Original Message-----
From: to...@acm.org
Sent: Sunday, October 19, 2014 1:11 AM
To: Fossil SCM user's discussion
Subject: Re: [fossil-users] New TIMELINE with FILENAME option
(WAS:FINFOsuggestion)
That's because 'trunk' is incorrectly interpreted as filename.
This is related to the same problem I have already reported about filenames
having priority over internal keywords and tags, instead of the other way
around.
I suspect it will be fixed soon.
-----Original Message-----
From: Stefan Bellon
<snip>
Now with the recent trunk build, I get:
$ fossil timeline trunk
+++ no more data (0) +++
$
<snip>
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
