emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Vicente Vera <vicentemvp@gmail.com>
To: Kyle Meyer <kyle@kyleam.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Issues when compiling Org master from source in GNU Emacs 25.0.50.1
Date: Wed, 20 Jan 2016 15:34:59 -0300	[thread overview]
Message-ID: <CAMfbzvA7Eumu4hs6aduQAVGWjzNv8bac0EKruB98QSsA6fvs9g@mail.gmail.com> (raw)
In-Reply-To: <87poww1d94.fsf@kyleam.com>

Hello Kyle,

Thanks for your reply. I see now why `font-lock-fontify-buffer' hasn't
been replaced.

2016-01-20 12:28 GMT-03:00 Kyle Meyer <kyle@kyleam.com>:
> Hi Vicente,
>
> Vicente Vera <vicentemvp@gmail.com> writes:
>
>> Hello
>>
>> When I started using GNU Emacs compiled from the emacs25 branch two
>> issues come up consistently during Org make routine. These issues are
>> related to changes in the next Emacs version.
>
> Thanks for reporting these.
>
>> Compiling /home/user/repositories/org-mode/lisp/org-src.el...
>>
>> In org-src-font-lock-fontify-block:
>> org-src.el:504:54:Warning: ‘font-lock-fontify-buffer’ is for interactive use
>>     only; use ‘font-lock-ensure’ or ‘font-lock-flush’ instead.
>
> This has been switched over to font-lock-ensure a couple times (in
> f36b19e and then reverted in 99f9999, then again in d81e6b5 and reverted
> in 003a0f1).  When font-lock-ensure is used, source blocks don't get
> highlighted.
>
>> Compiling /home/user/repositories/org-mode/lisp/org.el...
>>
>> In org-fast-tag-selection:
>> org.el:15261:47:Error: ‘add-to-list’ can’t use lexical var ‘buffer-tags’; use
>>     ‘push’ or ‘cl-pushnew’
>
> I think this one should be fixed.  I'll look into it.
>
> --
> Kyle

      reply	other threads:[~2016-01-20 18:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-20 13:32 Issues when compiling Org master from source in GNU Emacs 25.0.50.1 Vicente Vera
2016-01-20 15:28 ` Kyle Meyer
2016-01-20 18:34   ` Vicente Vera [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=CAMfbzvA7Eumu4hs6aduQAVGWjzNv8bac0EKruB98QSsA6fvs9g@mail.gmail.com \
    --to=vicentemvp@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=kyle@kyleam.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).