From: Jambunathan K <kjambunathan@gmail.com>
To: Thorsten Jolitz <tjolitz@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Is there a save-outline-visibility excursion or so?
Date: Wed, 22 May 2013 18:09:24 +0530 [thread overview]
Message-ID: <87txlvyyrn.fsf@gmail.com> (raw)
In-Reply-To: <87y5b7b9c1.fsf@gmail.com> (Thorsten Jolitz's message of "Wed, 22 May 2013 12:25:02 +0200")
Thorsten Jolitz <tjolitz@gmail.com> writes:
> Jambunathan K <kjambunathan@gmail.com> writes:
>
>> C-h f save-restriction
>>
>> You will find plenty of examples in Orgmode codebase.
>
> Well, I tried it out, and in this case it does not really reset the
> buffer to its original (partly folded) visibility state, but rather
> leaves it in show-all state. So I guess narrowing/widening and
> outline-visibility changes are, at least at this level, not the same.
Mmmm. Restriction apparently applies to (virtual) bounds of the buffer -
beg and end positions and has nothing to do with invisibility.
----------------------------------------------------------------
You may find it easier to work with `make-indirect-buffer' and
`clone-indirect-buffer' (See Elisp manual).
(I think) In the first case, the indirect buffer starts with no
overlays. In the second case, the indirect buffer starts with same
*overlay values* as the first one.
You can see that any visibility operation on the indirect buffer doesn't
affect the visibility of the original buffer.
----------------------------------------------------------------
If you lookup the `org-export--generate-copy-script', towards the end of
that defun you will see a snippet like this.
,----
| ;; Overlays with invisible property.
| ,@(let (ov-set)
| (mapc
| (lambda (ov)
| (let ((invis-prop (overlay-get ov 'invisible)))
| (when invis-prop
| (push `(overlay-put
| (make-overlay ,(overlay-start ov)
| ,(overlay-end ov))
| 'invisible (quote ,invis-prop))
| ov-set))))
| (overlays-in (point-min) (point-max)))
| ov-set)
`----
Visibility is controlled by `buffer-invisibility-spec'.
This should be a good starting point.
next prev parent reply other threads:[~2013-05-22 12:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 9:13 Is there a save-outline-visibility excursion or so? Thorsten Jolitz
2013-05-22 9:18 ` Jambunathan K
2013-05-22 10:12 ` Thorsten Jolitz
2013-05-22 10:25 ` Thorsten Jolitz
2013-05-22 12:39 ` Jambunathan K [this message]
2013-05-22 13:41 ` Thorsten Jolitz
2013-05-23 1:05 ` Stefan Monnier
2013-05-23 10:43 ` Thorsten Jolitz
2013-05-23 13:09 ` Stefan Monnier
2013-05-24 14:06 ` 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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87txlvyyrn.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=tjolitz@gmail.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.
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).