emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Samuel Wales <samologist@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: batch breaks bugfix
Date: Sun, 18 Jun 2023 16:33:57 -0700	[thread overview]
Message-ID: <CAJcAo8tWMP0sOHXfXjajL3YMK1CbK2gpstQ4G2Mgnyo-i6gzFA@mail.gmail.com> (raw)
In-Reply-To: <CAJcAo8sZNYvichogfU6QFuk66xJuEnaPe7n5xJ9o_nqkcDHA9w@mail.gmail.com>

wondering if it is possible to enable display stuff without actually
dispaying anything.

On 6/18/23, Samuel Wales <samologist@gmail.com> wrote:
> the bug occurs in recent bugfix, but not recent main, so perhaps we
> could say that it is fixed in main but that the fix has not been
> applied to bugfix?  [if only the fix were known.]
>
> does org testing use --batch?
>
> bugfix tests ok.  but idk if that tests agenda.
>
>
> On 6/18/23, Ihor Radchenko <yantar92@posteo.net> wrote:
>> Samuel Wales <samologist@gmail.com> writes:
>>
>>> 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.
>>
>> If you play with visibility, there might be differences. Emacs batch
>> mode disables some display staff and visibility relies upon display
>> working properly.
>>
>> No other ideas.
>>
>> --
>> Ihor Radchenko // yantar92,
>> Org mode contributor,
>> Learn more about Org mode at <https://orgmode.org/>.
>> Support Org development at <https://liberapay.com/org-mode>,
>> or support my work at <https://liberapay.com/yantar92>
>>
>
>
> --
> The Kafka Pandemic
>
> A blog about science, health, human rights, and misopathy:
> https://thekafkapandemic.blogspot.com
>


-- 
The Kafka Pandemic

A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com


  reply	other threads:[~2023-06-18 23:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-18  3:00 batch breaks bugfix Samuel Wales
2023-06-18 10:44 ` Ihor Radchenko
2023-06-18 23:32   ` Samuel Wales
2023-06-18 23:33     ` Samuel Wales [this message]
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=CAJcAo8tWMP0sOHXfXjajL3YMK1CbK2gpstQ4G2Mgnyo-i6gzFA@mail.gmail.com \
    --to=samologist@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@posteo.net \
    /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).