From: "Piotr Zielinski" <piotr.zielinski@gmail.com>
To: Scott Otterson <scotto@u.washington.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: New test version: org-4.19a
Date: Thu, 30 Mar 2006 19:03:17 +0100 [thread overview]
Message-ID: <3c12eb8d0603301003i404e36a9s847aaefb55e99348@mail.gmail.com> (raw)
In-Reply-To: <442C1ADB.2040604@u.washington.edu>
I've now removed references to org-xemacs-p from org-mouse.
http://www.cl.cam.ac.uk/~pz215/files/org-mouse.el
Piotr
On 30/03/06, Scott Otterson <scotto@u.washington.edu> wrote:
> 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
> "[[<http://www.gnu.org/software/emacs/>][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:
> <file:afilename>
> <news:comp.emacs>
>
> * 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?
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>
prev parent reply other threads:[~2006-03-30 18:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200603291702.k2TH2Z9a271582@bp04.u.washington.edu>
2006-03-30 2:55 ` New test version: org-4.19a Scott Otterson
2006-03-30 4:51 ` Carsten Dominik
2006-03-30 7:03 ` Scott Otterson
2006-03-30 7:49 ` Carsten Dominik
2006-03-30 17:52 ` Scott Otterson
2006-03-30 18:03 ` Piotr Zielinski [this message]
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=3c12eb8d0603301003i404e36a9s847aaefb55e99348@mail.gmail.com \
--to=piotr.zielinski@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=scotto@u.washington.edu \
/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).