gnu-arch-users
[Top][All Lists]
Advanced

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

Re: [Gnu-arch-users] Help please (filetypes)


From: Miles Bader
Subject: Re: [Gnu-arch-users] Help please (filetypes)
Date: Fri, 2 Jan 2004 17:38:33 -0500
User-agent: Mutt/1.3.28i

On Fri, Jan 02, 2004 at 11:30:53PM +0100, Johannes Berg wrote:
> Can we propose more?
> 
>   tagline_type[10, "ext", "pas"]              = "pascal"       #:  (* 
> arch-tag: ...\n  ... *)
>   tagline_type[10, "ext", "dpr"]              = "pascal"
>   tagline_type[10, "ext", "pp"]               = "pascal"

Sure, I'll add that to my sources (thanks!).  Note that with tla-tools'
auto-tag-generation, the user can add his own mappings via a
{arch}/=tagline-rules file; here's the one for tla-tools itself, which adds a
.shpp extension:

   # Tagline rules file
   #
   # The syntax is:
   #
   #       KIND[.LEVEL]  REGEXP  TYPE
   #  or:  tagline       TYPE    FORMAT
   #  or:  end-marker    TYPE    REGEXP
   #  or:  # COMMENT
   #
   # where KIND is "ext" to match file extensions, "name" to match whole
   # filenames, and "dir" to match directories.  LEVEL is a priority, where
   # lower levels are search first; default rules are level 10, and user rules
   # with no explicit priority are level 5.
   #
   # REGEXP is an egrep-style (`extended') regular expression used for
   # matching (within the context of KIND), and a positive match means a
   # tagline of type TYPE is used.
   #
   # FORMAT should contain the actual tagline to add for TYPE, with a
   # single %s where the actual tag value should be substituted (any other
   # occurances of % should be escaped by doubling them percent, e.g %%).
   #
   # Both REGEXP and FORMAT may contain the following special backslash
   # escape sequences: \n \t \s \\  (\s means a space)
   # other occurrences of backslash are left unchanged.
   #

   ext  shpp    sh

-Miles
-- 
97% of everything is grunge




reply via email to

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