From: akater <email@example.com> To: Bastien <firstname.lastname@example.org> Cc: email@example.com Subject: Re: [PATCH] Add support for trace and error output streams in Common Lisp Date: Tue, 07 Jul 2020 12:03:54 +0000 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> [-- Attachment #1: Type: text/plain, Size: 1461 bytes --] So, the overall plan that I suggest is as follows: - Merge the patch(es) I sent. Whether to merge documntation patch or not, is left for you to decide. The text does not lie to users but it hints at a feature that is not available yet. These patches will not break anything for anyone unless I get hit by the bus and SLIME gets to 2.28 without my submission merged into it. - Once my pending submission to SLIME (and SLY, if neccessary) is accepted, - update the documentation if it has not been done at the previous step - move utilitiy function `org-babel-nsubstitute-multiple' to a more appropriate file - move `require' forms (to the top of ob-lisp.el, or wherever `org-babel-nsubstitute-multiple' went) - Once SLIME 2.25--2.27 (the one that lacks the grab-multiple-outputs feature) becomes unsupported, - delete function `org-babel-execute:lisp--legacy' - rename `org-babel-execute:lisp--multiple-targets-support' to `org-babel-execute:lisp' - remove defalias for `org-babel-execute:lisp' By the way, I was wrong about something: newline variable in my patch does not refer to newlines emitted by Lisp, it's newline that Org inserts into Org buffer. I generally try to make it easy to allow consistent usage of non-unix newlines in users' files. If you are certain that trying to support this in Emacs is not worth it, I'll gladly stop doing it. [-- Attachment #2: signature.asc --] [-- Type: application/pgp-signature, Size: 800 bytes --]
prev parent reply other threads:[~2020-07-07 12:13 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-10 3:32 akater 2020-04-18 13:05 ` akater 2020-06-02 12:03 ` Bastien 2020-07-06 21:58 ` akater 2020-09-04 15:37 ` Bastien 2020-09-05 20:07 ` Tom Gillespie 2020-09-06 5:03 ` Bastien 2020-07-07 12:03 ` akater [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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [PATCH] Add support for trace and error output streams in Common Lisp' \ /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
Code repositories for project(s) associated with this 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).