unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Visuwesh <visuweshm@gmail.com>
To: Andreas Schwab <schwab@suse.de>
Cc: Akib Azmain Turja <akib@disroot.org>,  emacs-devel@gnu.org
Subject: Re: Compiling Emacs from source for hacking on it
Date: Tue, 31 May 2022 19:53:16 +0530	[thread overview]
Message-ID: <87a6axdbmz.fsf@gmail.com> (raw)
In-Reply-To: <mvmy1yh4whc.fsf@suse.de> (Andreas Schwab's message of "Tue, 31 May 2022 16:17:51 +0200")

[செவ்வாய் மே 31, 2022] Andreas Schwab wrote:

> On Mai 31 2022, Akib Azmain Turja wrote:
>
>> But it says that with-memoizaton function definition is
>> void,
>
> That function indeed doesn't exist in Emacs, so it must be coming from
> some customisation of yours.

    with-memoization is a Lisp macro in ‘subr-x.el’.

    (with-memoization PLACE &rest CODE)

    Return the value of CODE and stash it in PLACE.
    If PLACE’s value is non-nil, then don’t bother evaluating CODE
    and return the value found in PLACE instead.

      Probably introduced at or before Emacs version 29.1.

It's a macro tho.



  reply	other threads:[~2022-05-31 14:23 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-31 12:07 Compiling Emacs from source for hacking on it Akib Azmain Turja
2022-05-31 12:45 ` Po Lu
2022-05-31 13:35   ` tomas
2022-05-31 13:42     ` Ken Brown
2022-05-31 14:01       ` tomas
2022-05-31 14:02       ` Óscar Fuentes
2022-05-31 14:10         ` tomas
2022-05-31 14:18           ` Óscar Fuentes
2022-05-31 16:27   ` Akib Azmain Turja
2022-05-31 16:55     ` Lars Ingebrigtsen
2022-05-31 18:16       ` Akib Azmain Turja
2022-05-31 18:18         ` Lars Ingebrigtsen
2022-05-31 13:06 ` Eli Zaretskii
2022-05-31 13:43   ` Eli Zaretskii
2022-05-31 16:22   ` Akib Azmain Turja
2022-05-31 16:39     ` Eli Zaretskii
2022-05-31 18:11       ` Akib Azmain Turja
2022-05-31 18:30         ` Akib Azmain Turja
2022-05-31 19:22           ` Eli Zaretskii
2022-06-01  1:10             ` Akib Azmain Turja
2022-06-01  2:42               ` Eli Zaretskii
2022-06-01 11:26                 ` Akib Azmain Turja
2022-06-01 12:15                   ` Eli Zaretskii
2022-06-01 12:41                     ` Akib Azmain Turja
2022-06-01 13:03                       ` Akib Azmain Turja
2022-06-01 13:13                         ` Eli Zaretskii
2022-06-01 13:07                       ` Eli Zaretskii
2022-06-01 16:36                         ` Akib Azmain Turja
2022-06-01 17:23                           ` Eli Zaretskii
2022-06-02 10:52         ` Philip Kaludercic
2022-06-02 16:47           ` Akib Azmain Turja
2022-05-31 14:17 ` Andreas Schwab
2022-05-31 14:23   ` Visuwesh [this message]
2022-05-31 16:24     ` Akib Azmain Turja
2022-05-31 14:52   ` Michael Heerdegen
2022-05-31 16:24     ` Akib Azmain Turja
2022-05-31 16:25   ` Akib Azmain Turja

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=87a6axdbmz.fsf@gmail.com \
    --to=visuweshm@gmail.com \
    --cc=akib@disroot.org \
    --cc=emacs-devel@gnu.org \
    --cc=schwab@suse.de \
    /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 public inbox

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

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).