From: Colin Baxter <m43cap@yandex.com>
To: akater <nuclearspace@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Some whitespace stripped from emacs-lisp value in src blocks making it unreadable in certain cases
Date: Tue, 10 Sep 2019 16:43:36 +0100 [thread overview]
Message-ID: <87pnk8w40n.fsf@yandex.com> (raw)
In-Reply-To: <875zm1c6ld.fsf@gmail.com> (akater's message of "Tue, 10 Sep 2019 00:55:58 +0000")
[-- Attachment #1: Type: text/plain, Size: 2249 bytes --]
>>>>> akater <nuclearspace@gmail.com> writes:
> Consider a lisp form that, when evaluated, produces another
> form. I'm used to org printing the resulting form nicely, in lisp
> blocks. However, this is not the case for emacs-lisp src
> blocks. An example:
> 1. The way it should be (and is now the case) with lisp, namely
> sbcl:
> #+begin_src lisp :results value verbatim :wrap example lisp
> (macroexpand '(defun test (a b &optional c) "doc" nil)) #+end_src
> #+RESULTS:
> #+begin_example lisp (PROGN (EVAL-WHEN (:COMPILE-TOPLEVEL)
> (SB-C:%COMPILER-DEFUN 'TEST T NIL NIL)) (SB-IMPL::%DEFUN 'TEST
> (SB-INT:NAMED-LAMBDA TEST (A B &OPTIONAL C) "doc" (BLOCK TEST
> NIL)))) T #+end_example
> 2. The way it is now with emacs-lisp and a src block header that
> is otherwise identical:
> #+begin_src emacs-lisp :results value verbatim :wrap example
> emacs-lisp (macroexpand '(use-package outline :ensure nil :bind
> (:map outline-mode-map ("<kp-home>" . (lambda nil (interactive)
> (outline-up-heading 1)))))) #+end_src
> #+RESULTS:
> #+begin_example emacs-lisp (progn (use-package-ensure-elpa
> 'outline '(nil) 'nil) (defvar use-package--warning157 #'(lambda
> (keyword err) (let ((msg (format "%s/%s: %s" 'outline keyword
> (error-message-string err)))) (display-warning 'use-package msg
> :error)))) (condition-case-unless-debug err (progn (if (not
> (require 'outline nil t)) (display-warning 'use-package (format
> "Cannot load %s" 'outline) :error)) (bind-keys :package outline
> :map outline-mode-map ("<kp-home>" lambda nil (interactive)
> (outline-up-heading 1)))) (error (funcall use-package--warning157
> :catch err)))) #+end_example
> Is there a remedy? This probably better be fixed but it could be
> due to me using bleeding-edge Emacs 27 master (2019-09-10) & Org
> from melpa (2019-09-09). If you don't have proper output
> formatting with other versions in use, please report.
I get the same formatting error as you and I am using emacs-26.3 with
org-mode version 9.2.6.
Best wishes,
--
Colin Baxter
www.Colin-Baxter.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 472 bytes --]
next prev parent reply other threads:[~2019-09-10 15:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-10 0:55 Some whitespace stripped from emacs-lisp value in src blocks making it unreadable in certain cases akater
2019-09-10 15:43 ` Colin Baxter [this message]
2019-09-10 17:29 ` Berry, Charles
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=87pnk8w40n.fsf@yandex.com \
--to=m43cap@yandex.com \
--cc=emacs-orgmode@gnu.org \
--cc=nuclearspace@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).