From: Jean Louis <bugs@gnu.support>
To: Madhu <enometh@meer.net>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Lisp Live buffer
Date: Fri, 23 Dec 2022 11:23:11 +0300 [thread overview]
Message-ID: <Y6Vlb3hZNyzfp49G@protected.localdomain> (raw)
In-Reply-To: <m3359qt9kj.fsf@leonis4.robolove.meer.net>
* Madhu <enometh@meer.net> [2022-12-08 14:34]:
> * Emanuel Berg <87sfhsczaa.fsf @dataswamp.org> :
> Wrote on Tue, 06 Dec 2022 16:44:29 +0100:
>
> > I'd like a buffer that shows Lisp Live ...
> >
> > you say it should show some list or data structure, it
> > visualizes it (can/should be text only) and then if I in some
> > other buffer or wherever basically append to the list or
> > whatever it's updated in the live buffer - like watch(1),
> > maybe, only cooler ...
OK the lively functions or similar principle solve the above intention.
> > That way, one could make a whole game text only and then throw
> > it at some GFX guys, hey, draw this, and have 100% MVC
> > separation (and "in parallel", throw it to some other guys and
> > get two games that are actually the same, but not ...)
Doesn't that already exist in EIEIO?
EIEIO (“Enhanced Implementation of Emacs Interpreted Objects”)
provides an Object Oriented layer for Emacs Lisp, following the basic
concepts of the Common Lisp Object System (CLOS). It provides a
framework for writing object-oriented applications in Emacs.
> you've seen lively.el https://lukego.livejournal.com/23379.html
;;; Go to the end of any of the following lines and run `M-x lively'
;;; Current time: Fri Dec 23 11:19:41 2022
;;; Last command: last-command
;;; Open buffers: 208
;;; Unix processes: (lively-shell-command "ps -a | wc -l")
Those functions are very useful, thanks. I keep for later as sometimes
I do need it, for example when we run campaign and new people leads
are continually and hourly entered into the database.
--
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
In support of Richard M. Stallman
https://stallmansupport.org/
prev parent reply other threads:[~2022-12-23 8:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 15:44 Lisp Live buffer Emanuel Berg
2022-12-07 3:06 ` Jean Louis
2022-12-07 3:54 ` Emanuel Berg
2022-12-23 8:15 ` Jean Louis
2022-12-26 20:26 ` Emanuel Berg
2022-12-27 1:12 ` Emanuel Berg
2022-12-28 0:32 ` Emanuel Berg
2022-12-28 2:04 ` Emanuel Berg
2022-12-28 2:08 ` Emanuel Berg
2022-12-28 9:25 ` tomas
2022-12-28 19:53 ` Emanuel Berg
2022-12-28 23:20 ` Emanuel Berg
2022-12-08 11:32 ` Madhu
2022-12-23 8:23 ` Jean Louis [this message]
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=Y6Vlb3hZNyzfp49G@protected.localdomain \
--to=bugs@gnu.support \
--cc=enometh@meer.net \
--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).