From: Evgenii Klimov <eugene.dev@lipklim.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: [BUG] [PATCH] Avoid interaction in test ~ob-tangle/detangle-false-positive~
Date: Mon, 17 Jul 2023 12:53:44 +0100 [thread overview]
Message-ID: <87y1jeagcz.fsf@lipklim.org> (raw)
In-Reply-To: <87zg3uzzcw.fsf@localhost>
Ihor Radchenko <yantar92@posteo.net> writes:
> Evgenii Klimov <eugene.dev@lipklim.org> writes:
>
>> Test ~ob-tangle/detangle-false-positive~ asks for confirmation to kill
>> the buffer, connected to testing/examples/babel.org file, that is
>> modified during the couse of the test.
>>
>> Way to reproduce the bug (from projects main dir):
>
> Thanks!
> Waiting for your copyright assignment before applying.
Thanks, responsible person from FSF just returned from vacation.
While it's not applied, may I also ask: I noticed that non-default value
'other-frame of =org-src-window-setup= variable in my init.el leads to
creation of multiple frames during interactive testing.
I understand that testing should be done on ~emacs -Q~ etc, but since
it's an option to quickly test interactively in the current process
during development, would you accept the patch where
=org-src-window-setup= would be set to default value inside the test?
It took me some time to figure it out, so further developers in the
similar situation could benefit from it.
next prev parent reply other threads:[~2023-07-17 12:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-16 12:36 [BUG] [PATCH] Avoid interaction in test ~ob-tangle/detangle-false-positive~ Evgenii Klimov
2023-07-17 9:00 ` Ihor Radchenko
2023-07-17 11:53 ` Evgenii Klimov [this message]
2023-07-17 12:46 ` Ihor Radchenko
2023-07-20 22:11 ` Evgenii Klimov
2023-07-21 7:45 ` Ihor Radchenko
2023-07-21 9:52 ` Bastien Guerry
2023-07-21 9:55 ` Ihor Radchenko
2023-07-21 13:42 ` Evgenii Klimov
2023-07-21 17:03 ` Ihor Radchenko
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=87y1jeagcz.fsf@lipklim.org \
--to=eugene.dev@lipklim.org \
--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).