From: Emanuel Berg <incal@dataswamp.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Using called-interactively-p
Date: Wed, 05 Jul 2023 22:26:38 +0200 [thread overview]
Message-ID: <873522p0jl.fsf@dataswamp.org> (raw)
In-Reply-To: jrqFU4MVihYytjd4t4AOWLvLoRY6cyiKC1so0D4g_tC66_F8ca5Xyn_Q_-64paWzByJndMDqZhhlcJtN0frMtKKl9ux5Tlh8prW9FeBzI2w=@proton.me
It's the MVC (Model View Control) theory which is another way
of saying one should separate the interface from the
functionality from the data. In practice it is easier to
separate the interface from the functionality than separating
the data from whatever it is attached to. In Elisp one can
obviously do whatever, including have a neat
interface/functionality separation.
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2023-07-05 20:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 13:35 Using called-interactively-p uzibalqa
2023-07-05 15:25 ` Marcin Borkowski
2023-07-05 15:40 ` uzibalqa
2023-07-05 20:26 ` Emanuel Berg [this message]
2023-07-06 18:55 ` Marcin Borkowski
2023-07-06 21:36 ` Emanuel Berg
2023-07-05 17:52 ` Emanuel Berg
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=873522p0jl.fsf@dataswamp.org \
--to=incal@dataswamp.org \
--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).