From mboxrd@z Thu Jan 1 00:00:00 1970 From: Scott Otterson Subject: Re: New test version: org-4.19a Date: Thu, 30 Mar 2006 09:52:27 -0800 Message-ID: <442C1ADB.2040604@u.washington.edu> References: <200603291702.k2TH2Z9a271582@bp04.u.washington.edu> <442B488C.4070106@u.washington.edu> <06da1ae5c2d023418b53f85974f09d7e@science.uva.nl> <442B82B3.6030401@u.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FP1Jv-0007WP-Kd for emacs-orgmode@gnu.org; Thu, 30 Mar 2006 12:52:31 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FP1Ju-0007WD-U6 for emacs-orgmode@gnu.org; Thu, 30 Mar 2006 12:52:31 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FP1Ju-0007WA-Pi for emacs-orgmode@gnu.org; Thu, 30 Mar 2006 12:52:30 -0500 Received: from [140.142.32.166] (helo=mxout3.cac.washington.edu) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1FP1M8-00080W-4e for emacs-orgmode@gnu.org; Thu, 30 Mar 2006 12:54:48 -0500 In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Carsten Dominik Cc: emacs-orgmode@gnu.org Good idea about the *Messages* buffer -- I've always completely ignored it. Looking at it over, I realized that my problem is due to a conflict between org-4-19a and an old allout setting I had in my .emacs. With these lines in my .emacs: ----------------------------------------------- (defvar rf-allout-font-lock-keywords '(;; ;; Highlight headings according to the level. (eval . (list (concat "^\\(" outline-regexp "\\).+") 0 '(or (cdr (assq (outline-depth) '((1 . font-lock-function-name-face) (2 . font-lock-variable-name-face) (3 . font-lock-keyword-face) (4 . font-lock-builtin-face) (5 . font-lock-comment-face) (6 . font-lock-constant-face) (7 . font-lock-type-face) (8 . font-lock-string-face)))) font-lock-warning-face) nil t))) "Additional expressions to highlight in Outline mode.") ;; add font-lock to allout mode (defun rf-allout-font-lock-hook () (set (make-local-variable 'font-lock-defaults) '(rf-allout-font-lock-keywords t nil nil outline-back-to-current-heading)) ; doesn't work here? works if use emacs customizer (so leave it there) ;(setq outline-plain-bullets-string "-*-*-") ; not fontlocking... ; lead w/ spaces, could instead use: `outline-use-mode-specific-leader' ;(setq outline-header-prefix ".") ) (add-hook 'outline-mode-hook 'rf-allout-font-lock-hook) ---------------------------------------------- I got this message in *Messages*: Error during redisplay: (void-function outline-depth) [7 times] When I removed the allout settings above, the error went away and fontlocking in org-mode works again. Links now display very nicely. A couple comments * URL links work great. I think this is a big improvement! * It would be nice if file TAB completion worked after the minibuffer "Link" prompt * looks the stuff at the top of p. 18 of the manual has been obsoleted by this change. Tthe <>'s are no longer neded in "[[][GNU Emacs]])" although they still work. * Are the <>'s required anymore? At the C-c C-l "Link:" prompt is it possible to write things so that you can just type: file:afilename news:comp.emacs instead of: * It would be cool if file TAB completion worked after typing "file:" * If I hit BACKSPACE in a link, then the guts of the link are displayed. But then it's not clear how to repair the link to make them hidden again. Thanks for the changes, Scott Carsten Dominik (03/29/2006 11:49 PM) wrote: > I cannot reproduce this under Emacs 22.0.50.1. I tried under Linux and > under MacOS, works fine in both cases. > > Is there something in the *Messages* buffer that looks suspicious? What > if you turn off font-lock-mode, and then turn it back on? > > How does your font-lock and org-mode related setup look like, have you > configured something I don't?