From: Christian Moe <mail@christianmoe.com>
To: emacs-orgmode@gnu.org
Cc: Ihor Radchenko <yantar92@posteo.net>, Sam Crawford <sam@crawf.uk>
Subject: Re: [POLL] ob-R, ob-julia: Should we force-disable ess-ask-for-ess-directory? (was: [BUG] Relative filenames for graphics output in ob-R.el [9.8-pre (release_9.7.4-80-g7fa169)])
Date: Fri, 28 Jun 2024 15:46:07 +0200 [thread overview]
Message-ID: <871q4hyycg.fsf@christianmoe.com> (raw)
In-Reply-To: <m2ed8h9quu.fsf@adamkovic.org>
Rudolf Adamkovič writes:
> Ihor Radchenko <yantar92@posteo.net> writes:
>
>> I'd like to hear from ob-R/ob-julia users whether the current behavior
>> is something they rely on. If not, I'd prefer to follow the conventions
>> we introduce in the manual and suppress the ESS's directory prompt.
>
> +1 from me; I have always found that ESS prompt annoying.
>
> Rudy
+1; same, and I (rightly or wrongly) never rely on it for anything
Christian
next prev parent reply other threads:[~2024-06-28 13:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 10:57 [BUG] Relative filenames for graphics output in ob-R.el [9.8-pre (release_9.7.4-80-g7fa169)] Sam Crawford
2024-06-26 13:23 ` Ihor Radchenko
[not found] ` <Eol9qrqro63gxtIvCHknY775AV2QB4sVptOEZY__3tyWRRgw7GkCfbxqahcbQoVgNoQeqJzzXs5fHS-7ocn3OqTE0hJSwW9HCmWF4lt6N6g=@crawf.uk>
2024-06-27 9:41 ` [POLL] ob-R, ob-julia: Should we force-disable ess-ask-for-ess-directory? (was: [BUG] Relative filenames for graphics output in ob-R.el [9.8-pre (release_9.7.4-80-g7fa169)]) Ihor Radchenko
2024-06-28 12:47 ` Rudolf Adamkovič
2024-06-28 13:46 ` Christian Moe [this message]
2024-06-28 15:09 ` [POLL] ob-R, ob-julia: Should we force-disable ess-ask-for-ess-directory? Suhail Singh
2024-08-06 8:43 ` [POLL] ob-R, ob-julia: Should we force-disable ess-ask-for-ess-directory? (was: [BUG] Relative filenames for graphics output in ob-R.el [9.8-pre (release_9.7.4-80-g7fa169)]) 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=871q4hyycg.fsf@christianmoe.com \
--to=mail@christianmoe.com \
--cc=emacs-orgmode@gnu.org \
--cc=sam@crawf.uk \
--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).