From: Bastien <bzg@altern.org>
To: Gijs Hillenius <gijs@hillenius.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: turn-on-font-lock breaks org-mode in recent emacs [7.9.3e (7.9.3e-3-gb07a9b @ /usr/share/emacs/24.3.50/lisp/org/)]
Date: Tue, 26 Feb 2013 11:49:18 +0100 [thread overview]
Message-ID: <87sj4j8i4x.fsf@bzg.ath.cx> (raw)
In-Reply-To: <87k3pwwma6.fsf@hillenius.net> (Gijs Hillenius's message of "Mon, 25 Feb 2013 14:33:37 +0100")
Hi Gijs,
Gijs Hillenius <gijs@hillenius.net> writes:
> Until today, I had have these two (legacy) lines in my orgmode configuration
>
> ;; (global-font-lock-mode 1) ; for all buffers
>
> which is already a default in emacs. This is also noted in the manual
> http://orgmode.org/manual/Activation.html
You have a cached version of this page, `global-font-lock-mode' is not
mentioned in the current one (refresh the page to check.)
> However: it is still recommended in the Org-Mode Beginners Customization
> Guide http://orgmode.org/worg/org-configs/org-customization-guide.html
It is not anymore, fixed, thanks.
> The second line made a bit of a mess of my .org files with the
> 20130224 version of emacs-snapshot
>
> ;; (add-hook 'org-mode-hook 'turn-on-font-lock) ; org-mode buffers only
>
> org files would still open, but show up as (imaginary example)
> [[gnus:982.3334][link]] instead of the nice underlined clickable links.
Mhh... you mean that, with `global-font-lock-mode' already turned on
and (add-hook 'org-mode-hook 'turn-on-font-lock), then the links are
not clickable anymore? If so, please try ~$ emacs -Q test.org and
report the problem, together with your Emacs and Org versions.
Thanks!
--
Bastien
next prev parent reply other threads:[~2013-02-26 10:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-25 13:33 Bug: turn-on-font-lock breaks org-mode in recent emacs [7.9.3e (7.9.3e-3-gb07a9b @ /usr/share/emacs/24.3.50/lisp/org/)] Gijs Hillenius
2013-02-26 10:49 ` Bastien [this message]
2013-02-28 20:00 ` Fixed Re: Bug: turn-on-font-lock b Gijs Hillenius
2013-03-01 9:58 ` Bastien
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=87sj4j8i4x.fsf@bzg.ath.cx \
--to=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
--cc=gijs@hillenius.net \
/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).