unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Robert Thorpe <rt@robertthorpeconsulting.com>
To: Rusi <rustompmody@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: program outlining
Date: Mon, 11 Jul 2016 16:13:57 +0100	[thread overview]
Message-ID: <87a8hotdfu.fsf@robertthorpeconsulting.com> (raw)
In-Reply-To: <69592de8-5bae-48ac-9435-76e219d6ee38@googlegroups.com> (message from Rusi on Mon, 11 Jul 2016 05:59:59 -0700 (PDT))

Rusi <rustompmody@gmail.com> writes:

> Ive been trying to figure out the best outlining that emacs can give for
> programs.
>
> Outline-mode seems to be more for text than code
> Outshine mode inspired by above+org-mode seemed promising in that it seems to
> make org mode's wonderful TAB-behavior work for code.
> But I couldn’t get it to work
>
> So hideshow…
> But hideshow keystrokes are clumsy

There's a difference between personal code and shared code here.

The outline based modes require additions to the code to be made in the
right way.  Making that work with shared code when other people are
using different editors is difficult.  Even if the other programmers use
Emacs, many Emacs users don't use these modes.  This is not a problem if
it's personal code.

Hide/show, selective display and pages are more general tools.  They
require little or nothing to be embedded in the code itself.  But, in
many cases an automatically generated navigation tree can't beat a
manually created one.

So, there's no one best way.

BR,
Robert Thorpe




  parent reply	other threads:[~2016-07-11 15:13 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-11 12:59 program outlining Rusi
2016-07-11 13:48 ` Kaushal Modi
     [not found] ` <mailman.1089.1468244895.26859.help-gnu-emacs@gnu.org>
2016-07-11 14:12   ` Rusi
2016-07-11 14:34     ` Rusi
2016-07-11 14:59     ` Kaushal Modi
2016-07-11 14:53 ` Eli Zaretskii
2016-07-11 15:13 ` Robert Thorpe [this message]
2016-07-11 15:21 ` Emanuel Berg
2016-07-11 18:07   ` Rusi
2016-07-11 18:36     ` Emanuel Berg
2016-07-13 12:49       ` Rusi
2016-07-13 13:31         ` Emanuel Berg
     [not found] ` <mailman.1101.1468248815.26859.help-gnu-emacs@gnu.org>
2016-07-11 18:05   ` Rusi
2016-07-13  1:44 ` Howard Melman
2016-07-13  2:00   ` Drew Adams
     [not found] ` <mailman.1250.1468374265.26859.help-gnu-emacs@gnu.org>
2016-07-13  2:47   ` Rusi
2016-07-13 13:42     ` Howard Melman

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=87a8hotdfu.fsf@robertthorpeconsulting.com \
    --to=rt@robertthorpeconsulting.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=rustompmody@gmail.com \
    /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).