Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Samuel Loury konubi...@gmail.com writes:
Please find attached the merged patch, as asked for.
Applied, thank you.
Therefore, the hooks associated to the insertion of a heading will be
triggered. Since those hooks may cause the creation of
Samuel Loury konubi...@gmail.com writes:
Please find attached the merged patch, as asked for.
Applied, thank you.
Therefore, the hooks associated to the insertion of a heading will be
triggered. Since those hooks may cause the creation of some
metadata. `org-end-of-meta-data' is used
Hi,
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Samuel Loury konubi...@gmail.com writes:
I suggest to provide a helper that would move point after the meta-data
part to avoid code duplication. Something like (no surprise :-)):
(defun org-goto-after-metadata-part ()
(when
Samuel Loury konubi...@gmail.com writes:
I suggest to provide a helper that would move point after the meta-data
part to avoid code duplication. Something like (no surprise :-)):
(defun org-goto-after-metadata-part ()
(when (org-looking-at-p org-planning-line-re) (forward-line))
(when
Thank you for taking into account this problem.
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Samuel Loury konubi...@gmail.com writes:
I just realized that when creating a new entry in my org-diary
(`org-agenda-add-entry-to-org-agenda-diary-file'), the entry looks like:
** test
Hello,
Samuel Loury konubi...@gmail.com writes:
I just realized that when creating a new entry in my org-diary
(`org-agenda-add-entry-to-org-agenda-diary-file'), the entry looks like:
** test
2015-01-30 Fri
:PROPERTIES:
:CREATED: [2015-01-30 Fri 08:00]
:END:
The property is
Samuel Loury konubi...@gmail.com writes:
Nicolas Goaziou m...@nicolasgoaziou.fr writes:
Samuel Loury konubi...@gmail.com writes:
I just realized that when creating a new entry in my org-diary
(`org-agenda-add-entry-to-org-agenda-diary-file'), the entry looks like:
** test
2015-01-30
