Clarified distinction between attribute- and sequence renaming tokens a bit more using common token name as an example.

Fork: 0

tundra / tren

Browse code Clarified distinction between attribute- and sequence renaming tokens a bit more using common token name as an example. master
1 parent f26ff2b commit cedcbcd692d819002f38eda46f72c48f60fd7e68 tundra authored on 29 Mar 2010

Patch

Unified Split

Showing 1 changed file

                Ignore Space
               Show notes
              View
            
          
          24 ■■■■■
          tren.rst
 In short, sequences are just strings of numbers used to put
things in some order.
 
You can always tell the difference between an attribute-
and sequence renaming token, because sequence renaming tokens
always start with either a ``+`` or ``-`` sign (to indicate
ascending or descending counting respectively).
You can always tell the difference between an attribute- and sequence
renaming token, because sequence renaming tokens always start with
either a ``+`` or ``-`` sign (to indicate ascending or descending
counting respectively).  This distinction is important because some
attribute- and sequence renaming tokens share the same name.  For
instance, ``/FNAME/`` is an attribute token representing the original
name of the file before it was renamed.  However, ``/+FNAME::003/`` is
a sequence renaming token that returns the position of the file name
in alphabetic order starting counting from ``003``.  Although they are
both based on the file name (hence the common renaming token symbol),
they do very different things.
 
 
How **tren** Uses File Metadata
================================
-----------------------------
 
::
 
  $Id: tren.rst,v 1.163 2010/03/29 21:41:13 tundra Exp $
  $Id: tren.rst,v 1.164 2010/03/30 00:42:10 tundra Exp $
 
You can find the latest version of this program at:
 
  http://www.tundraware.com/Software/tren
 In short, sequences are just strings of numbers used to put
 things in some order.
+You can always tell the difference between an attribute-
+and sequence renaming token, because sequence renaming tokens
+always start with either a ``+`` or ``-`` sign (to indicate
+ascending or descending counting respectively).
+You can always tell the difference between an attribute- and sequence
+renaming token, because sequence renaming tokens always start with
+either a ``+`` or ``-`` sign (to indicate ascending or descending
+counting respectively).  This distinction is important because some
+attribute- and sequence renaming tokens share the same name.  For
+instance, ``/FNAME/`` is an attribute token representing the original
+name of the file before it was renamed.  However, ``/+FNAME::003/`` is
+a sequence renaming token that returns the position of the file name
+in alphabetic order starting counting from ``003``.  Although they are
+both based on the file name (hence the common renaming token symbol),
+they do very different things.
 How **tren** Uses File Metadata
 ================================
 -----------------------------
 ::
+  $Id: tren.rst,v 1.163 2010/03/29 21:41:13 tundra Exp $
+  $Id: tren.rst,v 1.164 2010/03/30 00:42:10 tundra Exp $
 You can find the latest version of this program at:
   http://www.tundraware.com/Software/tren

Show line notes below