[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#10559: perl-indent-command vs. perldoc parts
From: |
Mauro Aranda |
Subject: |
bug#10559: perl-indent-command vs. perldoc parts |
Date: |
Mon, 19 Sep 2022 17:36:16 -0300 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.11.0 |
jidanni@jidanni.org writes:
> If one marks the following region, and then runs
> TAB (translated from <tab>) runs the command perl-indent-command,
>
> =head2 _encode_word()
>
> Usage : my $encoded_quintet_word =
_encode_word($signed_floating_point_coordinate);
> Function : turn a signed float (either a full coordinate
> or a delta) for the _encode() function
> Returns : a string containing one encoded coordinate that
> will be added to a polyline string
> Args : one data word made of ASCII characters carrying
> a five-bit number per character from an encoded
> Google polyline string
>
> =cut
>
> one will get:
>
> =head2 _encode_word()
>
> Usage : my $encoded_quintet_word =
_encode_word($signed_floating_point_coordinate);
> Function : turn a signed float (either a full coordinate
> or a delta) for the _encode() function
> Returns : a string containing one encoded coordinate that
> will be added to a polyline string
> Args : one data word made of ASCII characters carrying
> a five-bit number per character from an encoded
> Google polyline string
>
> =cut
>
> One also notes trailing whitespace is retained.
I'm not able to reproduce this bug. Furthermore, perl-indent-command was
marked obsolete in Emacs 24.4, so I'd say there's nothing to do
with this bug report.
- bug#10559: perl-indent-command vs. perldoc parts,
Mauro Aranda <=