I would love to do more #Perl and #RakuLang coding. Have done some Perl over the last couple of weeks again. But what brings me back to #Ruby most of the time is the better #LSP support for my Editor. E.g. renaming variables, code-actions, etc. That's just a superior experience :-( #PerlNavigator and #perltidy are OK, but not perfect.
Will soon publish a new blog post about "Perl new features" and how I used them.
@deflarerOfClouds #GitHub has hosted #PerlTidy development for a long time. Please continue to file bug reports there: https://GitHub.com/perltidy/perltidy/issues
You might even consider making a reasonable case to move the project’s remaining assets off #SourceForge. Impotently whinging about it here doesn’t change anything.
@ovid @ChristosArgyrop @Perl The #Perltidy Home Page is still on #SourceForge: https://perltidy.sourceforge.net
@eliasp @ColinTheMathmo BTW #Perl has two well-known tools to encourage and enforce #programming style and best practices, respectively:
• #PerlTidy: https://perltidy.github.io/perltidy
• #PerlCritic: http://perlcritic.com
Your project or team can use their reasonable defaults or further configure them to reflect and maintain the consistent application of your preferences. They also integrate with editors/IDEs, source control management, and author #testing.
@ovid Either of the perltidy options:
-nwrs='A'
or
--no-want-right-space='A'
ought to do it. “A” is the token #perltidy uses for #Perl attribute separators according to the output of `perltidy --dump-token-types`.
Feel free to put either in your .perltidyrc file. I prefer to use long option names as they’re more self-documenting or at least easier to search for.