emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: ian@manor-farm.org
Cc: emacs-orgmode@gnu.org
Subject: Re: Folding Source Blocks
Date: Wed, 02 Nov 2011 16:36:08 +0000	[thread overview]
Message-ID: <87ipn2eb2f.fsf@ucl.ac.uk> (raw)
In-Reply-To: <4EB14607.5020602@wilkesley.net> (Ian Barton's message of "Wed, 02 Nov 2011 13:30:47 +0000")

Ian Barton <lists@wilkesley.net> writes:

> On 02/11/11 13:13, Nick Dokos wrote:
>> Ian Barton<lists@wilkesley.net>  wrote:
>>
>
>>> If I have a large begin_src block it can make reading the surrounding
>>> text difficult, as the reader has to keep paging up and down. Ideally
>>> it would be possible to fold src blocks, but I can see that would be
>>> inconsistent with org's structure. I could put the block in a draw,
>>> but was interested in what others do.
>>>
>>
>> Pressing TAB (bound to org-cycle) on a #+BEGIN_SRC line folds the code
>> block for me - not sure whether there is a special setting to allow
>> that, but a quick look at my config did not uncover anything.
>>
>
> Thanks for that. When I start Emacs with no config file, it works for
> me too. Must be some setting in my config that is stopping it working.
>
> Ian.

and 

#+startup: hideblocks

(equivalently: org-hide-block-startup variable)

will start up the org file with all blocks hidden.  I use this all the
time as I tend to have quite large blocks often.
-- 
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.90.1
: using Org-mode version 7.7 (release_7.7.508.ga081)

      reply	other threads:[~2011-11-02 18:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-02  7:28 Folding Source Blocks Ian Barton
     [not found] ` <lists@wilkesley.net>
2011-11-02 13:13   ` Nick Dokos
2011-11-02 13:30     ` Ian Barton
2011-11-02 16:36       ` Eric S Fraga [this message]

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.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ipn2eb2f.fsf@ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    --cc=ian@manor-farm.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 public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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).