# HG changeset patch
# User Dmitriy Morozov <dmitriy@mrzv.org>
# Date 1303167148 25200
# Node ID 0bfd48368c17e2a8dcabe02eaaa5f10c21668760
# Parent  30343993578e093b6def212aaee8f98b16af0240
Added #af5 (format string in the config file)

diff -r 30343993578e -r 0bfd48368c17 .issues/af5b63a7d86cf9e3/new/1303167129.M622016P25911Q1.vine
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/.issues/af5b63a7d86cf9e3/new/1303167129.M622016P25911Q1.vine	Mon Apr 18 15:52:28 2011 -0700
@@ -0,0 +1,24 @@
+From: Dmitriy Morozov <dmitriy@mrzv.org>
+Date: Mon, 18 Apr 2011 15:41:53 -0700
+State: new
+Subject: Configurable format
+Message-Id: <af5b63a7d86cf9e3-0-artemis@vine>
+
+The user should be able to define the format for the issue summary line (in
+ilist) in the config file. So, for instance, one could specify:
+
+  [artemis]
+  format = %(id)s (%(len)3d) [%(state)s]: %(Subject)s
+
+to have the default (current) format. One should also be able to specify
+additional conditions with the flags in the name of the option. For example:
+
+  format:state=in-progress    = %(id)s (%(len)3d) [%(state)s; priority=%(priority)s]: %(Subject)s
+  format:state=resolved       = %(id)s (%(len)3d) [%(state)s=%(resolution)s]: %(Subject)s
+  format:state=resolved&resolution=fixed  = %(id)s (%(len)3d) [fixed]: %(Subject)s    # also change color
+  format:state=fixed          = ...  # change color
+
+The format string would be passed the headers from the root message, so that
+the user could use whatever properties she wanted.
+
+This approach would also replace the current way we define colors.