From: Robert Pluim <rpluim@gmail.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: Angel de Vicente <angel.vicente.garrido@gmail.com>,
emacs-orgmode@gnu.org
Subject: Re: Timestamp with repeater interval AND END DATE?
Date: Fri, 10 Jun 2022 16:24:28 +0200 [thread overview]
Message-ID: <87r13w1tr7.fsf@gmail.com> (raw)
In-Reply-To: <87r13wr7x1.fsf@localhost> (Ihor Radchenko's message of "Fri, 10 Jun 2022 20:59:22 +0800")
>>>>> On Fri, 10 Jun 2022 20:59:22 +0800, Ihor Radchenko <yantar92@gmail.com> said:
Ihor> Robert Pluim <rpluim@gmail.com> writes:
>> I can send a patch against the org-mode repository main branch, or fix
>> it directly in the emacs repo. What's the preferred workflow for this
>> kind of change?
Ihor> Just submit a patch here. Against the Org mode repository.
Ihor> Org mode development happens in Org mode repository and in this mailing
Ihor> list, not in Emacs repo.
Ok. I will, or rather I would, but Iʼm obviously doing something wrong
when building org:
rltb:~/repos/org-mode (main)> cat local.mk
EMACS := /home/rpluim/repos/emacs-28/src/emacs
rltb:~/repos/org-mode (main)> git pull
Already up to date.
rltb:~/repos/org-mode (main)> git status
On branch main
Your branch is up to date with 'origin/main'.
nothing to commit, working tree clean
rltb:~/repos/org-mode (main)> make doc
make -C doc info
make[1]: Entering directory '/home/rpluim/repos/org-mode/doc'
/home/rpluim/repos/emacs-28/src/emacs -Q -batch --eval '(setq vc-handled-backends nil org-startup-folded nil org-element-cache-persistent nil)' \
--eval '(add-to-list `load-path "../lisp")' \
--eval '(load "../mk/org-fixup.el")' \
--eval '(org-make-manual)'
Loading /home/rpluim/repos/org-mode/mk/org-fixup.el (source)...
Debugger entered--Lisp error: (wrong-type-argument listp "Packages that conflict with Org mode")
org-element-secondary-p(#("Conflicts" 0 9 (:parent (headline (:raw-value "Packages that conflict with Org mode" :begin 739020 :end 744524 :pre-blank 0 :contents-begin 739061 :contents-end 744523 :robust-begin 739148 :robust-end 744521 :level 3 :priority nil :tags nil :todo-keyword nil :todo-type nil :post-blank 1 :footnote-section-p nil :archivedp nil :commentedp nil :post-affiliated 739020 :DESCRIPTION "Packages that lead to conflicts." :ALT_TITLE "Conflicts" :title "Packages that conflict with Org mode" :parent (headline (:raw-value "Interaction with Other Packages" :begin 735540 :end 744524 :pre-blank 0 :contents-begin 735575 :contents-end 744523 :robust-begin 735658
:robust-end 744521 :level 2 :priority nil :tags nil :todo-keyword nil :todo-type nil :post-blank 1 :footnote-section-p nil :archivedp nil :commentedp nil :post-affiliated 735540 :DESCRIPTION "With other Emacs packages." :ALT_TITLE "Interaction" :title "Interaction with Other Packages" :parent ... ...) (section ... ... ...) (headline ... ...) #4) ...) (section (:begin 739061 :end 744524 :contents-begin 739061 :contents-end 744523 :robust-begin 739061
:robust-end 744521 :post-blank 1 :post-affiliated 739061 :mode section :granularity nil :parent #4) (keyword (:key "CINDEX" :value "shift-selection" :begin 739150 :end 739176 :post-blank 0 :post-affiliated 739150 :mode nil :granularity nil :parent #7)) (keyword (:key "VINDEX" :value "org-support-shift-select" :begin 739176 :end 739211 :post-blank 0 :post-affiliated 739176 :mode nil :granularity nil :parent #7)) (paragraph (:begin 739211 :end 739889 :contents-begin 739211 :contents-end 739888 :post-blank 1 :post-affiliated 739211 :mode nil :granularity nil :parent #7) #("In Emacs, shift-selection combines motions o..." 0 155 ...) (export-snippet ...) #("S-<cursor>" 0 10 ...) (export-snippet ...) #("commands to change timestamps,\nTODO keywords..." 0 93 ...) (export-snippet ...) #("S-<cursor>" 0 10 ...) (export-snippet ...) #("commands outside of specific contexts do not..." 0 82 ...) (code ...) #
Ihor> See https://orgmode.org/worg/org-contribute.html
Ihor> Also, if you think that any of the extra diary functions from Org can be
Ihor> useful for Emacs, you can propose to include them directly into
Ihor> diary-lib.el via M-x submit-emacs-patch (Emacs >=28) or
Ihor> M-x report-emacs-bug. The latter is also for patches, unlike the command
Ihor> name suggests.
Iʼll put that on my list (Iʼm guessing you'd want compatibility shims
in org-mode if I did that).
Robert
--
next prev parent reply other threads:[~2022-06-10 14:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-31 13:46 Timestamp with repeater interval AND END DATE? Angel de Vicente
2022-05-31 14:03 ` Eric S Fraga
2022-05-31 14:36 ` Angel de Vicente
2022-06-10 8:44 ` Robert Pluim
2022-06-10 11:27 ` Angel de Vicente
2022-06-10 12:45 ` Robert Pluim
2022-06-10 12:59 ` Ihor Radchenko
2022-06-10 14:24 ` Robert Pluim [this message]
2022-06-10 15:03 ` Ihor Radchenko
2022-06-10 15:59 ` Robert Pluim
2022-06-11 4:51 ` Ihor Radchenko
2022-06-10 14:37 ` Ambiguity in commit message conventions for org Robert Pluim
2022-06-10 15:11 ` Ihor Radchenko
2022-06-10 16:02 ` Robert Pluim
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=87r13w1tr7.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=angel.vicente.garrido@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@gmail.com \
/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).