Re: M1

mikel evins <[email protected]>
Newsgroups gmane.lisp.openmcl.devel
Message-ID <[email protected]>

> On Feb 21, 2022, at 9:29 AM, Joakim Sandgren <[email protected]> wrote:
> 
> precious info !!
> 
> true, that lispworks would be the easiest way. and I’m using the source code only to see how things work - since I’m not good at understanding documentation without examples.

Lispworks offers tools for quickly finding sources, and you can use them to browse the sources of the editor, your own code, and any libraries you use. You just can't read the sources of Lispworks itself (except the editor), because they don't include those sources in the product.

> but in emacs/slime, what I understand, it would be quite possible to have a bunch of buffers up, changing parameters in them…

Yes, that's certainly true. Emacs has a significant learning curve, but it has nice enough features for Lisp programming that many Lispers use it, despite the learning curve.

> but are there any possibilities to do graphics in emacs ? with some library somewhere or via open-nn… something ?
> menu ? shortcuts to open directories and files ? 

It depends on what you mean. Emac is amazingly customizable. You can display graphics in Emacs windows. You can customize its windows and menus. You can build whole applications on it (for example, see org-mode or CEDET). 

The catch is that anything you build with it is basically going to look and feel like Emacs.

I've used GNU Emacs daily since about 1988. I wouldn't say that I particularly like it, but I would say that I dislike every other programmer's editor more.

If you want an environment you can use to build apps, display graphics, and so on, Emacs will do the job. 

If you want other people to use your apps, not so much.


_______________________________________________
Openmcl-devel mailing list
[email protected]
https://lists.clozure.com/mailman/listinfo/openmcl-devel
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.