X-Git-Url: https://git.donarmstrong.com/?a=blobdiff_plain;f=TODO;h=b8359cfe8045b0c3a119197bb78e7ad500adb55c;hb=cd1d5200f68edb61242d6115544b9afca06361c9;hp=8eaabd68ac248c0196261ad30995240f6ae16a8a;hpb=7272c75ca797879bc1a6bb26ad0f82b89255104a;p=perltidy.git

diff --git a/TODO b/TODO
index 8eaabd6..b8359cf 100644
--- a/TODO
+++ b/TODO
@@ -1,50 +1,6 @@
 Perltidy TODO List
-    This is a partial "wish-list" of features to add and things to do. All
-    of these are of interest, but there is no particular schedule for
-    implementing them.
 
-  Improved Vertical Alignment
-    There are many opportunities for improving vertical alignment.
+    For a list of bugs and feature requests see:
 
-  improved ?: formatting
-    An indentation level should be associated with ?: statements. This would
-    make nested ?: statements more readable.
-
-  improved internal if/unless formatting
-    Consider giving internal if/unless statements an additional level of
-    indentation. This would avoid running out of indentation levels.
-    Suggested by Jeff Armstorng. For example, we would like the 'ands' in
-    the following statement to be indented more than the if:
-
-        return $ship->chargeWeapons("phaser-canon")
-          if $encounter->description eq 'klingon'
-          and $ship->firepower >= $encounter->firepower
-          and $location->status ne 'neutral';
-
-  enable -ole under Windows
-    This only works under unix (or cygwin) at present. It doesn't work for
-    Windows versions, such as Active State, because they change line endings
-    that they don't like.
-
-  Documentation
-    A FAQ is needed to explain some of the more subtle formatting issues,
-    and to give examples of different styles.
-
-    The -formatter callback object documentation is incomplete.
-
-  HTML writer
-    The HTML writer does not colorize interpolated identifiers in here
-    documents or quoted strings. The tokenizer outputs interpolation
-    information for here docs; it still needs to be updated to do this for
-    multi-line quotes. Then code needs to be written to scan for and markup
-    identifiers.
-
-  Automatic style detection
-    It would be nice to write a program to read a sample of perl code and
-    write an approximate .perltidyrc file for that style.
-
-Things which have been suggested but will not be done
-  Recursive file processing
-    A -r flag might be nice, but this is probably best handled by an
-    exterior shell script.
+    https://rt.cpan.org/Public/Dist/Display.html?Name=Perl-Tidy