emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Keith Lancaster <klancaster1957@mac.com>
To: org-mode <emacs-orgmode@gnu.org>
Subject: Re: Hiding #+XXX lines
Date: Fri, 22 May 2009 16:12:31 -0500	[thread overview]
Message-ID: <55BD7803-B521-4EF1-A386-23FA8599DEB8@mac.com> (raw)
In-Reply-To: <4A171336.8020304@gmail.com>

Thanks to both of you! I'll give each a try and see which works for  
me. On this topic generally, I am using separate files for each  
project. So far, I've been copying text similar to that below to each  
new project, but given the breadth of org-mode, I'm guessing that I'm  
"doing it wrong". How do you handle this?


On May 22, 2009, at 4:03 PM, Michael Mrozek wrote:

> Daniel J. Sinder wrote:
>> As Keith Lancaster so eloquently wrote on 5/21/2009 2:41 PM:
>>> Is it possible to hide, during normal editing, the configuration /
>>> comment lines in a project file?
>> I put my entire top-of-the-file configuration in a property drawer.
>> It can obviously be expanded on demand, but otherwise is not expanded
>> (ie, when I load the file).
>> My .emacs has this (from Custom):
>> (custom-set-variables
>> '(org-drawers (quote ("PROPERTIES" "SETUP" "LOGBOOK"))))
>> The my .org file has this at the top (for example):
>> :SETUP:
>> #+STARTUP:   hidestars odd lognoteclock-out lognotedone
>> #+LANGUAGE:  en
>> #+OPTIONS:   H:4 num:nil toc:nil \n:nil @:t ::t |:t ^:{} *:t TeX:f
>> #+FILETAGS:  Work
>> :END:
>> Dan
> I have a top-level headline at the end of my file named "Config"  
> that's
> tagged with ARCHIVE so it gets grayed out and doesn't open
> automatically; I don't even notice it anymore

Keith Lancaster

  reply	other threads:[~2009-05-22 21:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-21 21:41 Hiding #+XXX lines Keith Lancaster
2009-05-22 20:35 ` Daniel J. Sinder
2009-05-22 21:03   ` Michael Mrozek
2009-05-22 21:12     ` Keith Lancaster [this message]
2009-05-22 22:33       ` Daniel J. Sinder

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:

  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=55BD7803-B521-4EF1-A386-23FA8599DEB8@mac.com \
    --to=klancaster1957@mac.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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