all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Emanuel Berg <moasenwood@zoho.eu>
Cc: "'Help-Gnu-Emacs \(help-gnu-emacs@gnu.org\)'" <help-gnu-emacs@gnu.org>
Subject: RE: [External] : messages to *Messages* without appearing in mini-buffer?
Date: Fri, 12 Nov 2021 17:06:09 +0000	[thread overview]
Message-ID: <SJ0PR10MB5488F00058934A82EB328031F3959@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87h7ci81ho.fsf@zoho.eu>

[-- Attachment #1: Type: text/plain, Size: 1304 bytes --]

> Best:
>   (do-some-thing)
> Second best:
>   (do-some-thing this-way)
> Not 3rd place:
>   (let ((control-behavior with-some-value))
>     (in-function) )

That's 3rd-grade "knowledge".  (Only a rough
first approximation, if you prefer.)

There's NO such "best", though convincing the
Lexical Police of this is hardly worth trying. ;-)
"Best" depends on the purpose/use.

[The same applies to side effects and state.
And to `quote' (which by itself destroys
referential transparency).  And to applicative
order evaluation.  And to...  All such "dirty",
more-difficult-to-prove/manage/manipulate, more
complicated things have their uses/advantages.]

There's are reasons that Common Lisp and Elisp
provide not only lexical binding but _also_
dynamic binding.  And the reasons are not just
hysterical raisins.  And Elisp has its own
particular reasons, as it's a Lisp for an editor
(and more).


https://www.gnu.org/software/emacs/emacs-paper.html#SEC17

"It is not necessary for dynamic scope to be the
only scope rule provided, just useful for it to
be available..."


https://www.gnu.org/software/emacs/emacs-paper.html#SEC18

"Some language designers believe that dynamic
binding should be avoided, and explicit argument
passing should be used instead..."


[-- Attachment #2: winmail.dat --]
[-- Type: application/ms-tnef, Size: 14958 bytes --]

  parent reply	other threads:[~2021-11-12 17:06 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-11 14:33 messages to *Messages* without appearing in mini-buffer? Eric S Fraga
2021-11-11 14:45 ` Gregory Heytings
2021-11-11 14:55   ` Eric S Fraga
2021-11-11 17:01 ` [External] : " Drew Adams
2021-11-11 17:07   ` Eric S Fraga
2021-11-12  0:10   ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-11-12  0:16     ` Gregory Heytings
2021-11-12  0:36       ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-11-12  2:08         ` Michael Heerdegen
2021-11-12  3:20           ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-11-12  3:56             ` Michael Heerdegen
2021-11-12  4:02               ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-11-12  4:13                 ` Michael Heerdegen
2021-11-12  4:28                   ` Michael Heerdegen
2021-11-12  5:00                     ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-11-12  5:07                   ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-11-12  5:19                     ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-11-12 21:31                     ` Michael Heerdegen
2021-11-12 21:36                       ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-11-12 17:06                 ` Drew Adams [this message]
2021-11-21 11:08                   ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-11-12  0:20     ` Drew Adams
2021-11-12  0:30       ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-11-12  1:47         ` Drew Adams
2021-11-12  3:10           ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-11-12 17:01             ` Drew Adams

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=SJ0PR10MB5488F00058934A82EB328031F3959@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=moasenwood@zoho.eu \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.