From: Jai Dayal <dayalsoap@gmail.com>
To: Tassilo Horn <tsdh@gnu.org>
Cc: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>,
C K Kashyap <ckkashyap@gmail.com>
Subject: Re: Arbitrary folding in emacs
Date: Fri, 28 Mar 2014 10:28:17 -0400 [thread overview]
Message-ID: <CAMJ-YiS1GxRaxnNa4M9=bVbnrO0B2BL=dBztep97Nk6pOh46Jg@mail.gmail.com> (raw)
In-Reply-To: <87r45mmmpe.fsf@thinkpad-t440p.fritz.box>
Emacs doesn't have code folding natively. You can get folding.el, though
http://git.savannah.gnu.org/cgit/emacs-tiny-tools.git/tree/lisp/other/folding.el?h=devel
On Fri, Mar 28, 2014 at 10:17 AM, Tassilo Horn <tsdh@gnu.org> wrote:
> Tim Visher <tim.visher@gmail.com> writes:
>
> >> narrowing the region is kind of opposite of what I am looking for -
> >> but I'll give it a shot - I am not familiar with it.
> >
> > To be clear, what I believe Eli is saying is to mark the entirety of
> > the buffer that you're interested in seeing, and then Calling
> > narrow-to-region.
>
> He's right, it's still the opposite. I wants to mark what he doesn't
> want to see whereas you mark what you want to see with narrowing. His
> approach has the possible benefit that you could divide the buffer into
> many hidden, shown, hidden, shown,... regions. With narrowing, it's
> always hidden, shown, hidden.
>
> Bye,
> Tassilo
>
>
next prev parent reply other threads:[~2014-03-28 14:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-28 9:06 Arbitrary folding in emacs C K Kashyap
2014-03-28 9:12 ` Eli Zaretskii
2014-03-28 9:25 ` C K Kashyap
2014-03-28 9:37 ` Eli Zaretskii
2014-03-28 9:50 ` C K Kashyap
2014-03-28 11:45 ` Tim Visher
2014-03-28 12:26 ` Nicolas Richard
2014-03-28 22:32 ` Stefan Monnier
2014-03-30 10:19 ` Nicolas Richard
2014-03-28 14:17 ` Tassilo Horn
2014-03-28 14:28 ` Jai Dayal [this message]
2014-03-29 20:29 ` Jarek Czekalski
2014-03-29 6:42 ` Marcin Borkowski
2014-03-31 15:15 ` Tim Visher
2014-03-28 20:00 ` Thien-Thi Nguyen
2014-03-28 19:58 ` Jai Dayal
2014-03-31 8:02 ` Andreas Röhler
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='CAMJ-YiS1GxRaxnNa4M9=bVbnrO0B2BL=dBztep97Nk6pOh46Jg@mail.gmail.com' \
--to=dayalsoap@gmail.com \
--cc=ckkashyap@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=tsdh@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).