From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Luke Gorrie Newsgroups: gmane.emacs.devel Subject: Re: Common Lisp in Emacs (lisp-mode, font-lock, SLIME, SLY, ...) Date: Sat, 11 Apr 2020 06:58:29 +0200 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000192ab805a2fcb4e4" Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="9862"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Luke Gorrie , YUE Daian , emacs-devel@gnu.org, Spenser , Helmut Eller , =?UTF-8?B?Sm/Do28gVMOhdm9yYQ==?= To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Apr 11 08:31:56 2020 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jN9gK-0002TY-3s for ged-emacs-devel@m.gmane-mx.org; Sat, 11 Apr 2020 08:31:56 +0200 Original-Received: from localhost ([::1]:49276 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jN9gJ-0002OO-53 for ged-emacs-devel@m.gmane-mx.org; Sat, 11 Apr 2020 02:31:55 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:49802) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jN8E8-000104-36 for emacs-devel@gnu.org; Sat, 11 Apr 2020 00:58:45 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jN8E6-0001zT-QN for emacs-devel@gnu.org; Sat, 11 Apr 2020 00:58:43 -0400 Original-Received: from mail-io1-xd2c.google.com ([2607:f8b0:4864:20::d2c]:39844) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1jN8E6-0001w9-Fm for emacs-devel@gnu.org; Sat, 11 Apr 2020 00:58:42 -0400 Original-Received: by mail-io1-xd2c.google.com with SMTP id m4so3742447ioq.6 for ; Fri, 10 Apr 2020 21:58:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=snabb-co.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=/4puIcPukx+5tx85WNOQk6TV/4leoErTyGfIUkwIW3A=; b=IqZUf2g6d+DtJFUIJuwYB+H3POAdRDuLcpfI6Mi06qMJBWj/kp/oQsqtrSJSZryrVe ofSslxf0oF6xXrICUATJ4+byDeWuCblf6L30SLZnNy30Fpnx/RlqPyK56DJTbulcZQEi NBIyC4ZgAqgMZkuCvinsEp8gEV7pqzw/SJD8Gw1vIL6/C0PAV/Br5F6FmGBY8Iz9tQ8V 0gTVXHWp8U4h+Dmm4sISpYel7NllWo5UVCQMMkuCNciEl2OzdeuisyoOApzgQNavis1Y MMBHeM/brPSYRcK2sj75KLLUT+C4Nl9gVdKyxqvauR99GF+OGO4qvIkrLQ6K4RUQX3T5 qASQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=/4puIcPukx+5tx85WNOQk6TV/4leoErTyGfIUkwIW3A=; b=OJPjjfLjeHtCcOW2N+lLqIfgrzh8Nx4/29sxBk8M3TUJesdPB5fKHa7jupFJJuVJ4d fzSNyL3eLat5tGLdQt/sHFXEMnrfLPZPpouZ/oZxlahIole9cu/GINNFD5vOGFyOCZ3r 4UEIaRMa5ENx4ynOEqxXoGGzWo2ARcmbgAoC/3k48wkF/PYdLOV5LEttxZ8eT1Y2wh/C 7T7PJmtISt/njeurjLnhydY/ZPelEWHYfyC8L5XoetaEeFUsVr5KGM6C/gcZ711235QF 1RMHjBGpnI0HA+hNlPaocpXXG+oRPaPg78w3hJCs1NJbjlAPsXTa44y7R/CPH8d7lITF TFgQ== X-Gm-Message-State: AGi0PuaxKHN0JE6MQd4jRcLieEQaLrjDErGXVKcLIm/iuuvFbh5XwAMg gDFxFqjIQpaM3hi+iQPmhIVU+MEyE4mak5K68wg= X-Google-Smtp-Source: APiQypIzGCIqSFdPRaFS4kGgzmakOZXX/MsIy97LgT9ec8jbz37bQs+POWeotgCY/f3re4JWJR2iGmuuSuRk52PtheQ= X-Received: by 2002:a02:6349:: with SMTP id j70mr7581898jac.137.1586581120557; Fri, 10 Apr 2020 21:58:40 -0700 (PDT) In-Reply-To: X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2607:f8b0:4864:20::d2c X-Mailman-Approved-At: Sat, 11 Apr 2020 02:30:33 -0400 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:246817 Archived-At: --000000000000192ab805a2fcb4e4 Content-Type: text/plain; charset="UTF-8" I'm the one most out of the loop so I rely on someone to correct my misinformation :) but the way I remember it at least from the early days is SLIME is a minor-mode below lisp-mode that reuses the lisp-mode functionality like navigating by sexp, font-lock, indentation, etc. The dynamic indentation stuff in SLIME, like detecting &body in macros, is used to configure property lists that lisp-mode will see. So really relying on and heavily using lisp-mode. That could well be wrong and/or out of date though. Just answering due to the novelty of being asked something about that code :) On Sat, 11 Apr 2020 at 01:00, Stefan Monnier wrote: > Sorry to spam here a little, but I was looking into how we should > integrate something like cl-font-lock > (https://github.com/cl-font-lock/cl-font-lock) into Emacs and then > I started to wonder... > > Who uses `lisp-mode`? IIUC neither SLY nor SLIME actually use > `lisp-mode` itself, they use some other major mode with its > fontification function, right? > > So do they already highlight built-in functions, types, and variables in > a special way (presumably by querying the underlying Lisp process)? > > Do they actually use a proper child-mode of `lisp-mode`? > > Do they (re)use the font-lock keywords of `lisp-mode` at all, or do they > use something completely independent? > > > Stefan > > --000000000000192ab805a2fcb4e4 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I'm the one most out of the loop so I rely on someone = to correct my misinformation :) but the way I remember it at least from the= early days is

SLIME is a minor-mode below lisp-mode tha= t reuses the lisp-mode functionality like navigating by sexp, font-lock, in= dentation, etc. The dynamic indentation stuff in SLIME, like detecting &= ;body in macros, is used to configure property lists that lisp-mode will se= e. So really relying on and heavily using lisp-mode.

That could well be wrong and/or out of date though. Just answering due t= o the novelty of being asked something about that code :)



On Sat, 11 Apr 2020 at 01:00, Stefan Monnier <monnier@iro.umontreal.ca> wrote= :
Sorry to spam = here a little, but I was looking into how we should
integrate something like cl-font-lock
(https://github.com/cl-font-lock/cl-font-lock) into = Emacs and then
I started to wonder...

Who uses `lisp-mode`?=C2=A0 IIUC neither SLY nor SLIME actually use
`lisp-mode` itself, they use some other major mode with its
fontification function, right?

So do they already highlight built-in functions, types, and variables in a special way (presumably by querying the underlying Lisp process)?

Do they actually use a proper child-mode of `lisp-mode`?

Do they (re)use the font-lock keywords of `lisp-mode` at all, or do they use something completely independent?


=C2=A0 =C2=A0 =C2=A0 =C2=A0 Stefan

--000000000000192ab805a2fcb4e4--