From: "Richard H. Stanton" <rhstanton@berkeley.edu>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: orgmode <emacs-orgmode@gnu.org>
Subject: Re: How to stop results being hidden when using ":results drawer"?
Date: Thu, 12 May 2022 10:04:08 -0700 [thread overview]
Message-ID: <9D0BF38C-01A1-4359-B529-7F6EAFC01D47@berkeley.edu> (raw)
In-Reply-To: <877d6rhxcf.fsf@localhost>
>> I’m creating documents where I run Python code blocks that create LaTeX mathematical output that I want to be able to export to either LaTeX/PDF or HTML.
>>
>> Using :wrap in the header works fine, except that LaTeX complains about the unknown environment “results” (it still compiles the file to PDF fine).
>>
>> Using :wrap export latex works fine for LaTeX export, but I can’t get HTML that way.
>>
>> The recommended method seems to be to use :results drawer. This works fine from an export perspective to both LaTeX/PDF and to HTML. However, it has one significant drawback when I’m actually creating the document: the results drawer starts out hidden and to see what’s there I have to click on it. This makes debugging the code in the first place a lot less convenient.
>>
>> Is there a way to use :results drawer and have the results NOT hidden by default?
>
> I think that you are experiencing the same issue with
> https://list.orgmode.org/80k0ar1lml.fsf@felesatra.moe/T/#u
>
> Does it help when you run
> M-: (setq org-fold-core-first-unfold-functionsp nil) <RET>
> before running the code block?
>
> Best,
> Ihor
Thanks for the suggestion, Ihor, but like John, this doesn’t solve my problem. For now, I'm using :wrap flushleft, which allows exporting to both LaTeX and HTML without errors, allows xenops to preview my LaTeX output, and doesn’t have any hiding issues. I’ve also reported the issue to the author of xenops.
prev parent reply other threads:[~2022-05-12 17:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 16:52 How to stop results being hidden when using ":results drawer"? Richard Stanton
2022-05-11 17:51 ` Richard Stanton
2022-05-11 20:14 ` Richard Stanton
2022-05-11 20:18 ` John Kitchin
2022-05-12 10:14 ` Ihor Radchenko
2022-05-12 13:07 ` John Kitchin
2022-05-13 12:11 ` Ihor Radchenko
2022-05-13 12:46 ` John Kitchin
2022-05-13 13:35 ` [PATCH] " Ihor Radchenko
2022-05-13 15:39 ` Eric S Fraga
2022-05-13 16:19 ` Ihor Radchenko
2022-07-31 2:21 ` Ihor Radchenko
2022-05-12 17:04 ` Richard H. Stanton [this message]
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=9D0BF38C-01A1-4359-B529-7F6EAFC01D47@berkeley.edu \
--to=rhstanton@berkeley.edu \
--cc=emacs-orgmode@gnu.org \
--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).