emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: York Zhao <gtdplatform@gmail.com>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: Nick Dokos <ndokos@gmail.com>, emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: commit 5ea0228 has problem opening big org-mode file
Date: Mon, 25 Nov 2013 20:38:12 -0500	[thread overview]
Message-ID: <CAD3zm23N6zPAVyX5RwSvLmGDH3oQVkYA789bm5Lzpd=YvQhv7Q@mail.gmail.com> (raw)
In-Reply-To: <CAD3zm22ASvtEAZHohz8f34Cdh8sQ9nOw=FJHZzqvUSiXmymdCQ@mail.gmail.com>

OK, finally I was able to reproduce the problem with a minimal setup.

First goes .emacs file:

--8<---------------cut here---------------start------------->8---
(add-to-list 'load-path "path/to/org-mode")
(add-to-list 'load-path "path/to/org-mode/lisp")  ; this line is the key
(add-to-list 'load-path "path/to/yhj-mode")
(require 'yhj-mode)
--8<---------------cut here---------------end--------------->8---

Second goes yhj-mode.el:

--8<---------------cut here---------------start------------->8---
(require 'org)
(define-derived-mode yhj-mode org-mode "yhj")
(provide 'yhj-mode)
--8<---------------cut here---------------end--------------->8---

Finally, file test.yz:

--8<---------------cut here---------------start------------->8---
# -*- mode:yhj -*-
--8<---------------cut here---------------end--------------->8---

Open file "test.yz" and note the comment line not fortified, open "*message*"
buffer and note the following error:

File local-variables error: (error "Lisp nesting exceeds `max-lisp-eval-depth'")

There are three keys to reproduce, first, you have to make two files, .emacs and
"yhj-mode.el". Second, this line must be present:

(add-to-list 'load-path "path/to/org-mode/lisp")  ; this line is the key

Third, file "yhj-mode.el" has to be byte-compiled.

York


On Mon, Nov 25, 2013 at 5:39 PM, York Zhao <gtdplatform@gmail.com> wrote:
> Oop, I didn't know that I replied to Nicolas instead of to the list because I
> hitted "reply" instead of "reply all". So I'm reposting my previous post to the
> list. Here we go:
>
> In my previous post I actually meant to say that I set `debug-on-quit', have no
> idea why I did `debug-on-error'. But anyways, I'm now pretty sure it was commit
> "5ea0228" that causes problem because the moment I deleted the last two lines in
> (define-derived-mode org-mode outline-mode "Org") everything worked fine.
> Demonstrated below:
>
> (define-derived-mode org-mode outline-mode "Org"
>    ...
>   ;; Delete these two lines and everything worked.
>    (report-errors "File local-variables error: %s"
>      (hack-local-variables))
> )
>
> Also, I figured out that it was my major mode that derived from `org-mode'
> didn't work, and the buffer showed in org-mode, instead of my derived mode. But
> my mode is as simple as:
>
> (define-derived-mode yhj-mode org-mode "yhj"
>   )
>
> With some special key bindings specific to my file that is opened in `yhj-mode'.
>
> By the way, I had toggled `debug-on-quit', but made no difference when I hit
> C-g.
>
>
> Thanks,
>
> York
>
> On Mon, Nov 25, 2013 at 2:26 PM, Thomas S. Dye <tsd@tsdye.com> wrote:
>> Nick Dokos <ndokos@gmail.com> writes:
>>
>>> It may be that hack-local-variables takes a long time to process a large
>>> file, although I don't think so: iirc, it limits itself to a tail of the
>>> file of a given size, or the last "page" of the file (demarcated by ^L),
>>> whichever is smaller.
>>
>> Hi Nick,
>>
>> I haven't noticed any slowdown or hangs since hack-local-variables was
>> introduced.
>>
>> I have noticed that I need to answer the query about loading file local
>> variables twice:
>>
>> Please type y, n, or !, or C-v to scroll: y [2 times]
>>
>> The first y has no apparent effect (except to make the second y
>> effective).
>>
>> hth,
>> Tom
>>
>> --
>> Thomas S. Dye
>> http://www.tsdye.com
>>

  reply	other threads:[~2013-11-26  1:38 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-25  3:55 commit 5ea0228 has problem opening big org-mode file York Zhao
2013-11-25  4:28 ` Nick Dokos
2013-11-25 16:57   ` Nick Dokos
2013-11-25 19:26     ` Thomas S. Dye
2013-11-25 22:39       ` York Zhao
2013-11-26  1:38         ` York Zhao [this message]
2013-11-26  4:29           ` Nick Dokos
2013-11-26  4:53             ` Nick Dokos
2013-11-27  2:26               ` York Zhao
2013-11-27  2:29               ` Thomas S. Dye
2013-11-27 14:27               ` Nick Dokos
2013-11-27 18:58                 ` Achim Gratz
2013-11-27 19:23                   ` Nick Dokos
2013-11-27 19:53                     ` Achim Gratz
2013-11-26 19:25           ` Achim Gratz
2013-11-27  1:46             ` York Zhao
2013-11-27  7:24               ` Achim Gratz
2013-11-28  0:17                 ` York Zhao
2013-11-28  7:25                   ` Achim Gratz
2013-11-29  3:58                     ` York Zhao

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='CAD3zm23N6zPAVyX5RwSvLmGDH3oQVkYA789bm5Lzpd=YvQhv7Q@mail.gmail.com' \
    --to=gtdplatform@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=ndokos@gmail.com \
    --cc=tsd@tsdye.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).