unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Jean Louis <bugs@gnu.support>
To: help-gnu-emacs@gnu.org
Subject: Re: SLIME and SBCL (Common Lisp)
Date: Mon, 28 Jun 2021 09:41:54 +0300	[thread overview]
Message-ID: <YNlvMtyAn94TQF44@protected.localdomain> (raw)
In-Reply-To: <87pmw7g7uo.fsf@zoho.eu>

* Emanuel Berg <moasenwood@zoho.eu> [2021-06-27 02:06]:
> Trying to get SLIME and SBCL Common Lisp up-and-running but my
> old stuff won't wort. It gets stuck on the count-up
> connection phase.

Before few years, SLIME worked just fine. I don't know now, somehow it
breaks connection too often. So I find it easier to disable it and use
M-x run-lisp -- it seem to be so much more stable work. Connection is
not easily broken unless I do kill-emacs by mistake. I don't have
access to all features of SLIME, but hey.

There is certain benefit of programming without helper functions as it
drives memory and thinking better. And I use CLISP implementation that
has a readline, so I run separate vterm or terminal where I can
quickly write any command and get its apropos or quickly jump to the
documentation of a function. SLIME has those features and when I am
not using SLIME I switch to CLISP and readline TAB TAB, documentation
opens for every function.

SBCL does not have a readline.

I also try to minimize libraries and just implement practical
functionality without dependent software.

Yesterday I was supposed to write a general Double Opt-In program in
Common Lisp but I wrote it in Emacs Lisp. I guess I will have to
rewrite it in Common Lisp, then I will do the same in Chicken,
Dr. Racket, Scheme and Perl, then maybe other languages to add.

-- 
Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

In support of Richard M. Stallman
https://stallmansupport.org/



  parent reply	other threads:[~2021-06-28  6:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-27  6:05 SLIME and SBCL (Common Lisp) Emanuel Berg via Users list for the GNU Emacs text editor
2021-06-27 13:15 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-06-27 14:16   ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-06-27 18:14     ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-06-28  6:41 ` Jean Louis [this message]
2021-06-28 10:30   ` Arthur Miller
2021-06-28 14:03     ` Jean Louis
2021-07-06  6:50       ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-07-06  6:49     ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-07-06  6:47   ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-07-06 20:31     ` Jean Louis

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=YNlvMtyAn94TQF44@protected.localdomain \
    --to=bugs@gnu.support \
    --cc=help-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.
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).