GNU bug report logs - #10559
perl-indent-command vs. perldoc parts

Previous Next

Full log

View this message in rfc822 format

From: jidanni <at> jidanni.org
To: 10559 <at> debbugs.gnu.org
Subject: bug#10559: perl-indent-command vs. perldoc parts
Date: Thu, 19 Jan 2012 18:57:47 +0800

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.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.