From: Samuel Wales <samologist@gmail.com>
To: emacs-orgmode@gnu.org
Subject: batch breaks bugfix
Date: Sat, 17 Jun 2023 20:00:55 -0700 [thread overview]
Message-ID: <CAJcAo8vv7oREqMUnJj9hOTSafA3cnTc5bNa56vaLX+32E7Ga-w@mail.gmail.com> (raw)
can you think of any differences between bugfix and main
that could result in
1) bugfix not producing certain agenda entries from the org
outline (THE BUG)
2) with no obvious differences between the entries that show
and the entries that do not
3) FROM A BATCH CALL. removing --batch from the emacs call
removes the bug.
i am merely hoping for an a priori idea about what might be
different from bugfix to main so that i don't have to do
what for unrealted reasons i cannot do at this time which is
produce an ecm. 27.1. apologies for bad non-bug-report.
===
(info "(elisp) Startup Summary") says what --batch does
differehtly from interactive. long ago i tried to make
testcase be like normal emacs gui use. loads .emacs, which
batch does not. i have no default library for batch to not
run. i did not do the other stuff --batch does. recently
adding (package-initialize) made no difference.
so idk what --batch is doing or not doing to screw up the
bugfix agenda but not main.
batch maint has sorting differences from main, which i will
presume are expected and fixable.
===
i wouldn't care about this issue but i like running my old
regression script to ensure agenda works ok.
--
The Kafka Pandemic
A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com
next reply other threads:[~2023-06-18 3:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-18 3:00 Samuel Wales [this message]
2023-06-18 10:44 ` batch breaks bugfix Ihor Radchenko
2023-06-18 23:32 ` Samuel Wales
2023-06-18 23:33 ` Samuel Wales
2023-06-19 10:36 ` Ihor Radchenko
2023-06-19 22:09 ` Samuel Wales
2023-07-01 3:03 ` Samuel Wales
2023-07-01 3:37 ` Samuel Wales
2023-07-01 6:08 ` Max Nikulin
2023-07-01 10:30 ` Ihor Radchenko
2023-07-02 0:55 ` Samuel Wales
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=CAJcAo8vv7oREqMUnJj9hOTSafA3cnTc5bNa56vaLX+32E7Ga-w@mail.gmail.com \
--to=samologist@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).