From: Mauro Aranda <maurooaranda@gmail.com>
To: 10559@debbugs.gnu.org
Cc: jidanni@jidanni.org
Subject: bug#10559: perl-indent-command vs. perldoc parts
Date: Mon, 19 Sep 2022 17:36:16 -0300 [thread overview]
Message-ID: <33f78353-b574-662d-d37c-2310e23426d4@gmail.com> (raw)
In-Reply-To: <87hazsnems.fsf@jidanni.org>
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.
next prev parent reply other threads:[~2022-09-19 20:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-19 10:57 bug#10559: perl-indent-command vs. perldoc parts jidanni
2022-09-19 20:36 ` Mauro Aranda [this message]
2022-09-20 10:13 ` Lars Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=33f78353-b574-662d-d37c-2310e23426d4@gmail.com \
--to=maurooaranda@gmail.com \
--cc=10559@debbugs.gnu.org \
--cc=jidanni@jidanni.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.