From: bolega <gnuist006@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: identity function with an echo side effect
Date: Wed, 11 Aug 2010 10:42:43 -0700 (PDT) [thread overview]
Message-ID: <106a3bf2-cd32-4b50-8e99-81e0cad8efa2@j8g2000yqd.googlegroups.com> (raw)
In-Reply-To: 87ocd99qps.fsf@kuiper.lan.informatimago.com
On Aug 11, 7:19 am, p...@informatimago.com (Pascal J. Bourguignon)
wrote:
> bolega <gnuist...@gmail.com> writes:
> > On Aug 10, 4:03 pm, p...@informatimago.com (Pascal J. Bourguignon)
> > wrote:
> >> bolega <gnuist...@gmail.com> writes:
> >> > After searching google groups and emacs apropos extensively, I could
> >> > not find a function, perhaps I am missing one that can return
> >> > identically return its argument and has a small side effect of echoing
> >> > the argument in some place such as for example
>
> >> > the mini buffer or the point at which C-x C-e is typed.
>
> >> > For example, calling this function "echo" , usage would look like
> >> > this :
>
> >> > (cdr ( echo (cdr (echo (cdr (echo '(a b c d)))))))
>
> >> > echo:
> >> > '(a b c d) or (a b c d) (I am not sure which would be appropriate)
> >> > (b c d)
> >> > (c d)
>
> >> > result:
> >> > (d)
>
> >> > Is there a need for quotes to prevent evaluation of alphabets at any
> >> > phase ?
>
> No. Expressions are evaluated only by EVAL or LOAD (and at
> compilation time, compilation time expressions by COMPILE and
> COMPILE-FILE). Otherwise, values are just values, they don't get
> evaluated magically (for what reason should they?)
>
> >> In Common Lisp, you can use PRINT for this.
>
> >> CL-USER> (cdr (print (cdr (print (cdr (print '(a b c d)))))))
>
> >> (A B C D)
> >> (B C D)
> >> (C D)
> >> (D)
> >> CL-USER>
> >> [...]
>
> > If you dont mind, how many years have you spent on learning emacs/
> > lisp ?
>
> 20 years.
>
> > Can you kindly give a reading syllabus, books list and possibly time
> > for completion from your perspective and what to get out of each book
> > since they have some common repetition.
>
> http://www.cliki.net/admin/search?words=books
>
> In particular, I like to advise:
>
> Common Lisp: A Gentle Introduction to Symbolic Computation
> http://www-cgi.cs.cmu.edu/afs/cs.cmu.edu/user/dst/www/LispBook/index....
> http://www.cs.cmu.edu/~dst/LispBook/
>
> > Are there any implicit quotations taking place in the above sequence
> > of cdr, print ... ?
>
> Since CDR and PRINT are function, no implicit quotation occurs: the
> result values are directly passed as argument to the next function.
Then why does the following gives an error. Currently, I only have
elisp working so we confine to emacs runs.
(cdr (print (cdr (print (cdr (print (a b c d))))))) C-x C-e
gives this error if I remove the quote. why ? I get errors if I remove
all prints. This means if the first cdr required quoted list, then the
rest must also require it. Hence, an implicit quotation might be
occurring as in setq ? Also, plz explain me the debugger output in
detail so I can figure it out myself. may be a line by line comment
and if there is a more comprehensive example you can cook, better for
all the readers, once and for all.
Debugger entered--Lisp error: (void-function a)
(a b c d)
(print (a b c d))
(cdr (print (a b c d)))
(print (cdr (print ...)))
(cdr (print (cdr ...)))
(print (cdr (print ...)))
(cdr (print (cdr ...)))
eval((cdr (print (cdr ...))))
eval-last-sexp-1(nil)
eval-last-sexp(nil)
* call-interactively(eval-last-sexp)
>
> Only macros receive their arguments un-evaluated, which could be
> characterized as an "implicit quotation".
>
> --
> __Pascal Bourguignon__ http://www.informatimago.com/
next prev parent reply other threads:[~2010-08-11 17:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-10 20:56 identity function with an echo side effect bolega
2010-08-10 23:03 ` Pascal J. Bourguignon
2010-08-11 5:01 ` bolega
2010-08-11 14:19 ` Pascal J. Bourguignon
2010-08-11 17:42 ` bolega [this message]
2010-08-11 20:43 ` Pascal J. Bourguignon
2010-08-12 2:35 ` TheFlyingDutchman
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=106a3bf2-cd32-4b50-8e99-81e0cad8efa2@j8g2000yqd.googlegroups.com \
--to=gnuist006@gmail.com \
--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).