From: Thorsten Jolitz <tjolitz@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: outline-flag-region: Variable binding depth exceeds max-specpdl-size
Date: Tue, 21 May 2013 19:00:13 +0200 [thread overview]
Message-ID: <878v388e02.fsf@gmail.com> (raw)
Hi List,
I implemented a new (optional and customizable) feature for 'outshine.el':
behind every folded headline, a little 'cookie' can show the number of
hidden lines till the next visible headline.
E.g., an Emacs Lisp buffer structured the 'outshine-way' with
outline-minor-mode and outshine.el activated might look like this after
evaluating 'outshine-show-hidden-lines-cookies':
,-------------------------------------------------------------------------------
| ;; * navi-mode.el --- major-mode for easy buffer-navigation [#13]
| ;; ** Commentary [#1]
| ;; *** About navi-mode
|
| ;; This file implements extensions for occur-mode. You can think of a
| ;; navi-buffer as a kind of 'remote-control' for an (adecuately)
| ;; outline-structured original-buffer. It enables quick navigation and basic
| ;; structure editing in the original-buffer without (necessarily) leaving the
| ;; navi-buffer. When switching to the original-buffer and coming back after
| ;; some modifications, the navi-buffer is always reverted (thus up-to-date).
|
| ;; Besides the fundamental outline-heading-searches (8 outline-levels) and the
| ;; 5 basic keyword-searches (:FUN, :VAR, :DB, :OBJ and :ALL), all languages
| ;; can have their own set of searches and keybindings (see `navi-key-mappings'
| ;; and `navi-keywords'). Heading-searches and keyword-searches can be
| ;; combined, offering a vast amount of possible 'views' at the
| ;; original-buffer.
|
| ;; *** Usage [#165]
| ;; *** Installation [#19]
| ;; *** Emacs Version [#5]
| ;; * Requires [#4]
| ;; * Mode Definitions [#30]
`-------------------------------------------------------------------------------
This works alright so far, and when a folded buffer is expanded or the
number of hidden lines change, the cookies are updated correctly. But
obviously its a bit tedious to manually do
,------------------------------------------
| M-:(outshine-show-hidden-lines-cookies)
`------------------------------------------
each time the status of the buffer changes, so the right thing to do
seems to be:
,-----------------------------------------------
| (add-hook 'outline-view-change-hook
| 'outshine-show-hidden-lines-cookies)
`-----------------------------------------------
This worked shortly, but since then results in the following error:
,---------------------------------------------------------------------
| outline-flag-region: Variable binding depth exceeds max-specpdl-size
`---------------------------------------------------------------------
Whats this error about and what would be a possible fix? There are
several reports about this error for several Emacs modes, but the
background and cure are not really explained.
--
cheers,
Thorsten
next reply other threads:[~2013-05-21 17:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-21 17:00 Thorsten Jolitz [this message]
2013-05-21 21:28 ` outline-flag-region: Variable binding depth exceeds max-specpdl-size 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=878v388e02.fsf@gmail.com \
--to=tjolitz@gmail.com \
--cc=help-gnu-emacs@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.
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).