From: Emmanuel Charpentier <emm.charpentier@free.fr>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: Possible bug in org-mode (MELPA version as of 1018-11-25) : #+language: is not (fully) honored.
Date: Mon, 26 Nov 2018 04:40:40 +0100 [thread overview]
Message-ID: <8e5cfb1695d0d1ab18752b281800e67012210c1d.camel@free.fr> (raw)
In-Reply-To: <877eh0zt4n.fsf@nicolasgoaziou.fr>
Yet another data point:
I followed your suggestion :
* desinstalled MELPA's org
* cloned https://code.orgmode.org/bzg/org-mode.git
* make autoloads
* make
* emacs -q
* M-: (add-to-list 'load-path "<relevant directory>/org-mode/lisp")
C-c C-e l o still gets me the same result (i. e. a table of contents
entitled "Contents" rather than "Table des matières").
I got this result
* using the (default) master branch
* using the "next" branch :
- git branch next origin/next
- git checkout next
- make autoloads
- make
In both branches, make says "org-version: 9.1.14 (release_9.1.14-1124-
gfb5e3e)" at the end of compilation.
I'm stymied...
I have but one *visual* clue : whereas the fontlock gives me a gray
color for #+title, #+author and #+date (light gray for the tags, dark
blue for the title, medium grey for author and date), "#+language: fr"
remains in red, even after C-c C-c. (Approximate colors : I'm semi-
color-blind).
HTH,
--
Emmanuel Charpentier
Le dimanche 25 novembre 2018 à 23:31 +0100, Nicolas Goaziou a écrit :
> Emmanuel Charpentier <emm.charpentier@free.fr> writes:
>
> > Thanks for a prompt answer ! A couple questions :
> >
> > 1) What do you mean by "minimal configuration" ? A stripped
> > .emacs/d/init.el ?
>
> Indeed.
>
> > 2) How can I get the "development version" ? I'm following MELPA
> > already...
>
> You have to clone the repository and load Org from there, "master"
> branch, aka "Org 9.2".
next prev parent reply other threads:[~2018-11-26 3:40 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-25 15:54 Possible bug in org-mode (MELPA version as of 1018-11-25) : #+language: is not (fully) honored Emmanuel Charpentier
2018-11-25 19:03 ` Nicolas Goaziou
2018-11-25 20:32 ` Emmanuel Charpentier
2018-11-25 22:31 ` Nicolas Goaziou
2018-11-26 3:40 ` Emmanuel Charpentier [this message]
2018-11-26 8:58 ` Nicolas Goaziou
2018-11-25 21:33 ` Emmanuel Charpentier
2018-11-27 14:19 ` Michael Welle
-- strict thread matches above, loose matches on Subject: below --
2018-11-25 18:01 emanuel.charpentier
2018-11-25 20:36 emanuel.charpentier
2018-11-27 14:20 ` Eric S Fraga
2018-11-27 15:29 ` Emmanuel Charpentier
2018-11-27 20:26 ` Nicolas Goaziou
2018-11-27 20:55 ` emanuel.charpentier
2018-11-27 23:40 ` Nicolas Goaziou
2018-11-28 11:38 ` Emmanuel Charpentier
2018-11-28 14:06 ` Nicolas Goaziou
2018-11-29 7:21 ` emanuel.charpentier
2018-11-29 14:07 ` Nicolas Goaziou
2018-11-29 17:31 ` Emmanuel Charpentier
2018-11-29 19:12 ` Nicolas Goaziou
2018-12-02 20:26 ` emanuel.charpentier
2018-12-05 16:37 ` Emmanuel Charpentier
2018-12-06 22:40 ` Nicolas Goaziou
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=8e5cfb1695d0d1ab18752b281800e67012210c1d.camel@free.fr \
--to=emm.charpentier@free.fr \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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).