unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Peter Seibel <peter@javamonkey.com>
Cc: bug-gnu-emacs@gnu.org
Subject: Re: lisp-interaction-mode binding RET
Date: 05 Aug 2003 21:19:53 -0700	[thread overview]
Message-ID: <m3r83zto2e.fsf@javamonkey.com> (raw)
In-Reply-To: <E19kEcS-0001bf-GR@fencepost.gnu.org>

Richard Stallman <rms@gnu.org> writes:

> Can you suggest another key binding to use for last-sexp-toggle-display
> instead of RET?

Dunno. Something I'm not already trying to use for something else like
entering new lines. ;-) I'm not sure I understand the binding for
last-sexp-toggle-display fits into things--it doesn't *seem* to be
part of the major mode (i.e. it's not listed as a binding when I type
C-h m) so I'm not sure what conventions it's supposed to be following.
Maybe ESC RET on the pattern of ESC TAB which the major mode already
uses?

Anyway, I noticed this problem because I was trying to use RET to
enter a new line in the middle of a longish list (like the value of
load-path) that I had just dumped into my *scratch* buffer to see what
the heck it was and was pretty confused at what the heck was going on
since the binding didn't show up in the mode documentation (nor, as it
turns out, in the output of describe-bindings) I eventually figured
out from experiments with C-h k more or less what was going on.

>       (make-list 20 'a)
>       (a a a a a a a a a a a a ...)
> 
>     Now if I put my cursor on the opening parentheses of the list of a's
>     and hit return I get an error:
> 
>       Wrong type argument: integer-or-marker-p, nil
> 
> That bug seems to have been fixed in the latest sources in CVS.

Cool.

>       (make-list 20 'a)
>       Type a bunch of stuff here(a a a a a a a a a a a a ...)
> 
> 
>     Then when I hit RET, l-s-t-d expands the list and wipes out everything
>     back to the original list leaving me with this:
> 
>       (make-list 20 'a)
>       (a a a a a a a a a a a a ...)(a a a a a a a a a a a a a a a a a a a a)
> 
> That also seems to have been fixed.

Likewise, cool.

>     This is all with GNU Emacs 21.3.1 running on Linux.
> 
> Linux alone is not a sufficient platform to run Emacs.  You need the
> whole GNU/Linux system.
>
> We worked for many years to develope the GNU system before Linux was
> even thought of.  If you call the whole system "Linux", you're giving
> its principal developers none of the credit.  Would you please call it
> "GNU/Linux"?

My mistake. Thanks for all your hard work.

-Peter

-- 
Peter Seibel                                      peter@javamonkey.com

         Lisp is the red pill. -- John Fraser, comp.lang.lisp

  reply	other threads:[~2003-08-06  4:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-04 18:23 lisp-interaction-mode binding RET Peter Seibel
2003-08-06  3:05 ` Richard Stallman
2003-08-06  4:19   ` Peter Seibel [this message]
     [not found] <mailman.66.1060024420.29551.bug-gnu-emacs@gnu.org>
2003-08-04 20:12 ` Kevin Rodgers

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.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=m3r83zto2e.fsf@javamonkey.com \
    --to=peter@javamonkey.com \
    --cc=bug-gnu-emacs@gnu.org \
    /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.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).