From: Bob Newell <bobnewell@bobnewell.net>
To: emacs-orgmode@gnu.org
Subject: Per-window visibility cycling
Date: Sun, 07 Jul 2013 14:21:12 -1000 [thread overview]
Message-ID: <87pputzytj.fsf@bobnewell.net> (raw)
This likely has been asked in the past but I didn't find it so please
allow me :)
Is visibility cycling per-buffer and not per-window?
I ask because I want to do a horizontal split of a window containing an
org-mode file. Then I want to do a certain level of visibility cycling
in the left side to sort of make an index. On the right side, I want to
open/close various tree branches without affecting the left side.
But the two always seem to stay in sync with respect to visibility.
Any ideas appreciated.
--
Bob Newell
Honolulu, Hawai`i
* Sent via NoGnus 0.18-Emacs 23.3-Linux Mint 13 *
next reply other threads:[~2013-07-08 0:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-08 0:21 Bob Newell [this message]
2013-07-08 0:24 ` Per-window visibility cycling Samuel Wales
2013-07-08 6:54 ` Thorsten Jolitz
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=87pputzytj.fsf@bobnewell.net \
--to=bobnewell@bobnewell.net \
--cc=emacs-orgmode@gnu.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).