Instead of worrying too much about indentation while I'm coding, I just get it down and then use Perltidy to clean up the details.

You can use something like this to tidy up your Perl code from within Emacs:

(global-set-key "\C-xt" 'perltidy-region)
(setq shell-command-default-error-buffer "perltidy-errors")
(defun perltidy-region ()
  "Run the perltidy parser on the current region."
  (interactive)
  (let ((start (mark))
        (end (point))
        (command "perltidy"))
        (shell-command-on-region start end command t t shell-command-d
+efault-error-buffer)))

[download]

Put this in your ~/.emacs file, select the region you want to clean up and type C-xt or M-x perltidy-region.

In reply to Re: Specific Indentation request for perl in Emacs by rhythmicus
in thread Specific Indentation request for perl in Emacs by Yoyoson

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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! —
  • 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:
    & &amp;
    < &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.