comment on

> Auto Complete ... I know some also like company-mode

These two modes are very similar and do basically the same.

Their usefulness heavily depends on the configured provider back-ends (so called "omni-completion" )... and from what I see both don't bring notable Perl support out of the box.

At least plsense builds on auto-complete to provide Perl omni-completion.

But if you have details on why to prefer the one over the other, I'd be interested to hear them.

> I prefer flycheck to flymake,

IMHO fly-make is build in, that's why I use it. The intention of my talk is to give an overview, people are free to experiment and contribute better solutions.

Cheers Rolf
_{(addicted to the Perl Programming Language and ☆☆☆☆ :)

Je suis Charlie!}

In reply to Re^2: [EMACS] "Emacs as Perl IDE" - Abstract for YAPC::EU 2016 by LanX
in thread [EMACS] "Emacs as Perl IDE" - Abstract for YAPC::EU 2016 by LanX

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Syntactic Confectionery Delight
	PerlMonks