From: John Kitchin <jkitchin@andrew.cmu.edu>
To: Rasmus <rasmus@gmx.us>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: how does invisibility impact org?
Date: Tue, 26 Apr 2016 14:47:03 -0400 [thread overview]
Message-ID: <CAJ51ETpaXUoOn21MFNjEHYrSvdf-nAoaq3ez7q5VT-sAxO+TkQ@mail.gmail.com> (raw)
In-Reply-To: <87h9eop68l.fsf@gmx.us>
[-- Attachment #1: Type: text/plain, Size: 1178 bytes --]
normally I would use narrowing, but I want to see all the verses in the
document at once., so I was going to make all the other text temporarily
invisible.
John
-----------------------------------
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu
On Tue, Apr 26, 2016 at 2:36 PM, Rasmus <rasmus@gmx.us> wrote:
> John Kitchin <jkitchin@andrew.cmu.edu> writes:
>
> > Hi, I am trying to use this code to make parts of an org-file that are
> > not a verse block invisible. That part works fine, and I can also unhide
> > it. However, after that, I get errors like
>
> Isn't this the job of narrowing and widening? Though I guess this could
> only show one verse block at the time.
>
> I.e. use something like this:
>
> (defun narrow-to-next-verse ()
> (interactive)
> (widen)
> (let ((next-elm (search-forward-regexp "^#\\+BEGIN_VERSE" nil t)))
> (when next-elm
> (widen)
> (goto-char next-elm)
> (org-narrow-to-element)
> (goto-char (point-min))
> (forward-line))))
>
> Rasmus
>
> --
> Hooray!
>
>
>
[-- Attachment #2: Type: text/html, Size: 1965 bytes --]
prev parent reply other threads:[~2016-04-26 18:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-26 17:50 how does invisibility impact org? John Kitchin
2016-04-26 18:36 ` Rasmus
2016-04-26 18:47 ` John Kitchin [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=CAJ51ETpaXUoOn21MFNjEHYrSvdf-nAoaq3ez7q5VT-sAxO+TkQ@mail.gmail.com \
--to=jkitchin@andrew.cmu.edu \
--cc=emacs-orgmode@gnu.org \
--cc=rasmus@gmx.us \
/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).