emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bastien.guerry@wikimedia.fr>
To: Leonidas Tsampros <ltsampros@upnet.gr>
Cc: emacs-orgmode@gnu.org
Subject: Re: Hiding/Narrowing dblocks and keywords
Date: Wed, 02 Feb 2011 16:38:27 +0100	[thread overview]
Message-ID: <877hdimop8.fsf@gnu.org> (raw)
In-Reply-To: <87oc6uldmp.fsf@bifteki.lan> (Leonidas Tsampros's message of "Wed, 02 Feb 2011 16:22:54 +0200")

Hi Leonidas,

Leonidas Tsampros <ltsampros@upnet.gr> writes:

> My question is: Can I hide the keywords defined on the top of the buffer

You can hide *some* keywords with org-hidden-keywords.  The docstring
was not accurate, I just fixed it.  For example you can use:

  (setq org-hidden-keywords '(author)) 

to make the #+AUTHOR: keyword invisible.  You cannot use *any* keyword
though: only title, author, date, email.  I think it makes sense since
hiding other #+* keywords could be confusing (but I don't have a strong
opinion about this.)

> * test entry1
> #+BEGIN clocktable :maxlevel 3 :scope file :link
> Clock summary etc etc
>
> <clock table would be here with multiple lines>
> #+END:

You can hide #+begin blocks at startup with this:

  (setq org-hide-block-startup t)

There was a bug here preventing the folding of dynamic blocks, other
blocks were folding okay.

See also 

  M-x org-hide-block-all
  M-x org-hide-block-toggle

> Did I clarify my question enough? Or am I misunderstading the way
> dblocks/keywords work?

Hope I clarified some points, thanks!

-- 
 Bastien

      reply	other threads:[~2011-02-02 15:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-30 20:28 Hiding/Narrowing dblocks and keywords Leonidas Tsampros
2011-02-02 10:52 ` Bastien
2011-02-02 14:22   ` Leonidas Tsampros
2011-02-02 15:38     ` Bastien [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=877hdimop8.fsf@gnu.org \
    --to=bastien.guerry@wikimedia.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=ltsampros@upnet.gr \
    /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).