Re: rethinking @def*

[Gavin Smith]

On Thu, Aug 11, 2022 at 11:56:23AM +0100, Gavin Smith wrote:
> On Thu, Aug 11, 2022 at 11:14:06AM +0200, Patrice Dumas wrote:
> > Maybe also protect the first leading space in code context?  Would that
> > be too 'invasive'?
> 
> Probably not, as it wouldn't appear everywhere, only where there was
> a leading space.  It is only an extra \ in the output.

I've done this and committed the test result changes.

There were several test result changes which were nothing to do
with this change, so I manually excluded them all from my commit.
I expect these were due to a recent change you made.

iff --git a/tp/t/results/formatting/direntry_dircategory_info_split.pl 
b/tp/t/results/formatting/direntry_dircategory_info_split.pl
index 5ed423abd1..b11c1bd6f4 100644
--- a/tp/t/results/formatting/direntry_dircategory_info_split.pl
+++ b/tp/t/results/formatting/direntry_dircategory_info_split.pl
@@ -409,7 +409,7 @@ $result_trees{'direntry_dircategory_info_split'} = {
                       'parent' => {},
                       'text' => '
 ',
-                      'type' => 'after_menu_description_line'
+                      'type' => 'after_description_line'
                     },
                     {
                       'parent' => {},

> This could be fixed using \@, so

Your original suggestion was enough so this wasn't necessary.