-
Notifications
You must be signed in to change notification settings - Fork 589
Closed
Labels
Closable?We might be able to close this ticket, but we need to check with the reporterWe might be able to close this ticket, but we need to check with the reportertype-library
Description
Migrated from rt.perl.org#131762 (status was 'open')
Searchable as RT131762$
Metadata
Metadata
Assignees
Labels
Closable?We might be able to close this ticket, but we need to check with the reporterWe might be able to close this ticket, but we need to check with the reportertype-library
Type
Projects
Milestone
Relationships
Development
Select code repository
Activity
p5pRT commentedon Jul 17, 2017
From zefram@fysh.org
Created by zefram@fysh.org
As has been discussed in some previous tickets, recent versions of
Pod::Perldoc (and hence the perldoc(1) command) have bad behaviour
regarding the form of their output, particularly in a default invocation.
It is a problem that the perl core distro bundles a module with this
bad behaviour, and especially with it arising in a tool that forms such
an important part of the user experience. I'm opening this ticket to
track the specific issue of the core distro exhibiting misbehaviour in
this area. I think this should be a 5.28.0 blocker.
There have been several slightly different versions of the bad behaviour;
I'm not tying this ticket to any specific form of misbehaviour.
Problems have arisen in two main areas. Firstly, using by default a
formatter that doesn't produce properly plain (pageable) text output.
(The problem originally arose in switching the default from the ToMan
formatter to the ToTerm formatter, in Pod::Perldoc 3.20.) Secondly,
since Pod::Perldoc 3.25, dishonouring the user's pager configuration in
an attempt to address the first problem.
Various tickets (current and historical) regarding various versions of the
problem: [rt.cpan.org #120229] [rt.cpan.org #98636] [rt.cpan.org #88204]
[perl #130759]
https://rt.cpan.org/Public/Bug/Display.html?id=120229
https://rt.cpan.org/Public/Bug/Display.html?id=98636
https://rt.cpan.org/Public/Bug/Display.html?id=88204
https://rt.perl.org/Public/Bug/Display.html?id=130759
Perl Info
p5pRT commentedon Sep 22, 2017
From zefram@fysh.org
I wrote:
Bump. We're halfway to contentious code freeze and this hasn't been
addressed. The current Pod::Perldoc 3.28 still generates unpageable
output by default, and still makes unportable changes to pager
configuration. If this doesn't get fixed upstream soonish, we should
customise Pod::Perldoc in blead in the obvious manner (default to ToText
renderer on all platforms, never call $formatter->pager_configuration).
-zefram
p5pRT commentedon Oct 7, 2017
From zefram@fysh.org
I wrote:
I have implemented this customisation on branch
zefram/perldoc_portability. If there's no upstream movement and no
objections, I intend to merge this to blead in time for 5.27.5.
-zefram
p5pRT commentedon Oct 8, 2017
From @xsawyerx
On 10/07/2017 06:46 AM, Zefram wrote:
I will contact Mark Allen to discuss fixing Pod::Perldoc entirely. This
can go in 5.27.5 and, at most, reverted afterwards if we could upgrade a
version of Pod::Perldoc that fixes it.
Does that make sense?
p5pRT commentedon Oct 8, 2017
The RT System itself - Status changed from 'new' to 'open'
p5pRT commentedon Oct 16, 2017
From zefram@fysh.org
I wrote:
Now applied to blead as f2ee4cb.
-zefram
jkeenan commentedon Feb 3, 2020
Zefram originally filed this ticket in 2017, but applied a patch that same year.
What remains to be done before we can close this ticket?
Thank you very much.
Jim Keenan
khwilliamson commentedon Apr 10, 2022
No response in over 2 years, and a patch was applied; closing
xsawyerx commentedon Apr 10, 2022
There's a long-running issue with the behavior of perldoc and its output. The most relevant ticket is probably briandfoy/pod-perldoc#36. Zefram provided specific feedback on finer points in restoring the handling of perldoc but I didn't get around to addressing them.