Thanks for the Lightning Talk at GPW 2023. ++

Here the promised feedback, I'll try to keep it short. ;-)

Installation

Fetching from ELPA worked, (but installation failed on my old Emacs24 with a "version 27" requirement, like I've messaged you)

Installation on combination Emacs 28 / Windows/ Strawberry Perl was flawless.

I like the fact that it's a separate package from the huge cperl-mode.

Typing <M-x> perl-doc <RET> Moose <RET> showed me Moose in an extra buffer.

It also has heuristics to show the perldoc -f or -v if asked for function/var name (tho I hope you are aware of ambiguities like open )

Impression

The display is accurate. Code section (i.e. indented POD) is shown in an extra mono-spaced font.

Clicking on links let's me navigate to other jump-marks and new POD pages of other modules in a second buffer.

There is a noticeable short lag because every new POD means starting perdoc in the background

Using imenu to jump to internal headings/jump-marks (like SYNOPSIS ) is also possible.

I like the fact that dabbrev-expand is also automatically parsing the new buffer, i.e. when trying to expand a new method-name/sub-name in my code-buffer it will try to take advantage of the opened POD. ( one of the reasons why I prefer this over a separate browser)

I like the fact that one can navigate the POD now, i.e. to jump from one link to the next and reminds me in that way a bit of Pod::POM::Web or info mode inside emacs.

There is also the command perl-doc-view-source to see the original code generating the POD, very nice.

Bugs

• imenu-add-menubar-index or adding new panes ("windows") is often reversed by a timer trigger in your code forcing a redraw. That's kind of a PITA. (Not sure if this is related to some Emacs28 strangeness.)

Feature requests

• Via a side-bar (like speedbar) I'd like to display imenu's index for navigation. info has this.
• displaying the POD of the actual buffer would be nice
• context-menu and Top-bar entry for mode, alike info or wo/man-mode

Nice to Haves

• syntax-highlighting of code-sections in the POD using the cperl-mode logic
• mouse-over tool-tips like in cperl-mode
• option to open in external browser
• completion/expansion when searching a pod

HTH!!! :)

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.