Re: [O] coderef does not provide file path for org-insert-link when not in original buffre
Nicolas Goaziou writes: > Hello, > > stardiviner writes: > >> Because the variable `org-src-source-file' is a bridge to pass info >> between two buffers "source buffer" and source block opened "dedicated >> buffer". So this variable must be global. Otherwise the "dedicated >> buffer" can't read it. > > The variable is set in the "dedicated buffer", and is local to it. OTOH, > the source buffer doesn't need to read it, ever. > > I committed a change in "master" branch. Could you tell me if it fixes > your issue? > > Regards, I tested, confirm that it works. -- [ stardiviner ] I try to make every word tell the meaning what I want to express. Blog: https://stardiviner.github.io/ IRC(freenode): stardiviner, Matrix: stardiviner GPG: F09F650D7D674819892591401B5DF1C95AE89AC3
[O] [SOLVED] Re: coderef does not provide file path for org-insert-link when not in original buffre
Thanks, Nicolas. -- [ stardiviner ] I try to make every word tell the meaning what I want to express. Blog: https://stardiviner.github.io/ IRC(freenode): stardiviner, Matrix: stardiviner GPG: F09F650D7D674819892591401B5DF1C95AE89AC3
Re: [O] Bug: org-back-to-heading with inline tasks above point [9.1.14 (9.1.14-3-geb9955a-elpaplus @ /home/yantar92/.emacs.d/elpa/org-plus-contrib-20180924/)]
Thanks! Did not know about `org-with-limited-levels'. After reading the function docstring again, I see that it behaved correctly. However, it seems that `org-back-to-heading' is not really used according to the docstring in the org source code: - `org-agenda' with subtree restriction: the results are different if you call it below or above an inline task. - `org-attach', `org-attach-dir', `org-attach-tag', with point below/above an inline task behave differently - the following functions from org.el behave depending on the point position (below or above an inline task): `org-entry-beginning-position', `org-entry-end-position', `org-get-heading', `org-get-entry', `org-insert-heading-after-current', `org-promote', `org-demote', `org-move-subtree-down', etc. Some of the functions above give very unexpected results if the point is below an inline task. Would it make sense to add org specific macros to Hacking section of org manual? It is sometimes difficult to guess that some of these macros even exist. Best, Ihor Nicolas Goaziou writes: > Hllo, > > yanta...@gmail.com writes: > >> Consider calling =org-back-to-heading= for the following org entry: >> >> #+begin_src org >> * Sample entry >> >> Some text. >> >> *** TODO Inline task >> *** END >> >> Some more text. >> >> ->(point)<- >> >> Yet another piece of text. >> #+end_src >> >> The expected behaviour is that the point moves to the first line of the >> entry. >> However, the point moves to the end of the inline task. >> >> Indeed, the wrong behaviour is because =outline-regexp= variable is set >> to ="\\*+ "=, which includes inline tasks. > > This is the desired effect. Use the macro `org-with-limited-levels' to > ignore headlines. > > Regards, > > -- > Nicolas Goaziou signature.asc Description: PGP signature
Re: [O] Bug: ODT export fails if NAME: and ref: equation [9.1.14 (9.1.14-1-g4931fc-elpa @ /home/kdm/.emacs.d/elpa/org-20180910/)]
Hello,
Ken Mankoff writes:
> Bumping this bug report. Still valid with this mornings elpa-updated
> org-20181105.
No wonder no one answered this; there is nothing simple in "ox-odt.el".
>> If I have the following simple Org file, latest Org, and a clean emacs
>> session (emacs -Q), ODT export fails.
>>
>> # == BEGIN MWE
>> #+NAME: eq:foo
>> \begin{equation}
>> 42
>> \end{equation}
>> See [[eq:foo]].
>> # == END MWE
>>
>> It does not fail if I comment out either of the #+NAME or the "[[eq:foo]]"
>> lines.
What would be the expected output?
Regards,
--
Nicolas Goaziou
Re: [O] Bug: Capture template insertion fails with #+FOO [9.1.14 (9.1.14-1-g4931fc-elpa @ /home/phil/.emacs.d/elpa/org-9.1.14/)]
Hello,
Philip Hudson writes:
> On Sun, 4 Nov 2018 at 14:03, Nicolas Goaziou wrote:
>> No, it is not the case. AFAIU, in the minimal failing case, you capture
>>
>> #+FOO: bar
>> * Baz
>>
>> This is _not_ a node. A node starts with a headline and everything is
>> contained within that headline. So it doesn't qualify as a valid `entry'
>> capture type.
>
> That's disappointing, and, obviously, news to me. So I have not
> encountered a regression but rather a tightening of the existing
> documented contract. Is that a fair interpretation of what you're
> saying? If so, and not that I doubt you, do you have a reference for
> that?
It is not a tightening of anything. The function responsible for the
raised error is `org-capture-verify-tree'. It is called from the
function responsible for capturing `entry' types since December 2010:
commit 8aacc708dd038fd0d351abbed04d49f813f8a7bf
Author: Carsten Dominik
Date: Thu Dec 16 16:51:04 2010 +0100
Capture: Better error message for invalid entry-type templates
It seems to me the intent is clear, and from the documentation,
I wouldn't have thought about inserting data before the headline. I'm
surprised that your template even worked at some point.
I did my homework, though. I tried the following set-up
(setq org-capture-templates
'(("B" "BUG" entry (file "/tmp/bug-capture.org") "#+BAR: baz\n* Foo"
:immediate-finish t)))
Even in Org 8.2.10, which is old in my book, I got an error mentioning
the template was invalid.
> The idea of 'entry type for templates, and of a node as we are
> discussing it, is that a well-formed and valid Org file is composed
> exclusively of these entities and nothing else. Correct?
Not at all. I'm absolutely not talking about what is a valid Org file.
See for this.
I'm talking about what can be captured using an `entry' template, i.e.,
a node/heading/entry and that's it.
> Sorry if this is getting tiresome. At this point I'm content for you
> to close this issue and move on if you'd rather. I'll change my
> template type to 'plain, or find some other workaround. But if you'd
> like to keep going for the sake of clarifying what the right and
> proper meaning of 'entry and "node" are then I'm glad to participate.
Entry, node, and heading (and to some extent, headline) are synonyms.
They mean star(s) at the beginning of line, followed by a space, and
optionally other stuff of that line.
Contents can be anything as long as no line starts with as many or less
stars followed by a space, i.e., there is no headline of a lesser or
equal level.
In any case, if documentation needs to be clarified, please let me know.
Regards,
--
Nicolas Goaziou
Re: [O] Bug: ODT export fails if NAME: and ref: equation [9.1.14 (9.1.14-1-g4931fc-elpa @ /home/kdm/.emacs.d/elpa/org-20180910/)]
Bumping this bug report. Still valid with this mornings elpa-updated
org-20181105.
-k.
On Thu, Sep 13, 2018 at 11:48 PM Ken Mankoff wrote:
>
> Sorry if this is a triplicate bug report. I emailed this as a message (not
> bug report) to the Org list a week ago, but have seen no reply. I tried an
> official bug report last night which I *think* did not work (mailing from
> within "emacs -Q" does not "just work"), so here I try again.
>
> If I have the following simple Org file, latest Org, and a clean emacs
> session (emacs -Q), ODT export fails.
>
> # == BEGIN MWE
> #+NAME: eq:foo
> \begin{equation}
> 42
> \end{equation}
> See [[eq:foo]].
> # == END MWE
>
> It does not fail if I comment out either of the #+NAME or the "[[eq:foo]]"
> lines. Note, perhaps tangentially related, that the manual shows "#+LABEL:
> ", but I'm using "+#NAME: ", and I thought LABEL was deprecated for NAME
>
>
> https://www.gnu.org/software/emacs/manual/html_node/org/Labels-and-captions-in-ODT-export.html#Labels-and-captions-in-ODT-export
>
> -k.
>
>
>
>
>
> Emacs : GNU Emacs 25.2.2 (x86_64-pc-linux-gnu, GTK+ Version 3.22.21)
> of 2017-09-22, modified by Debian
> Package: Org mode version 9.1.14 (9.1.14-1-g4931fc-elpa @
> /home/kdm/.emacs.d/elpa/org-20180910/)
>
> current state:
> ==
> (setq
> org-tab-first-hook '(org-babel-hide-result-toggle-maybe
> org-babel-header-arg-expand)
> org-speed-command-hook '(org-speed-command-activate
> org-babel-speed-command-activate)
> org-occur-hook '(org-first-headline-recenter)
> org-metaup-hook '(org-babel-load-in-session-maybe)
> org-confirm-shell-link-function 'yes-or-no-p
> org-after-todo-state-change-hook '(org-clock-out-if-current)
> org-src-mode-hook '(org-src-babel-configure-edit-buffer
> org-src-mode-configure-edit-buffer)
> org-agenda-before-write-hook '(org-agenda-add-entry-text)
> org-babel-pre-tangle-hook '(save-buffer)
> org-mode-hook '(#[0 "\300\301\302\303\304$\207"
>[add-hook change-major-mode-hook org-show-block-all
> append
> local]
>5]
> #[0 "\300\301\302\303\304$\207"
>[add-hook change-major-mode-hook
> org-babel-show-result-all
> append local]
>5]
> org-babel-result-hide-spec org-babel-hide-all-hashes)
> org-bibtex-headline-format-function #[257 "\300.\236A\207" [:title] 3
> "\n\n(fn ENTRY)"]
> org-archive-hook '(org-attach-archive-delete-maybe)
> org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-hide-drawers
> org-cycle-show-empty-lines
> org-optimize-window-after-visibility-change)
> org-confirm-elisp-link-function 'yes-or-no-p
> org-metadown-hook '(org-babel-pop-to-session-maybe)
> org-link-parameters '(("id" :follow org-id-open)
>("rmail" :follow org-rmail-open :store
> org-rmail-store-link)
>("mhe" :follow org-mhe-open :store
> org-mhe-store-link)
>("irc" :follow org-irc-visit :store
> org-irc-store-link)
>("info" :follow org-info-open :export
> org-info-export
> :store org-info-store-link)
>("gnus" :follow org-gnus-open :store
> org-gnus-store-link)
>("docview" :follow org-docview-open :export
> org-docview-export :store org-docview-store-link)
>("bibtex" :follow org-bibtex-open :store
> org-bibtex-store-link)
>("bbdb" :follow org-bbdb-open :export
> org-bbdb-export
> :complete org-bbdb-complete-link :store
> org-bbdb-store-link)
>("w3m" :store org-w3m-store-link) ("file+sys")
>("file+emacs") ("doi" :follow org--open-doi-link)
>("elisp" :follow org--open-elisp-link)
>("file" :complete org-file-complete-link)
>("ftp" :follow
> (lambda (path) (browse-url (concat "ftp:" path
>("help" :follow org--open-h
Re: [O] agenda and todo list
I am confused, really, I just saw right now what was the cause of this
problem in my setup. Forget and forgive my ask of help, definitely.
Jo.
Le lun. 5 nov. 2018 à 22:05, Joseph Vidal-Rosset <
joseph.vidal.ros...@gmail.com> a écrit :
> Unfortunately the problem remains the same, even after the change of
> rights on the folders... C-c C-c register the task directly in a todo.org
> in /home/joseph/ and not in the Dropbox/Orgzly folder :(
>
> I need help to fix this.
>
> Best wishes,
>
> Jo.
>
> Le lun. 5 nov. 2018 à 21:50, Joseph Vidal-Rosset <
> joseph.vidal.ros...@gmail.com> a écrit :
>
>> Sorry for this email that I just sent. I understood too late that it was
>> only a problem of rights on my Dropbox folder, created by the Dropbox
>> installation.
>>
>> Thanks Ken, I apologize !
>>
>> Best,
>>
>> Jo.
>>
>> Le lun. 5 nov. 2018 à 21:40, Joseph Vidal-Rosset <
>> joseph.vidal.ros...@gmail.com> a écrit :
>>
>>> Hello everybody,
>>>
>>> I'm trying to configure a todo list and I would be happy to succeed in
>>> getting this todo list in a todo.org file in my Dropbox/Orgzly/ but, I
>>> do not understand why it does not work with my setup:
>>>
>>> ;;file to save todo items
>>> (setq org-agenda-files (quote ("/home/joseph/Dropbox/Orgzly/todo.org")))
>>>
>>> Thetodolist persistsinbeingin myhomeonly
>>> i.e. /home/joseph/ .
>>>
>>> Your help with agenda and todo list would be very welcome.
>>>
>>> Best wishes
>>>
>>>
>>> --
>>> Joseph
>>>
>>
Re: [O] agenda and todo list
Unfortunately the problem remains the same, even after the change of rights
on the folders... C-c C-c register the task directly in a todo.org in
/home/joseph/ and not in the Dropbox/Orgzly folder :(
I need help to fix this.
Best wishes,
Jo.
Le lun. 5 nov. 2018 à 21:50, Joseph Vidal-Rosset <
joseph.vidal.ros...@gmail.com> a écrit :
> Sorry for this email that I just sent. I understood too late that it was
> only a problem of rights on my Dropbox folder, created by the Dropbox
> installation.
>
> Thanks Ken, I apologize !
>
> Best,
>
> Jo.
>
> Le lun. 5 nov. 2018 à 21:40, Joseph Vidal-Rosset <
> joseph.vidal.ros...@gmail.com> a écrit :
>
>> Hello everybody,
>>
>> I'm trying to configure a todo list and I would be happy to succeed in
>> getting this todo list in a todo.org file in my Dropbox/Orgzly/ but, I
>> do not understand why it does not work with my setup:
>>
>> ;;file to save todo items
>> (setq org-agenda-files (quote ("/home/joseph/Dropbox/Orgzly/todo.org")))
>>
>> Thetodolist persistsinbeingin myhomeonly
>> i.e. /home/joseph/ .
>>
>> Your help with agenda and todo list would be very welcome.
>>
>> Best wishes
>>
>>
>> --
>> Joseph
>>
>
Re: [O] Bug: org-back-to-heading with inline tasks above point [9.1.14 (9.1.14-3-geb9955a-elpaplus @ /home/yantar92/.emacs.d/elpa/org-plus-contrib-20180924/)]
Hllo, yanta...@gmail.com writes: > Consider calling =org-back-to-heading= for the following org entry: > > #+begin_src org > * Sample entry > > Some text. > > *** TODO Inline task > *** END > > Some more text. > > ->(point)<- > > Yet another piece of text. > #+end_src > > The expected behaviour is that the point moves to the first line of the > entry. > However, the point moves to the end of the inline task. > > Indeed, the wrong behaviour is because =outline-regexp= variable is set > to ="\\*+ "=, which includes inline tasks. This is the desired effect. Use the macro `org-with-limited-levels' to ignore headlines. Regards, -- Nicolas Goaziou
Re: [O] Bug Tracker?
Hello, Ken Mankoff writes: > Is there some sort of official bug tracker for Org? Or is it just > emails to this list? I'm asking because I have a simple reproducible > bug that has been around for a few months now, and I'm wondering if > I didn't submit the bug in the right place/form/way/etc. There is no official bug tracker. However, Emacs has one. You can send a bug report there, too, if it relates to the Org version shipping with Emacs. Otherwise, the bug tracker is the mailing list archives. > I'm pretty sure it was submitted correctly (via > org-submit-bug-report). Perhaps it is just a low priority and I didn't > include a patch. In which case is the bug lost from our communal > memory, or is there at least a place where it is properly filed as > "open"? AFAICT, it felt through the cracks. You may want to bump it. Regards, -- Nicolas Goaziou
Re: [O] agenda and todo list
Sorry for this email that I just sent. I understood too late that it was
only a problem of rights on my Dropbox folder, created by the Dropbox
installation.
Thanks Ken, I apologize !
Best,
Jo.
Le lun. 5 nov. 2018 à 21:40, Joseph Vidal-Rosset <
joseph.vidal.ros...@gmail.com> a écrit :
> Hello everybody,
>
> I'm trying to configure a todo list and I would be happy to succeed in
> getting this todo list in a todo.org file in my Dropbox/Orgzly/ but, I
> do not understand why it does not work with my setup:
>
> ;;file to save todo items
> (setq org-agenda-files (quote ("/home/joseph/Dropbox/Orgzly/todo.org")))
>
> Thetodolist persistsinbeingin myhomeonly
> i.e. /home/joseph/ .
>
> Your help with agenda and todo list would be very welcome.
>
> Best wishes
>
>
> --
> Joseph
>
Re: [O] agenda and todo list
Hi Joseph,
The `org-agenda-files` variables tells Org which files (or folders) to use
to build your Agenda. It doesn't write anything or save anything to disk.
Why not just move the todo.org file from /home/joseph to the Orgzly folder,
and work with it there?
-k.
On Mon, Nov 5, 2018 at 12:41 PM Joseph Vidal-Rosset <
joseph.vidal.ros...@gmail.com> wrote:
> Hello everybody,
>
> I'm trying to configure a todo list and I would be happy to succeed in
> getting this todo list in a todo.org file in my Dropbox/Orgzly/ but, I
> do not understand why it does not work with my setup:
>
> ;;file to save todo items
> (setq org-agenda-files (quote ("/home/joseph/Dropbox/Orgzly/todo.org")))
>
> Thetodolist persistsinbeingin myhomeonly
> i.e. /home/joseph/ .
>
> Your help with agenda and todo list would be very welcome.
>
> Best wishes
>
>
> --
> Joseph
>
>
[O] agenda and todo list
Hello everybody,
I'm trying to configure a todo list and I would be happy to succeed in
getting this todo list in a todo.org file in my Dropbox/Orgzly/ but, I
do not understand why it does not work with my setup:
;;file to save todo items
(setq org-agenda-files (quote ("/home/joseph/Dropbox/Orgzly/todo.org")))
Thetodolist persistsinbeingin myhomeonly
i.e. /home/joseph/ .
Your help with agenda and todo list would be very welcome.
Best wishes
--
Joseph
[O] Bug Tracker?
Hi Org List, Is there some sort of official bug tracker for Org? Or is it just emails to this list? I'm asking because I have a simple reproducible bug that has been around for a few months now, and I'm wondering if I didn't submit the bug in the right place/form/way/etc. I'm pretty sure it was submitted correctly (via org-submit-bug-report). Perhaps it is just a low priority and I didn't include a patch. In which case is the bug lost from our communal memory, or is there at least a place where it is properly filed as "open"? Thanks, -k.
Re: [O] typo, sp at C++ Source Code Blocks in Org Mode
Aloha Van L, Worg is maintained by the community. You can find information on how to make these changes yourself: https://orgmode.org/worg/worg-git.html Thanks for your interest in Org mode and Worg. All the best, Tom
[O] [PATCH] org-habit: allow overriding org-scheduled-past-days and always including time of day
I guess I'm supposed to add the [PATCH] tag to the subject line? So this email is just to do that. Sorry if I've missed some instructions about this... On Mon, 5 Nov 2018, at 00:31, John Lee wrote: > Hi > > Here's a couple of patches that add new org-habit variables. I hope the > variable documentation describes them sufficiently: if not I need to > change the docs so if you review these patches please read the patch > before the rest of this email so that you're not "cheating"! > > > Does the idea behind each of these seem appropriate to people? They > work for me of course, and behaviour is unchanged unless you set non- > default values for the new variables -- but I know people have different > workflows. > > My own workflow around this is similar to GTD, so I'm using SCHEDULED as > basically a way to get TODO items to show up after the scheduled date, > not to show up in the calendar except as a reminder that I have new > TODOs. For that reason I set org-scheduled-past-days to a low value (3 > right now). I also set org-agenda-todo-ignore-scheduled to 'future and > org-agenda-tags-todo-honor-ignore-options to t (not directly relevant > here except as context). For habits that causes habits not to show up > sometimes because of the short org-scheduled-past-days, which isn't > appropriate for my habits: if I say .+5d, I still want to see the habit > there if it's due, even if it's been 4 days since the last done date > (which is more than the 3 days of org-scheduled-past-days). This > motivates `org-habit-scheduled-past-days'. > > Similarly, since I want to do some of my habits at a particular time of > day, org-agenda's omitting of the time of day from the scheduled > timestamp if this is a "repeat" (i.e. I missed doing the habit) is > unhelpful for habits, because now I have to scan though a long-ish list > of habits (5 or 10 right now!) and think "is now the right time, should > I have done that already?" for every habit in the list, rather than just > eyeballing it to see which ones are around now in time. This motivates > `org-habit-always-show-time'. > > I have not yet submitted the FSF copyright assignment form but am > prepared to do so. > > > From 7bcf7b70b201af7a3d3cbbcf6a95511944370627 Mon Sep 17 00:00:00 2001 > From: John Lee > Date: Sun, 4 Nov 2018 23:11:17 + > Subject: [PATCH 1/2] org-habit: Add org-habit-scheduled-past-days > > * lisp/org-habit.el: Add new variable `org-habit-scheduled-past-days' > to allow overriding `org-scheduled-past-days' for habits > > * lisp/org-agenda.el (org-agenda-get-scheduled): override > `org-scheduled-past-days' for habits if > `org-habit-scheduled-past-days` is not nil > --- > lisp/org-agenda.el | 5 - > lisp/org-habit.el | 11 +++ > 2 files changed, 15 insertions(+), 1 deletion(-) > > diff --git a/lisp/org-agenda.el b/lisp/org-agenda.el > index 180a0612c..e2bd5cc2d 100644 > --- a/lisp/org-agenda.el > +++ b/lisp/org-agenda.el > @@ -6196,7 +6196,10 @@ scheduled items with an hour specification like > [h]h:mm." > habitp > (bound-and-true-p org-habit-show-all-today)) > (when (or (and (> ddays 0) (< diff ddays)) > - (> diff org-scheduled-past-days) > + (> diff (if habitp > + (or org-habit-scheduled-past-days > + org-scheduled-past-days) > + org-scheduled-past-days)) > (> schedule current) > (and (/= current schedule) > (/= current today) > diff --git a/lisp/org-habit.el b/lisp/org-habit.el > index 375714e35..b8415bdde 100644 > --- a/lisp/org-habit.el > +++ b/lisp/org-habit.el > @@ -89,6 +89,17 @@ It will be green even if it was done after the deadline." >:group 'org-habit >:type 'boolean) > > +(defcustom org-habit-scheduled-past-days nil > + "Non-nil means the value of this variable will be used instead > +of org-scheduled-past-days, for habits only. > +Setting this to say 1 is a way to make habits always show up > +as a reminder, even if you set org-scheduled-past-days to a small > +value because you regard SCHEDULED items as a way of 'turning on' > +TODO items on a particular date, rather than as a means of > +creating calendar-based reminders." > + :group 'org-habit > + :type 'integer) > + > (defface org-habit-clear-face >'background light)) (:background "#8270f9")) > (((background dark)) (:background "blue"))) > -- > 2.17.1 > > From a1d6e3af978237b3f555682a111c2439f17b45b9 Mon Sep 17 00:00:00 2001 > From: John Lee > Date: Sun, 4 Nov 2018 23:17:15 + > Subject: [PATCH 2/2] org-habit: Add org-habit-always-show-time > > * lisp/org-habit.el: Add new variable `org-habit-always-show-time' > to force always showing the time of day > > * lisp/org-agenda.el (org-agenda-get-scheduled): honour >
Re: [O] [BUG][ODT] ODT_STYLES_FILE not read as a list
Thanks, Nicolas!
I'll test on my end when it shows up in ELPA.
Yours,
Christian
Nicolas Goaziou writes:
> Hello,
>
> Christian Moe writes:
>
>> It seems the ODT exporter currently fails to read the ODT_STYLES_FILE
>> option as a list, as in this example from the manual
>> ([[info:org#Applying custom styles]]):
>>
>> #+ODT_STYLES_FILE: ("/path/to/file.ott" ("styles.xml" "image/hdr.png"))
>>
>> This is needed if you want a complex style with e.g. an image in the
>> header.
>>
>> Exporting this causes an "Invalid specification of styles.xml file"
>> error on my recent ELPA version. The problem seems to be that the option
>> is treated as a string and never tested to see if it contains a list.
>>
>> To reproduce the problem, place the attached documents
>> odt-styles-test.org and odt-test-styles.odt in the same directory, then
>> export odt-styles-test.org to ODT. The result should have a unicorn in
>> the letterhead.
>>
>> The below quick-and-dirty patch seems to fix it, but I'm sure there's a
>> better approach.
>
> Thank you. I applied your patch with an additional check: the value should
> be enclosed within round brackets.
>
> Regards,
[O] typo, sp at C++ Source Code Blocks in Org Mode
Hello, At the following page: https://orgmode.org/worg/org-contrib/babel/languages/ob-doc-C.html // CC+ should be C++ :main can be set to "no" to inhibit wrapping of the code block in a main function call. :includes (C & CC+ only) accepts either a single string name, or a list of names of files to #include in the execution of the code block. // Spelling should be ‘explicitly' C++ needs to explicitely include either stdio.h or
[O] Bug: org-back-to-heading with inline tasks above point [9.1.14 (9.1.14-3-geb9955a-elpaplus @ /home/yantar92/.emacs.d/elpa/org-plus-contrib-20180924/)]
Consider calling =org-back-to-heading= for the following org entry: #+begin_src org * Sample entry Some text. *** TODO Inline task *** END Some more text. ->(point)<- Yet another piece of text. #+end_src The expected behaviour is that the point moves to the first line of the entry. However, the point moves to the end of the inline task. Indeed, the wrong behaviour is because =outline-regexp= variable is set to ="\\*+ "=, which includes inline tasks. Best, Ihor Emacs : GNU Emacs 26.1 (build 1, x86_64-pc-linux-gnu, X toolkit) of 2018-10-29 Package: Org mode version 9.1.14 (9.1.14-3-geb9955a-elpaplus @ /home/yantar92/.emacs.d/elpa/org-plus-contrib-20180924/) signature.asc Description: PGP signature
