From: Heime <heimeborgia@protonmail.com>
To: Heime <heimeborgia@protonmail.com>
Cc: Eduardo Ochs <eduardoochs@gmail.com>,
Heime via Users list for the GNU Emacs text editor
<help-gnu-emacs@gnu.org>
Subject: Re: Printing code made by a macro
Date: Sun, 06 Aug 2023 02:16:12 +0000 [thread overview]
Message-ID: <d3pRFALoUgx70fNG8EGvJRtWXczoC9CE-ReFix8_hFqhm0ZqUbHnKnqulXaWrhY13iluq7T0M02U6PFKZbXt7cU8rwwb5HCAhjLebR2I2OM=@protonmail.com> (raw)
In-Reply-To: <yrDCN4qdgS2z-L4BTsoZM67HEtZsRZfcXqsjLU-vE_-IILKSkq3J8cNuqO2PouACkseBvOT-g0qQOx0BhqA2TX1XiR9lxPGSoriUvJH4c8Q=@protonmail.com>
------- Original Message -------
On Sunday, August 6th, 2023 at 1:15 PM, Heime <heimeborgia@protonmail.com> wrote:
> ------- Original Message -------
> On Sunday, August 6th, 2023 at 12:50 PM, Eduardo Ochs eduardoochs@gmail.com wrote:
>
>
>
> > On Sat, 5 Aug 2023, 21:44 Heime, heimeborgia@protonmail.com wrote:
> >
> > > You wrote eev ?
> >
> > Yes, but it has at least 10 other users besides me...
> > Cheers,
> > Edrx =)
>
>
> This find-eppm of yours, does it involve a lot of code in its implementation ?
> I thought that find-eppm is only to find code as text in files, rather than
> printing code results from macros.
Do you know in which file you implemented find-eppm ?
next prev parent reply other threads:[~2023-08-06 2:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-05 23:42 Printing code made by a macro Heime
2023-08-06 0:31 ` Eduardo Ochs
2023-08-06 0:44 ` Heime
2023-08-06 0:50 ` Eduardo Ochs
2023-08-06 1:15 ` Heime
2023-08-06 2:16 ` Heime [this message]
2023-08-06 2:54 ` Eduardo Ochs
2023-08-06 3:36 ` Heime
2023-08-06 17:23 ` Heime
2023-08-06 20:36 ` Eduardo Ochs
2023-08-06 22:45 ` Heime
2023-08-06 23:11 ` Emanuel Berg
2023-08-06 18:10 ` Heime
2023-08-06 5:04 ` Eli Zaretskii
2023-08-06 6:22 ` Sebastian Miele
2023-08-07 19:54 ` Pierre Rouleau
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='d3pRFALoUgx70fNG8EGvJRtWXczoC9CE-ReFix8_hFqhm0ZqUbHnKnqulXaWrhY13iluq7T0M02U6PFKZbXt7cU8rwwb5HCAhjLebR2I2OM=@protonmail.com' \
--to=heimeborgia@protonmail.com \
--cc=eduardoochs@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.
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.