From: Ihor Radchenko <yantar92@gmail.com>
To: Colin Baxter <m43cap@yandex.com>, emacs-orgmode@gnu.org
Subject: Re: keep org drawers visible
Date: Sun, 16 Aug 2020 19:39:17 +0800 [thread overview]
Message-ID: <87sgcmhlay.fsf@localhost> (raw)
In-Reply-To: <87364newa7.fsf@yandex.com>
> I realise the above is none too clear. I can use showeverything in
> STARTUP of course and this does indeed open the drawers. However the
> drawers close and remain closed after multiple uses of <SHIFT>-<TAB>.
> Therefore my question is how can I again reach the showeverything status
> without closing down the file and re-opening it?
Take a look at default org-cycle-hook value. You can remove
org-cycle-hide-drawers from there.
Best,
Ihor
Colin Baxter <m43cap@yandex.com> writes:
>>>>>> Colin Baxter <m43cap@yandex.com> writes:
>
> > Hello,
>
> > Property drawers remaining invisible even when I use <shift>-<TAB>
> > drives me nuts. I know about M-x org-hide-drawer-toggle <RET> but
> > how do I keep the drawers open all the time without having to
> > toggle? I work on the basis that I want to see what I write - if I
> > didn't then I wouldn't have written it.
>
> I realise the above is none too clear. I can use showeverything in
> STARTUP of course and this does indeed open the drawers. However the
> drawers close and remain closed after multiple uses of <SHIFT>-<TAB>.
> Therefore my question is how can I again reach the showeverything status
> without closing down the file and re-opening it?
>
> Colin Baxter.
next prev parent reply other threads:[~2020-08-16 11:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-15 15:33 keep org drawers visible Colin Baxter
2020-08-15 15:58 ` Colin Baxter
2020-08-16 11:39 ` Ihor Radchenko [this message]
2020-08-16 13:19 ` Colin Baxter
2020-08-25 18:01 ` David Rogers
2020-08-25 18:45 ` Colin Baxter
2020-08-26 1:33 ` Ihor Radchenko
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=87sgcmhlay.fsf@localhost \
--to=yantar92@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=m43cap@yandex.com \
/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).