From: Chris Dolan <[EMAIL PROTECTED]>
Date: Sun, 17 Dec 2006 13:22:53 -0600
On Dec 16, 2006, at 12:41 PM, Paul Cochrane via RT wrote:
> Hi all,
>
> We could close this ticket if a decision were made as to whether or
> not
> the emacs/vim formatting information can be put at the *beginning*
> of a
> file in the case where __END__ or __DATA__ blocks are used within a
> perl source file.
>
> What are people's opinions? Would it be too ugly to put the "coda" at
> the beginning of the file just after the shebang line?
>
> Paul
Be aware that you cannot use the verbose form of Emacs settings at
the beginning of a file, unless the file is shorter than 3000 bytes
. . .
That will still be true for Emacs 22, BTW. However, this wouldn't be
hard to hack around in a cperl-mode hook function. Since we already
insist that people load editor/parrot.el for editing C code, this would
amount to zero additional burden on Parrot hackers. And in that case,
we could put the "Local Variables:" section anywhere we like, so we
might as well keep it at the end of the code, just before any __END__ or
__DATA__ blocks.
I think I would like to write this anyway; it would be a useful
addition to cperl-mode. But in that case, we would also need a
customized Perl::Critic::Policy::Editor::RequireEmacsFileVariables
policy. WDOT?
-- Bob Rogers
http://rgrjr.dyndns.org/
