NAME
podsel - Select Pod::Elemental nodes using CSel syntax
VERSION
This document describes version 0.008 of podsel (from Perl distribution App-podsel), released on 2020-04-29.
SYNOPSIS
To select the head1 sections:
% podsel foo.pod -t Pod5 -t Nested '.Nested[command=head1]'
To dump Pod document tree (--root
select the root node, --dump
dumps the content):
% podsel foo.pod -t Pod5 -t Nested --root --dump
DESCRIPTION
This utility uses CSel to select against a tree of Pod::Elemental nodes, constructed from a Perl POD document.
About the tree: the root node is Pod::Elemental::Document object. The other nodes are Pod::Elemental::Element::* nodes. This utility allows you to omit the Pod::Elemental::Element::Generic
, Pod::Elemental::Element::Pod5
, Pod::Elemental::Element
or Pod::Elemental::
prefix, so to select a command you can use:
.Element::Generic::Command
or just:
.Command
OPTIONS
*
marks required options.
Main options
- --count
-
Shortcut for --node-action count.
See
--node-action
. - --dump
-
Shortcut for --node-action dump.
See
--node-action
. - --eval=s@
-
--eval E is shortcut for --action eval:E.
See
--node-action
.Can be specified multiple times.
- --expr=s
- --file=s
-
Default value:
"-"
- --node-action=s@
-
Specify action(s) to perform on matching nodes.
Default value:
["print_as_string"]
Each action can be one of the following:
* `count` will print the number of matching nodes.
* `print_method` will call on or more of the node object's methods and print the result. Example:
print_method:as_string
* `dump` will show a indented text representation of the node and its descendants. Each line will print information about a single node: its class, followed by the value of one or more attributes. You can specify which attributes to use in a dot-separated syntax, e.g.:
dump:tag.id.class which will result in a node printed like this: HTML::Element tag=p id=undef class=undef
By default, if no attributes are specified, `id` is used. If the node class does not support the attribute, or if the value of the attribute is undef, then `undef` is shown.
* `eval` will execute Perl code for each matching node. The Perl code will be called with arguments: `($node)`. For convenience, `$_` is also locally set to the matching node. Example in <prog:htmlsel> you can add this action:
eval:'print $_->tag' which will print the tag name for each matching <pm:HTML::Element> node.
Can be specified multiple times.
- --node-actions-json=s
-
Specify action(s) to perform on matching nodes (JSON-encoded).
See
--node-action
. - --node-actions-on-descendants=s
-
Specify how descendants should be actioned upon.
Default value:
""
Valid values:
["","descendants_depth_first"]
This option sets how node action is performed (See `node_actions` option).
When set to '' (the default), then only matching nodes are actioned upon.
When set to 'descendants_depth_first', then after each matching node is actioned upon by an action, the descendants of the matching node are also actioned, in depth-first order. This option is sometimes necessary e.g. when your node's `as_string()` method shows a node's string representation that does not include its descendants.
-
Shortcut for --node-action print_as_string.
See
--node-action
. - --print-method=s@
-
--print-method M is shortcut for --node-action print_method:M.
See
--node-action
.Can be specified multiple times.
- --root
-
Shortcut for --select-action=root.
See
--select-action
. - --select-action=s
-
Specify how we should select nodes.
Default value:
"csel"
Valid values:
["csel","root"]
The default is `csel`, which will select nodes from the tree using the CSel expression. Note that the root node itself is not included. For more details on CSel expression, refer to <pm:Data::CSel>.
`root` will return a single node which is the root node.
- --transform=s@, -t
-
Apply one or more Pod::Elemental::Transform's.
**TRANSFORMS**
First of all, by default, the "stock" Pod::Elemental parser will be generic and often not very helpful in parsing your typical POD (Perl 5 variant) documents. You often want to add:
-t Pod5 -t Nester
or -5 for short, which is equivalent to the above. Except in some simple cases. See examples below.
The following are available transforms:
* Pod5
Equivalent to this:
Pod::Elemental::Transformer::Pod5->new->transform_node($tree);
* Nester
Equivalent to this:
my $nester; $nester = Pod::Elemental::Transformer::Nester->new({ top_selector => Pod::Elemental::Selectors::s_command('head3'), content_selectors => [ Pod::Elemental::Selectors::s_command([ qw(head4) ]), Pod::Elemental::Selectors::s_flat(), ], }); $nester->new->transform_node($tree); $nester = Pod::Elemental::Transformer::Nester->new({ top_selector => Pod::Elemental::Selectors::s_command('head2'), content_selectors => [ Pod::Elemental::Selectors::s_command([ qw(head3 head4) ]), Pod::Elemental::Selectors::s_flat(), ], }); $nester->new->transform_node($tree); $nester = Pod::Elemental::Transformer::Nester->new({ top_selector => Pod::Elemental::Selectors::s_command('head1'), content_selectors => [ Pod::Elemental::Selectors::s_command([ qw(head2 head3 head4) ]), Pod::Elemental::Selectors::s_flat(), ], }); $nester->new->transform_node($tree);
**EXAMPLES**
Note: <prog:pmpath> is a CLI utility that returns the path of a locally installed Perl module. It's distributed in <pm:App::PMUtils> distribution.
Select all head1 commands (only print the command lines and not the content):
% podsel `pmpath strict` 'Command[command=head1]' =head1 NAME =head1 SYNOPSIS =head1 DESCRIPTION =head1 HISTORY
Select all head1 commands that contain "SYN" in them (only print the command lines and not the content):
% podsel `pmpath strict` 'Command[command=head1][content =~ /synopsis/i]' =head1 SYNOPSIS
Select all head1 commands that contain "SYN" in them (but now also print the content; note now the use of the `Nested` class selector and the `-5` flag to create a nested document tree instead of a flat one):
% podsel -5 `pmpath strict` 'Nested[command=head1][content =~ /synopsis/i]' =head1 SYNOPSIS use strict; use strict "vars"; use strict "refs"; use strict "subs"; use strict; no strict "vars";
List of head commands in POD of <pm:List::Util>:
% podsel `pmpath List::Util` 'Command[command =~ /head/]' =head1 NAME =head1 SYNOPSIS =head1 DESCRIPTION =head1 LIST-REDUCTION FUNCTIONS =head2 reduce =head2 reductions ... =head1 KEY/VALUE PAIR LIST FUNCTIONS =head2 pairs =head2 unpairs =head2 pairkeys =head2 pairvalues ...
List only key/value pair list functions and not list-reduction ones:
% podsel -5 `pmpath List::Util` 'Nested[command=head1][content =~ /pair/i] Nested[command=head2]' --print-method content pairs unpairs pairkeys pairvalues pairgrep pairfirst pairmap
Can be specified multiple times.
- --transforms-json=s
-
Apply one or more Pod::Elemental::Transform's (JSON-encoded).
See
--transform
. - -5
-
Shortcut for -t Pod5 -t Nester.
See
--transform
. - -R
-
Shortcut for --node-action-on-descendants=descendants_depth_first.
See
--node-actions-on-descendants
.
Logging options
- --debug
-
Shortcut for --log-level=debug.
- --log-level=s
-
Set log level.
- --quiet
-
Shortcut for --log-level=error.
- --trace
-
Shortcut for --log-level=trace.
- --verbose
-
Shortcut for --log-level=info.
Output options
- --format=s
-
Choose output format, e.g. json, text.
Default value:
undef
- --json
-
Set output format to json.
- --naked-res
-
When outputing as JSON, strip result envelope.
Default value:
0
By default, when outputing as JSON, the full enveloped result is returned, e.g.:
[200,"OK",[1,2,3],{"func.extra"=>4}]
The reason is so you can get the status (1st element), status message (2nd element) as well as result metadata/extra result (4th element) instead of just the result (3rd element). However, sometimes you want just the result, e.g. when you want to pipe the result for more post-processing. In this case you can use `--naked-res` so you just get:
[1,2,3]
- --page-result
-
Filter output through a pager.
Other options
COMPLETION
This script has shell tab completion capability with support for several shells.
bash
To activate bash completion for this script, put:
complete -C podsel podsel
in your bash startup (e.g. ~/.bashrc). Your next shell session will then recognize tab completion for the command. Or, you can also directly execute the line above in your shell to activate immediately.
It is recommended, however, that you install modules using cpanm-shcompgen which can activate shell completion for scripts immediately.
tcsh
To activate tcsh completion for this script, put:
complete podsel 'p/*/`podsel`/'
in your tcsh startup (e.g. ~/.tcshrc). Your next shell session will then recognize tab completion for the command. Or, you can also directly execute the line above in your shell to activate immediately.
It is also recommended to install shcompgen (see above).
other shells
For fish and zsh, install shcompgen as described above.
HOMEPAGE
Please visit the project's homepage at https://metacpan.org/release/App-podsel.
SOURCE
Source repository is at https://github.com/perlancar/perl-App-podsel.
BUGS
Please report any bugs or feature requests on the bugtracker website https://rt.cpan.org/Public/Dist/Display.html?Name=App-podsel
When submitting a bug or request, please include a test-file or a patch to an existing test-file that illustrates the bug or desired feature.
SEE ALSO
Other utilities that use CSel against various data: ddsel, jsonsel, orgsel, podsel, htmlsel, yamlsel.
AUTHOR
perlancar <perlancar@cpan.org>
COPYRIGHT AND LICENSE
This software is copyright (c) 2020, 2019 by perlancar@cpan.org.
This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself.