Re: [BUG] Setting compile command causes fontification error [9.5 (release_9.5-661-g5e0afb @ /home/quintus/.emacs.d/org-mode/lisp/)]

2022-05-29 Thread Christopher M. Miles
Ihor Radchenko writes: > "Christopher M. Miles" writes: > >> From the backtrace, seems (buffer-file-name) returned nil, I guess you >> first created a new buffer and have not saved it to file. That caused it >> return nil. Not Org Mode problem. Not saving file is a common problem in >> young pr

Re: [BUG] Setting compile command causes fontification error [9.5 (release_9.5-661-g5e0afb @ /home/quintus/.emacs.d/org-mode/lisp/)]

2022-05-27 Thread Ihor Radchenko
"Christopher M. Miles" writes: > From the backtrace, seems (buffer-file-name) returned nil, I guess you > first created a new buffer and have not saved it to file. That caused it > return nil. Not Org Mode problem. Not saving file is a common problem in > young programmer as I experienced. No off

Re: [BUG] Setting compile command causes fontification error [9.5 (release_9.5-661-g5e0afb @ /home/quintus/.emacs.d/org-mode/lisp/)]

2022-05-27 Thread Christopher M. Miles
From the backtrace, seems (buffer-file-name) returned nil, I guess you first created a new buffer and have not saved it to file. That caused it return nil. Not Org Mode problem. Not saving file is a common problem in young programmer as I experienced. No offence. Marvin Gülker writes: > Remembe

[BUG] Setting compile command causes fontification error [9.5 (release_9.5-661-g5e0afb @ /home/quintus/.emacs.d/org-mode/lisp/)]

2022-05-27 Thread Marvin Gülker
Remember to cover the basics, that is, what you expected to happen and what in fact did happen. You don't know how to make a good report? See https://orgmode.org/manual/Feedback.html#Feedback Your bug report will be posted to the Org mailing list. --