From: Ihor Radchenko <yantar92@posteo.net>
To: Jeremie Juste <jeremiejuste@gmail.com>
Cc: "Ihor Radchenko" <yantar92@gmail.com>,
"Rudolf Adamkovič" <salutis@me.com>,
emacs-orgmode@gnu.org
Subject: Re: [BUG] Incorrect background color [9.5.4 (release_9.5.4-3-g6dc785 @ /Users/salutis/src/emacs/nextstep/Emacs.app/Contents/Resources/lisp/org/)]
Date: Sun, 13 Nov 2022 04:37:54 +0000 [thread overview]
Message-ID: <87cz9r8o65.fsf@localhost> (raw)
In-Reply-To: <87leogzd7a.fsf@gmail.com>
Jeremie Juste <jeremiejuste@gmail.com> writes:
> >> WORG page is not accurate here. The truth is that ob-R.el does not provide
> >> any defaults for header args. Instead, R defaults are used. I suspect
> >> that defaults for background color changed in R since the WORG page has
> >> been written.
> >
> > Jeremie, could you please take a look?
>
> Yes. Thanks for confirming the issue. I confirm that the white backgroud is the default and is R default.
> I could not trace back any recent change in R. So I suspect white was always the default.
> But I could well be wrong here.
> ...
> Thanks also for updating the WORG page.
Thanks for the confirmation!
Also, it was Bastien who updated the page.
Fixed.
https://git.sr.ht/~bzg/worg/commit/5c24f6e33f20505ee161cd2c5fc93e39891d08ad
> Note also that R parameters always takes precedence on the org-mode ones. As in the example below.
>
> #+BEGIN_SRC R :results graphics file :file test.svg :outputs both bg red
> par(bg="blue")
> plot(1:10, type = "n")
> #+end_src
>
> In opinion the actual org parameters are the right ones. But I'm open to suggestions.
I do not think that we can do anything about it and I do not think that
we do anything wrong.
Org can set options provided in header args as defaults, but the actual
code can do anything, including changing those defaults.
--
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>
next prev parent reply other threads:[~2022-11-13 4:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 18:56 [BUG] Incorrect background color [9.5.4 (release_9.5.4-3-g6dc785 @ /Users/salutis/src/emacs/nextstep/Emacs.app/Contents/Resources/lisp/org/)] Rudolf Adamkovič
2022-07-02 4:44 ` Ihor Radchenko
2022-10-16 10:44 ` Ihor Radchenko
2022-11-12 10:20 ` Jeremie Juste
2022-11-13 4:37 ` Ihor Radchenko [this message]
2022-11-12 10:14 ` Jeremie Juste
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=87cz9r8o65.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=jeremiejuste@gmail.com \
--cc=salutis@me.com \
--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).