emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: boris martin <boris.martin@univ-rennes1.fr>
To: emacs-orgmode@gnu.org
Subject: Re: Bug: no more fontifying in org mode [9.1.14 (9.1.14-dist @ /home/abel/git-ext/org-9.1.14/lisp/)]
Date: Thu, 15 Nov 2018 09:54:53 +0100	[thread overview]
Message-ID: <092cf0aa-7eef-4c6d-f6d7-0da371f940f7@univ-rennes1.fr> (raw)
In-Reply-To: <87efbngx29.fsf@nicolasgoaziou.fr>

Hello,

same issue occured with the master branch of 
https://code.orgmode.org/bzg/org-mode.git

- is there a way for me to know for sure that there is not interference
from any other git-org

installation file ?

- is there a way for me to put emacs in a verbose debug mode so i can
trace what currently
happened when i open a org file ?

best regards

Le 14/11/2018 à 22:37, Nicolas Goaziou a écrit :
> Hello,
>
> boris martin <boris.martin@univ-rennes1.fr> writes:
>
>> ---------------- minimal-org.el -----------------------
>>
>> ;;; Minimal setup to load latest 'org-mode'
>>
>> ;; activate debugging
>> (setq debug-on-error t
>>       debug-on-signal nil
>>       debug-on-quit nil)
>> (add-to-list 'load-path "~/git-ext/org-9.1.14/lisp")
>> (add-to-list 'load-path "~/git-ext/org-9.1.14/contrib/lisp" t)
>>
>> ---------- en minimal-org.el --------------------------
>>
>> ------------ minimal file where the bug happens -----------
>>
>> *sdfsd*
>> *aezraze*
>> /titi/
>>
>>
>> ------------- end minimal file where the bug happens -----
> I cannot reproduce your issue. Could you try Org development version?
>
> Regards,
>

  reply	other threads:[~2018-11-15  8:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-13 16:11 Bug: no more fontifying in org mode [9.1.14 (9.1.14-dist @ /home/abel/git-ext/org-9.1.14/lisp/)] boris martin
2018-11-13 16:45 ` Nicolas Goaziou
2018-11-14 12:47   ` boris martin
2018-11-14 21:37     ` Nicolas Goaziou
2018-11-15  8:54       ` boris martin [this message]
2018-11-17 21:09         ` 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=092cf0aa-7eef-4c6d-f6d7-0da371f940f7@univ-rennes1.fr \
    --to=boris.martin@univ-rennes1.fr \
    --cc=emacs-orgmode@gnu.org \
    /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).