From: Wang Lei <fxhjgzydw@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: How to expertly fold perl or other scripting code.
Date: Sun, 20 Sep 2009 13:22:34 +0800 [thread overview]
Message-ID: <b97f47d60909192222v1c57e15du113126b5b9d00a3f@mail.gmail.com> (raw)
In-Reply-To: <87my4q8dsq.fsf@lion.rapttech.com.au>
On 9/20/09, Tim X <timx@nospam.dev.null> wrote:
> Andreas Politz <politza@fh-trier.de> writes:
>
>> Harry Putnam <reader@newsguy.com> writes:
>>
>>> I see too much output on google that looks very complex when I try to
>>> delve into folding code in emacs.
>>>
>>> Is it horribly complicated?
>>>
>>> I know some windows editors or ide's do such folding very
>>> quickly... but I'm not going to do my coding on windows. I'm far to
>>> comfortable on linux or opensolaris, but I would really like to have
>>> the ability to fold/unfold code as needed, quickly and easily.
>>
>> M-x outline-minor-mode RET
>> C-c @ C-t
>>
>> For a start...
>>
>
> I personally find outline of limited use when it comes to folding
> code. However, there are a few folding modes out there (check the emacs
> wiki). I use an old mode called folding.el (which is bundled in the
> emacs-goodies debian package. It works quite well, is easy to install
> and provides good functionality.
>>
>>Tim
>
>
> --
> tcross (at) rapttech dot com dot au
>
After reading these from folding.el, I decided to use hs-minor-mode.
;;
;; Please note, that the maintainers do not recommend to use only
;; folding for you your code layout and navigation. Folding.el is
;; on its best when it can "chunk" large sections of code inside
;; folds. The larger the chunks, the more the usability of
;; folding will increase. Folding.el is not meant to hide
;; individual functions: you may be better served by hideshow.el
;; or imenu.el (which can parse the function indexes)
--
Regards,
Lei
next prev parent reply other threads:[~2009-09-20 5:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-19 21:58 How to expertly fold perl or other scripting code Harry Putnam
2009-09-19 23:16 ` Andreas Politz
2009-09-20 1:44 ` Bernardo
2009-09-20 17:24 ` Harry Putnam
2009-09-20 22:31 ` Wang Lei
[not found] ` <mailman.7073.1253402286.2239.help-gnu-emacs@gnu.org>
2009-09-20 4:01 ` Tim X
2009-09-20 5:22 ` Wang Lei [this message]
2009-09-20 16:36 ` Harry Putnam
[not found] ` <mailman.7099.1253464623.2239.help-gnu-emacs@gnu.org>
2009-09-21 7:51 ` Tim X
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=b97f47d60909192222v1c57e15du113126b5b9d00a3f@mail.gmail.com \
--to=fxhjgzydw@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.
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).