From: Ilya Zakharevich <nospam-abuse@ilyaz.org>
To: help-gnu-emacs@gnu.org
Subject: Re: cperl-mode - how people outline their code?
Date: Tue, 27 Apr 2010 04:13:57 +0000 (UTC) [thread overview]
Message-ID: <slrnhtcp45.j9t.nospam-abuse@powdermilk.math.berkeley.edu> (raw)
In-Reply-To: 837d568f-c895-49c2-b7de-e0c688028ae9@u34g2000yqu.googlegroups.com
On 2010-04-25, LanX <lanx.perl@googlemail.com> wrote:
> from perlpod:
>
> -----------------------
>=pod
>=cut
>
> The ``=pod'' directive does nothing beyond telling the compiler to
> lay off parsing code through the next ``=cut''. It's useful for adding
> another paragraph to the doc if you're mixing up code and pod a lot.
> -----------------------
>
> maybe just assigning a high outline level to lines starting with
> "=pod" might be sufficient.
Unclear: do you say that the handling of =headN, =item etc is already
satisfactory, and only the =pod is mishandled, or what?
> BTW: did you see http://debbugs.gnu.org/cgi/bugreport.cgi?bug=6013
Yes. [This is a contributed code, so I might be very slow in
touching it...]
Ilya
next prev parent reply other threads:[~2010-04-27 4:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-19 15:12 cperl-mode - outline minor mode - subroutines Terrence Brannon
2010-04-19 16:16 ` LanX
2010-04-19 16:39 ` Terrence Brannon
2010-04-19 16:49 ` LanX
2010-04-21 18:28 ` Terrence Brannon
2010-04-22 1:25 ` LanX
2010-04-19 16:41 ` LanX
2010-04-19 18:02 ` Terrence Brannon
2010-04-20 8:22 ` LanX
2010-04-20 19:10 ` Terrence Brannon
2010-04-21 13:52 ` LanX
2010-04-21 18:36 ` David Rogoff
2010-04-23 20:49 ` cperl-mode - how people outline their code? Ilya Zakharevich
2010-04-23 23:09 ` LanX
2010-04-25 2:07 ` Ilya Zakharevich
2010-04-25 10:15 ` LanX
2010-04-25 11:36 ` LanX
2010-04-27 4:13 ` Ilya Zakharevich [this message]
2010-05-04 14:59 ` LanX
2010-07-01 16:16 ` Ted Zlatanov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=slrnhtcp45.j9t.nospam-abuse@powdermilk.math.berkeley.edu \
--to=nospam-abuse@ilyaz.org \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).