unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Emanuel Berg <incal@dataswamp.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Should prefix variable be used in function argument list
Date: Sun, 10 Jul 2022 06:14:52 +0200	[thread overview]
Message-ID: <87k08la9j7.fsf@dataswamp.org> (raw)
In-Reply-To: 87bktymzks.fsf@posteo.net

Philip Kaludercic wrote:

>> Check out the theory on MVC for why ...
>>
>> Check out the practice of annoying little Elisp pointers in
>> help mode for why ...
>
> I would appreciate it if you could explain what you are
> talking about instead of just insinuating points.

MVC = Model View Control.

Model is a word from OO theory, we would call it the program's
state or maybe internals, logic. Yeah, what it is and how that
works, basically.

View = What you see, i.e. the part of the interface that's
presented to you.

Control = the interface from the other side, from you as
a user

Not unlike the Lisp REPL where R (read) would be control,
E (eval) would be the logic acted upon the state, and
P (print) would be what the user sees from his or
her viewpoint.

So these three (MVC) should be separated, modules.

So translated to our case, and not in general but this
specifically, it becomes the control has not one control to do
something, it has two, one interactively and one
non-interactively, and you have to think in terms of the
program and Lisp environment, i.e. in the Model part of MVC
how that would work differently and so.

So you have Lisp in code, its makes up the model, but if the
user do M-: and types some Lisp, that is actually _not_ part
of the Model but is a part of, or an alternative interface.

If your practical reasons one has to have two functions, one
interactively and one non-interactively, what one can do is
having another function, e.g. (bob) and that would in turn do
either (goto-char (point-min)) or do it interactively if there
was some very special situation that called for that.
Such things can pe handled under the hood. But stuff that is
intuitive to the user, like that, one can have that
contra-intuitive and then hope that comments in the help
should remedy that.

>> Actually they are useful! So the annoyance should be
>> directed at the practice which they try to correct at
>> a later stage. That would be more fair.
>
> (Also, why do you always just respond to the list and don't
> CC the person you are responding too)

Often the sad truth is, they just can't handle the truth.

-- 
underground experts united
https://dataswamp.org/~incal




  reply	other threads:[~2022-07-10  4:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-08 17:12 Should prefix variable be used in function argument list carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-08 17:40 ` Philip Kaludercic
2022-07-08 17:53   ` Emanuel Berg
2022-07-08 18:11     ` Emanuel Berg
2022-07-09  8:59       ` Philip Kaludercic
2022-07-10  4:14         ` Emanuel Berg [this message]
2022-07-08 17:41 ` Emanuel Berg
2022-07-08 18:09   ` Emanuel Berg
2022-07-08 21:08   ` carlmarcos--- via Users list for the GNU Emacs text editor
2022-07-09  4:57     ` tomas

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=87k08la9j7.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).