all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Daniel Colascione <dancol@dancol.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Emacs development discussions <emacs-devel@gnu.org>
Subject: Re: ielm changes: display standard-output in buffer
Date: Thu, 26 Sep 2013 20:37:28 -0700	[thread overview]
Message-ID: <5244FD78.5010401@dancol.org> (raw)
In-Reply-To: <jwvpprvxqdh.fsf-monnier+emacs@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 934 bytes --]

On 9/26/13 1:49 PM, Stefan Monnier wrote:
>> How does this change look?
> 
> Looks OK, but see comments/questions.

Thanks for taking a look.

> 
>> +;;; -*- lexical-binding: t -*-
>>  ;;; ielm.el --- interaction mode for Emacs Lisp
> 
> Please just put -*- lexical-binding: t -*- at the end of the first line

Sure.

>> +(defun ielm-standard-output-impl (char)
> 
> I don't really understand the standard-output part of your patch.
> Could you provide a simple example where it makes a difference (and put
> it in some comment somewhere in the code)?

Sure: it's a new feature: the basic idea is that if a form being
evaluated through ielm writes to standard-output (say, using princ),
that output appears in the ielm buffer, making it work more like a
normal command line. I looked into doing the same thing for message
output, but I couldn't get after-change-functions in *Messages* to run
reliably.



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2013-09-27  3:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-26 18:13 ielm changes: display standard-output in buffer Daniel Colascione
2013-09-26 20:49 ` Stefan Monnier
2013-09-27  3:37   ` Daniel Colascione [this message]
2013-09-28  0:46 ` Stefan Monnier
2013-10-03  6:23   ` Daniel Colascione
2013-10-03 13:50     ` Stefan Monnier
2013-10-05  1:42       ` Daniel Colascione
2013-10-05 13:45         ` Stefan Monnier

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5244FD78.5010401@dancol.org \
    --to=dancol@dancol.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.