unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Heime <heimeborgia@protonmail.com>
To: Eduardo Ochs <eduardoochs@gmail.com>
Cc: 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 18:10:27 +0000	[thread overview]
Message-ID: <D5IEQgepGrjhWaffttyDYO2hrQIQ7S8zGonJCdJc5unMnTpXcxVDXk7by-lllSz-noFftbLz5OtkfxYZQzFtbFXPJ58EmoZRp0bHB5dh43Y=@protonmail.com> (raw)
In-Reply-To: <CADs++6h9Ebp8PYkyLaPps7xT-TNjcr1Et4H9rJ5SzCCjb6g21A@mail.gmail.com>


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

Eduardo, it would be really helpful (especially to those using eev from source) to 
start using version numbers for your eev.

Could you do that ? What version would you describe the current eev ?

You have mentioned having a series of workshops in 2021 and 2022, where very few 
people attended them.  That has happened to me as well.  Why do you think few
people attended ?

"But they inspired me to produce many pages and videos."  Very Good :)

  





  parent reply	other threads:[~2023-08-06 18:10 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
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 [this message]
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

  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='D5IEQgepGrjhWaffttyDYO2hrQIQ7S8zGonJCdJc5unMnTpXcxVDXk7by-lllSz-noFftbLz5OtkfxYZQzFtbFXPJ58EmoZRp0bHB5dh43Y=@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.
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).