From: Thorsten Jolitz <tjolitz@gmail.com>
To: emacs-devel@gnu.org
Cc: Bastien <bzg@gnu.org>
Subject: Re: Modern Conventions for Emacs Lisp files?
Date: Mon, 15 Apr 2013 10:37:21 +0200 [thread overview]
Message-ID: <87y5cknq9q.fsf@gmail.com> (raw)
In-Reply-To: 87li8m3sny.fsf@gmail.com
Thorsten Jolitz <tjolitz@gmail.com> writes:
> PS
> There is one strange problem I have:
>
> I can not open org.el any more, now that the oldschool elisp headers are
> recognized by 'outshine' too. Its a big file, but size can't be the
> problem since other quite big files open within 1 or 2 seconds or so.
> When I try to open org.el, Emacs apparently goes into an infinite loop
> and uses 100pc CPU - I have to kill the Emacs process and restart Emacs
> to recover from that.
>
> What might be different in org.el than in all the other elisp files I
> tested so far to cause this problem?
FYI:
I figured out whats different in org.el and causes the problem described
above: its the one long line consisting only of ';' in the preamble,
just above the 'Commentary:' section.
,------------------------------------------------------------------------------
| ;;; org.el --- Outline-based notes management and organizer
|
| ;; Carstens outline-mode for keeping track of everything.
| ;; Copyright (C) 2004-2013 Free Software Foundation, Inc.
| ;;
| ;; Author: Carsten Dominik <carsten at orgmode dot org>
| ;; Maintainer: Bastien Guerry <bzg at gnu dot org>
| ;; Keywords: outlines, hypermedia, calendar, wp
| ;; Homepage: http://orgmode.org
| ;;
| ;; This file is part of GNU Emacs.
|
| [...]
|
| ;; You should have received a copy of the GNU General Public License
| ;; along with GNU Emacs. If not, see <http://www.gnu.org/licenses/>.
| ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
| ;;
| ;;; Commentary:
| ;;
|
| [...]
`------------------------------------------------------------------------------
I would prefer in this case not to investigate why this line causes such
problems but rather to consider writing such a line a bug.
So maybe Bastien could consider this a bug-report and remove this line?
Because otherwise org.el with its more than 23000 lines is just a
perfect example were the use of outline/outshine and navi-mode for file
structuring, high-level (over)views on the file and easy navigation
makes sense.
--
cheers,
Thorsten
next prev parent reply other threads:[~2013-04-15 8:37 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-08 0:23 Modern Conventions for Emacs Lisp files? Thorsten Jolitz
2013-04-08 9:32 ` Alan Mackenzie
2013-04-08 20:05 ` Thorsten Jolitz
2013-04-08 13:22 ` Stefan Monnier
2013-04-08 13:54 ` Andreas Röhler
2013-04-08 19:51 ` Thorsten Jolitz
2013-04-09 6:05 ` Andreas Röhler
2013-04-08 19:47 ` Thorsten Jolitz
2013-04-08 20:07 ` Stefan Monnier
2013-04-08 20:37 ` Thorsten Jolitz
2013-04-08 21:26 ` Stefan Monnier
2013-04-08 22:21 ` Thorsten Jolitz
2013-04-09 7:29 ` Bastien
2013-04-09 12:27 ` Stefan Monnier
2013-04-09 13:11 ` Bastien
2013-04-09 13:36 ` Andreas Röhler
2013-04-09 13:41 ` Bastien
2013-04-13 23:41 ` Thorsten Jolitz
2013-04-14 0:24 ` Stefan Monnier
2013-04-14 3:06 ` Stefan Monnier
2013-04-14 8:16 ` Thorsten Jolitz
2013-04-15 8:37 ` Thorsten Jolitz [this message]
2013-04-15 9:04 ` Eli Zaretskii
2013-04-15 11:16 ` Thorsten Jolitz
2013-04-15 13:13 ` Stefan Monnier
2013-04-15 9:09 ` Bastien
2013-04-08 20:55 ` Naming internal functions (was: Modern Conventions for Emacs Lisp files?) Christopher Schmidt
2013-04-08 21:28 ` Naming internal functions Stefan Monnier
2013-04-15 13:46 ` Christopher Schmidt
2013-04-15 14:07 ` Eli Zaretskii
2013-04-15 14:14 ` Christopher Schmidt
2013-04-15 14:25 ` Eli Zaretskii
2013-04-15 17:08 ` Christopher Schmidt
2013-04-15 14:16 ` xfq
2013-04-08 22:41 ` Modern Conventions for Emacs Lisp files? Pascal J. Bourguignon
2013-04-08 23:42 ` Thorsten Jolitz
2013-04-09 2:11 ` Stefan Monnier
2013-04-09 8:04 ` Thorsten Jolitz
2013-04-09 12:23 ` Stefan Monnier
2013-04-10 19:06 ` Pascal J. Bourguignon
2013-04-10 20:04 ` Thorsten Jolitz
2013-04-09 9:18 ` Leo Liu
-- strict thread matches above, loose matches on Subject: below --
2013-04-09 14:00 Barry OReilly
2013-04-09 14:39 ` Nicolas Richard
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=87y5cknq9q.fsf@gmail.com \
--to=tjolitz@gmail.com \
--cc=bzg@gnu.org \
--cc=emacs-devel@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.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).