emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Jack Kamm <jackkamm@gmail.com>
Cc: emacs-orgmode@gnu.org, jeremiejuste@gmail.com
Subject: Re: [PATCH] ob-comint,R,python: Options for more robust non-async session output
Date: Sat, 19 Oct 2024 07:20:10 +0000	[thread overview]
Message-ID: <87v7xowod1.fsf@localhost> (raw)
In-Reply-To: <87h6993y6q.fsf@gmail.com>

Jack Kamm <jackkamm@gmail.com> writes:

> This is related to my recent thread,
>
> https://list.orgmode.org/87wmi9etku.fsf@gmail.com/T/#m93bd964243638ee358d4375c9ed4f40e066238d4
>
> which addresses problems with prompt filtering of R and python async evaluation in Org 9.7.
>
> Here, I address the non-async case.
>
> First, I introduce options to `org-babel-comint-with-output' to skip the
> cleanup of prompts and dangling text.  This allows individual Babel
> languages to handle these tasks in a more robust, language-specific
> manner, e.g. by sourcing temp files or relying on functionality from
> external libraries like python.el or ESS.

I have no objections to the idea.
Just one comment on the patch.

> -	 ;; got located, and save dangling text
> -	 (goto-char (process-mark (get-buffer-process (current-buffer))))
> -	 (let ((start (point))
> -	       (end (point-max)))
> -	   (setq dangling-text (buffer-substring start end))
> -	   (delete-region start end))
> +         (unless ,no-save-dangle
> +	   ;; got located, and save dangling text
> +	   (goto-char (process-mark (get-buffer-process (current-buffer))))
> +	   (let ((start (point))
> +	         (end (point-max)))
> +	     (setq dangling-text (buffer-substring start end))
> +	     (delete-region start end)))
>  	 ;; pass FULL-BODY to process
>  	 ,@body

Previously, the point was always at process-mark when BODY is
called. Now, it may not be the case. It may cause problems.

-- 
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>


  reply	other threads:[~2024-10-19  7:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-18 21:20 [PATCH] ob-comint,R,python: Options for more robust non-async session output Jack Kamm
2024-10-19  7:20 ` Ihor Radchenko [this message]
2024-10-21  5:45   ` Jack Kamm
2024-10-23 17:24     ` Ihor Radchenko
2024-11-03 18:05       ` Jack Kamm
2024-11-10 15:22         ` Ihor Radchenko
2024-11-13  4:09           ` Jack Kamm

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=87v7xowod1.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=jackkamm@gmail.com \
    --cc=jeremiejuste@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).