From: Nick Dokos <nicholas.dokos@hp.com>
To: Juan Pechiar <juan@pechiar.com>
Cc: "Filippo A. Salustri" <salustri@ryerson.ca>,
nicholas.dokos@hp.com, emacs-orgmode@gnu.org
Subject: Re: hide #+ lines?
Date: Sat, 19 Mar 2011 18:26:50 -0400 [thread overview]
Message-ID: <9973.1300573610@alphaville.dokosmarshall.org> (raw)
In-Reply-To: Message from Juan Pechiar <juan@pechiar.com> of "Sat, 19 Mar 2011 19:06:44 -0300." <20110319220644.GA2276@soloJazz.com>
Juan Pechiar <juan@pechiar.com> wrote:
> On Sat, Mar 19, 2011 at 05:27:23PM -0400, Filippo A. Salustri wrote:
> > I've started using #+ blocks here and there, and (meaning no
> > disrespect) I find them a bit ugly. I would much rather there were
> > some way to hide the #+ directives (without, of course, impeding their
> > functionality).
> > I believe I've done my due diligence, checking doc & google, but I
> > can't find anything to help.
> >
> > Anyone got something to offer?
>
> If you are referring to directives such as export templates, etc.,
> these can in general be placed anywhere in the document. For example,
> inside a COMMENT'ed heading at the end of the document, with folded
> view as default.
>
> You can also have all that in another file and use #+setupfile or
> #include for inclusion.
>
> Other things such as #+category have their equivalent as properties,
> which are normally folded.
Another similar solution (cribbed from this list, but I don't remember
who suggested it) is to define a drawer and put all that stuff in it -
isn't that what drawers are for? :-) Keep the drawer closed and the mess
is hidden - and it is not affected by general visibility cycling: you
have to open the drawer deliberately.
The top of one of my org files looks like this:
--8<---------------cut here---------------start------------->8---
:SETUP:
#+STARTUP: showall lognotedone
#+SEQ_TODO: TODO(t) STARTED(s) WAITING(w) | DONE(d) DEFERRED CANCELLED(c)
#+TAGS: { FINANCES(f) HOME(h) PACC(p) SCHOOL(s) WORK(w) } CALL(c) ERRAND(e)
:END:
--8<---------------cut here---------------end--------------->8---
You need to set up the variable org-drawers - see section 2.8 of the Org manual.
Nick
next prev parent reply other threads:[~2011-03-19 22:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-19 21:27 hide #+ lines? Filippo A. Salustri
2011-03-19 22:06 ` Juan Pechiar
2011-03-19 22:26 ` Nick Dokos [this message]
2011-03-19 22:38 ` Filippo A. Salustri
2011-03-20 1:42 ` Nick Dokos
2011-03-20 1:58 ` Filippo A. Salustri
2011-03-20 2:19 ` Nick Dokos
2011-03-20 14:46 ` Filippo A. Salustri
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=9973.1300573610@alphaville.dokosmarshall.org \
--to=nicholas.dokos@hp.com \
--cc=emacs-orgmode@gnu.org \
--cc=juan@pechiar.com \
--cc=salustri@ryerson.ca \
/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).