From: Steve Hancock <perltidy@users.sourceforge.net>
Date: Fri, 2 Oct 2020 13:47:55 +0000 (-0700)
Subject: update logs
X-Git-Tag: 20201001.01~32
X-Git-Url: https://git.donarmstrong.com/?a=commitdiff_plain;h=ede3950ba6c5507c3dd1ff50c71b960aa90abcc6;p=perltidy.git

update logs
---

diff --git a/CHANGES.md b/CHANGES.md
index 29a3b6a7..3cccd1f6 100644
--- a/CHANGES.md
+++ b/CHANGES.md
@@ -1,5 +1,8 @@
 # Perltidy Change Log
 
+    - Fix issue git #40: when using -bli a closing brace followed by a semicolon was 
+      not being indented.
+
 ## 2020 10 01
 
     - Robustness of perltidy has been significantly improved.  Updating is recommended. Continual 
diff --git a/local-docs/BugLog.pod b/local-docs/BugLog.pod
index a22ff1e1..55dfe642 100644
--- a/local-docs/BugLog.pod
+++ b/local-docs/BugLog.pod
@@ -1,3 +1,38 @@
+=head1 Issues fixed after release 20201001
+
+=item B<terminal braces not indenting correctly with -bli formatting, issue git #40>
+
+This problem is illustrated with the following snippet when run with -bli -blil='*'
+ 
+    #-bli -bli list='*'
+    try
+      {
+        die;
+      }
+    catch
+      {
+        die;
+      };    # <-- this was not indenting
+
+This was due to conflicting rules and was fixed 1 Oct 2020 in commit
+'fix issue git #40, incorrect closing brace indentation with -bli', a5aefe9.
+
+At the same time, it was noted that block types sort/map/grep and eval were not
+following -bli formatting when -blil='*' and this was fixed.  For example, with
+corrected formatting, we would have
+
+  # perltidy -bli -blil='*'
+    eval
+      {
+        my $app = App::perlbrew->new( "install-patchperl", "-q" );
+        $app->run();
+      }
+      or do
+      {
+        $error          = $@;
+        $produced_error = 1;
+      };
+
 =head1 Issues fixed after release 20200907
 
 This is a detailed log of changes since the release 20200907. All bugs were