From: Maxim Nikulin <firstname.lastname@example.org>
Subject: Re: [PATCH] org-agenda.el: Avoid dependency on subr-x
Date: Fri, 6 Aug 2021 00:04:59 +0700 [thread overview]
Message-ID: <email@example.com> (raw)
On 05/08/2021 04:41, Вячеслав Гришин wrote:
> Now I don't know if I need to do something extra, because the
> problem arose because of my mistake.
Vyacheslav, you do not need to react to my patch, it is for Org
maintainers. There is neither continuous integration server nor ready to
use configuration (e.g. a set of docker containers) to verify commits in
clean environment. As a result some files may have minor issues that are
unnoticeable by most of users. However it is better to fix
inconsistencies like missed `require', etc.
> When I removed the second version of Org and the extra code from .emacs,
> everything worked. I don't know how to explain it, because I'm just
> starting to learn emacs and lisp
Notice that you can have more than one org mode version installed. E.g.
in Debian and Ubuntu in addition to the version bundled with Emacs, it
is possible to install elpa-org deb package. The version however is
anyway noticeably older than current stable Org release, so people often
use various package managers for Emacs.
The problem you have met is not uncommon, example of usual response:
Unfortunately symptoms are usually quite obscure, they may reveal
another issue. I do not know if it is possible to implement a trap to
explicitly notify user that parts of org are loaded from different
There are may be some pitfalls on the way to have newer org version:
- You should not require any org modules before `load-path' is adjusted.
- Do not forget to recompile after update of sources. It seems, Emacs do
not have means to detect stale .elc file similar to e.g. Python.
- Attempt to try alternative version without modification of init.el may
result in unexpected result. Usually "-Q" or at least "-q" option is
required to suppress initialization. "-L" option is processed after
init.el. So "emacs -L ~/src/org-mode/lisp" can easily result in mixed
install. E.g. "emacs -Q -L ~/src/org-mode/lisp -l ~/.emacs.d/init.el"
mostly work but there are some edge cases since it is not full
equivalent of real initialization. There is no way to specify custom
init file through command line option, it is necessary to create a part
of parallel universe and pass it as --user option argument, HOME or
XDG_CONFIG_HOME (for latest emacs version) environment:
Do not be afraid by such complications too much. ELPA package is the
recommended way to have latest stable version:
Alternatively ensure that (add-to-list 'load-path "~/src/org-mode/lisp")
is early enough in your init.el.
next prev parent reply other threads:[~2021-08-05 17:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-30 15:24 Bug: org-agenda-highlight-todo: Symbol’s function definition is void: string-empty-p [9.4.6 (9.4.6-11-g1ee52c-elpa @ /home/vmg/.emacs.d/elpa/org-20210726/)] Вячеслав Гришин
2021-08-04 1:41 ` Tim Cross
2021-08-04 21:36 ` Вячеслав Гришин
2021-08-04 15:20 ` [PATCH] org-agenda.el: Avoid dependency on subr-x Maxim Nikulin
2021-08-04 21:41 ` Вячеслав Гришин
2021-08-05 17:04 ` Maxim Nikulin [this message]
2021-08-04 22:11 ` Tim Cross
2021-08-05 11:55 ` Maxim Nikulin
2021-08-05 12:59 ` Timothy
2021-08-06 17:10 ` Maxim Nikulin
2021-08-06 20:30 ` Timothy
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).