From: Heime <heimeborgia@protonmail.com>
To: Corwin Brust <corwin@bru.st>
Cc: Pierre Rouleau <prouleau001@gmail.com>,
Heime via Users list for the GNU Emacs text editor
<help-gnu-emacs@gnu.org>
Subject: Re: Passing result of macroexpand-all as argument to a function
Date: Wed, 09 Aug 2023 02:40:57 +0000 [thread overview]
Message-ID: <9o5E7MoUMZVoQPN_YOcy921n2Afw2TEfhWagGmLK23cMPbzzIZZWGwyY-5nqZm5jyETMxzAGA_tbwHzNjv-xnmVIXO3ZnrgwevE0fTj9l_4=@protonmail.com> (raw)
In-Reply-To: <CAJf-WoS=oT+Uy60dzJ2fsCBjTMo+jc=juEsNdOnxMpUAe9jVLg@mail.gmail.com>
------- Original Message -------
On Wednesday, August 9th, 2023 at 2:26 PM, Corwin Brust <corwin@bru.st> wrote:
> On Tue, Aug 8, 2023 at 9:04 PM Heime heimeborgia@protonmail.com wrote:
>
> > On Wednesday, August 9th, 2023 at 1:37 PM, Pierre Rouleau prouleau001@gmail.com wrote:
> >
> > > On Tue, Aug 8, 2023 at 8:22 PM Heime heimeborgia@protonmail.com wrote:
> > >
> > > 3- If #2 is not clear, reading a LISP tutorial will help. Investing time
> > > reading on LISP and Emacs Lisp will help a lot.
> >
> > I am going to pass
>
>
> What does "I am going to pass" mean, please?
>
> I hope that it does not mean "I do not want to read the manual". (Or
> were you saying that you do not want to explain your problem, or
> perhaps you object to quoting lisp forms to pass them around?)
>
> I ask because, in my view, it is not acting kindly toward those who
> read the list and attempt to help people, that you would refuse to
> read the documentation. In fact, it initially strikes me as rather
> rude to depend only on others to personally explain solutions (to
> problems that you do not define). Especially so when I consider you
> are depending on the rest of us to read the documentation (source,
> this list, etc), in order to know something you don't. I hope this
> helps to make clear why I found your "I am going to pass" remark so
> exceptional as to comment on it, choosing in this case to completely
> ignore the context of whatever it is that you might want to know.
Seems that ignoring the context has became a habit of yours !
next prev parent reply other threads:[~2023-08-09 2:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 0:22 Passing result of macroexpand-all as argument to a function Heime
2023-08-09 1:37 ` Pierre Rouleau
2023-08-09 2:04 ` Heime
2023-08-09 2:26 ` Corwin Brust
2023-08-09 2:40 ` Heime [this message]
2023-08-09 2:27 ` [External] : " Drew Adams
2023-08-09 2:53 ` Heime
2023-08-09 4:02 ` Pierre Rouleau
2023-08-09 4:14 ` Drew Adams
2023-08-09 3:37 ` Michael Heerdegen
2023-08-09 4:13 ` Heime
2023-08-09 4:36 ` Michael Heerdegen
2023-08-09 4:54 ` Heime
2023-08-09 15:21 ` Drew Adams
2023-08-09 4:28 ` Drew Adams
2023-08-09 3:39 ` Michael Heerdegen
2023-08-09 5:06 ` Heime
2023-08-09 15:27 ` [External] : " Drew Adams
2023-08-09 20:34 ` Heime
2023-08-09 21:24 ` Drew Adams
2023-08-09 21:32 ` Heime
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='9o5E7MoUMZVoQPN_YOcy921n2Afw2TEfhWagGmLK23cMPbzzIZZWGwyY-5nqZm5jyETMxzAGA_tbwHzNjv-xnmVIXO3ZnrgwevE0fTj9l_4=@protonmail.com' \
--to=heimeborgia@protonmail.com \
--cc=corwin@bru.st \
--cc=help-gnu-emacs@gnu.org \
--cc=prouleau001@gmail.com \
/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).