From: Andrea Crotti <andrea.crotti.0@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Narrow/widen in folding.el
Date: Wed, 22 Dec 2010 10:01:16 +0100 [thread overview]
Message-ID: <m1d3oufag3.fsf@ip1-201.halifax.rwth-aachen.de> (raw)
In-Reply-To: 87zkryz0h0.fsf@member.fsf.org
Tassilo Horn <tassilo@member.fsf.org> writes:
>
> Yes, several modes implement some folding capabilities wtr. some
> syntactic constructs of a programming language. For example, there's
> also hs-minor-mode, which can collapse/expand blocks in languages like
> C/C++/Java.
>
> That's a good thing, but with outline-minor-mode (or folding.el), you
> can add more coarse-grained sections to structure your code into several
> groups of things (e.g. functions) belonging together, like:
>
> ;;* Code
> ;;** User Variables
> ;;** User Commands
> ;;** Internal Implementation
> ;;*** General
> ;;*** Feature A
> ;;*** Feature B
Ah thanks for hs-minor-mode, it's also quite nice and it works at least
with python and C++.
Sure structuring is very nice, but I don't see why you need it when you
can jump fast to sections?
I use tags, isearch or grep as a last resource, and it's very fast.
>
> That's what I like with `outline-minor-mode' and my config (i.e. outline
> headings are `comment-start' + one or many *s). You would comment your
> code anyway (I hope so!), and adding a few * to make a comment a
> headline to make the structure of the file visible is worth it.
>
> But I agree, that I don't like folding.el's obtrusive {{{ ... }}}
> syntax, too.
>
> Bye,
> Tassilo
Well depends, I never comment trivial functions, I try to make them
clear enough and with good names, that's already enough.
So adding a comment just to create the right section would be already
too annoying, but of course becasue I don't really feel I need it.
next prev parent reply other threads:[~2010-12-22 9:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-20 21:41 Narrow/widen in folding.el Leo Alekseyev
2010-12-21 17:24 ` Andrea Crotti
2010-12-21 18:42 ` Tassilo Horn
2010-12-21 22:00 ` Andrea Crotti
2010-12-22 8:16 ` Tassilo Horn
2010-12-22 9:01 ` Andrea Crotti [this message]
2010-12-22 9:14 ` Leo Alekseyev
2010-12-22 11:02 ` Tassilo Horn
2010-12-22 12:26 ` Leo Alekseyev
[not found] ` <mailman.7.1293008512.15562.help-gnu-emacs@gnu.org>
2010-12-23 23:49 ` Tim X
2010-12-25 2:18 ` Leo Alekseyev
2010-12-25 3:08 ` Leo Alekseyev
2010-12-25 4:45 ` Leo Alekseyev
[not found] ` <mailman.9.1293252343.14161.help-gnu-emacs@gnu.org>
2010-12-25 22:48 ` Tim X
2010-12-27 9:19 ` Tassilo Horn
[not found] ` <mailman.0.1293441599.18751.help-gnu-emacs@gnu.org>
2010-12-27 22:37 ` 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=m1d3oufag3.fsf@ip1-201.halifax.rwth-aachen.de \
--to=andrea.crotti.0@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).