Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: info-gnus-english@gnu.org
Subject: Re: Strip signature on reply without standard separator
Date: Thu, 25 Aug 2022 00:26:42 +0200	[thread overview]
Message-ID: <87tu61i8gt.fsf@web.de> (raw)
In-Reply-To: <875yii2oru.fsf@dataswamp.org>

Emanuel Berg <incal@dataswamp.org> writes:

> If you quote a lambda it is just a list with data:
>
> '(a b c)
>
> '(lambda not an anonymous function)
>
> Eval and you will see, there's no difference in
> principle. Lists.

Yes - and you want to make your lambda forms subject to evaluation, for
several different reasons.  They are not data.  You want to use the
return value, not the expression.

Michael.



  reply	other threads:[~2022-08-24 22:34 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-09  4:28 Satoshi Yoshida
2022-08-09  5:56 ` Emanuel Berg
2022-08-09  8:34   ` Satoshi Yoshida
2022-08-09  8:52     ` Emanuel Berg
2022-08-09  9:25       ` Satoshi Yoshida
2022-09-11  9:46       ` Satoshi Yoshida
2022-09-12  6:45         ` Satoshi Yoshida
2022-09-14  6:08           ` Emanuel Berg
2022-09-14  7:48             ` Satoshi Yoshida
2022-08-11  6:41 ` Satoshi Yoshida
2022-08-11 14:48   ` Satoshi Yoshida
2022-08-12  3:06     ` Satoshi Yoshida
2022-08-11 15:26   ` Satoshi Yoshida
2022-08-24  2:30   ` Satoshi Yoshida
2022-08-24  2:37     ` Emanuel Berg
2022-08-24  3:55       ` Satoshi Yoshida
2022-08-24  5:28         ` Emanuel Berg
2022-08-24 22:26           ` Michael Heerdegen [this message]
2022-08-25  2:10             ` Satoshi Yoshida
2022-08-25  3:04           ` Strip signature on reply without standard separator [solved] Satoshi Yoshida
2022-08-25  6:46             ` Emanuel Berg
2022-08-27  6:59               ` Strip signature on reply without standard separator Satoshi Yoshida
2022-08-27  7:19             ` Satoshi Yoshida
2022-09-04  0:48               ` Satoshi Yoshida
2022-09-04  2:04                 ` Emanuel Berg
2022-09-06 23:36                   ` Satoshi Yoshida
2022-09-07  1:14                     ` Emanuel Berg
2022-09-15 23:50                       ` Satoshi Yoshida
2022-09-19  0:58                         ` Emanuel Berg
2022-09-21  9:15                           ` Satoshi Yoshida
2022-09-21 13:15                             ` Emanuel Berg
2022-09-23 21:36                               ` Satoshi Yoshida
2022-09-24 15:29                                 ` Emanuel Berg
2022-09-25  3:32                                   ` Satoshi Yoshida
2022-09-25  3:41                                     ` Emanuel Berg
2022-09-26  8:03                                       ` Satoshi Yoshida
2022-09-26 12:28                                         ` Emanuel Berg
2022-10-22  6:16                                           ` Satoshi Yoshida
2022-10-23 23:45                                             ` Emanuel Berg
2022-09-25  9:42                                     ` Michael Heerdegen
2022-09-26  7:56                                       ` Satoshi Yoshida

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=87tu61i8gt.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=info-gnus-english@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 NNTP newsgroup(s).