From: Terrence Brannon <metaperl@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: cperl-mode - outline minor mode - subroutines
Date: Mon, 19 Apr 2010 09:39:28 -0700 (PDT) [thread overview]
Message-ID: <247ada74-8337-4fdd-90bf-3e6b7c66875c@5g2000yqj.googlegroups.com> (raw)
In-Reply-To: a6a0d304-d85f-4df8-872f-07dde5e93dee@q15g2000yqj.googlegroups.com
On Apr 19, 12:16 pm, LanX <lanx.p...@googlemail.com> wrote:
> > I would like to know how to give hints to outline minor mode, so that
> > the subroutine can be broken down into
> > sections and subsections.
>
> I presume we are talking about cperl-mode?
yes, sorry I must've forgotten to mention that
> HTH please give a note if you are succesful! :)
>
well, what I still dont know is how to outline a subroutine... how to
decompose it into sections and subsections:
sub somesub {
# A - do something
# A1 - do something within do something
# A2 - do something else within do something
# B - next step
# B1 - do something within next step
# B2 - do something else within next step
}
next prev parent reply other threads:[~2010-04-19 16:39 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=247ada74-8337-4fdd-90bf-3e6b7c66875c@5g2000yqj.googlegroups.com \
--to=metaperl@gmail.com \
--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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.