-
Notifications
You must be signed in to change notification settings - Fork 560
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
perldoc output misbehaviour #16082
Comments
From zefram@fysh.orgCreated by zefram@fysh.orgAs has been discussed in some previous tickets, recent versions of There have been several slightly different versions of the bad behaviour; Various tickets (current and historical) regarding various versions of the Perl Info
|
From zefram@fysh.orgI wrote:
Bump. We're halfway to contentious code freeze and this hasn't been -zefram |
From zefram@fysh.orgI wrote:
I have implemented this customisation on branch -zefram |
From @xsawyerxOn 10/07/2017 06:46 AM, Zefram wrote:
I will contact Mark Allen to discuss fixing Pod::Perldoc entirely. This Does that make sense? |
The RT System itself - Status changed from 'new' to 'open' |
From zefram@fysh.orgI wrote:
Now applied to blead as f2ee4cb. -zefram |
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. |
No response in over 2 years, and a patch was applied; closing |
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. |
Migrated from rt.perl.org#131762 (status was 'open')
Searchable as RT131762$
The text was updated successfully, but these errors were encountered: