unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Eduardo Ochs <eduardoochs@gmail.com>
To: Heime <heimeborgia@protonmail.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: Sat, 5 Aug 2023 23:54:45 -0300	[thread overview]
Message-ID: <CADs++6h7u-Zhh4Zn34oxAPuqGs9tGeyWYaF4YkN+fkgQJyQPfA@mail.gmail.com> (raw)
In-Reply-To: <d3pRFALoUgx70fNG8EGvJRtWXczoC9CE-ReFix8_hFqhm0ZqUbHnKnqulXaWrhY13iluq7T0M02U6PFKZbXt7cU8rwwb5HCAhjLebR2I2OM=@protonmail.com>

On Sat, 5 Aug 2023 at 23:16, Heime <heimeborgia@protonmail.com> wrote:

>
> Do you know in which file you implemented find-eppm ?
>

 Hi Heime,

`find-eppm' uses the functions `find-epp', `find-eoutput-rerun',
`ee-goto-position' and `ee-goto-rest' and the variable
`ee-buffer-name'. You can go to their definitions in the source code
of eev by using these sexp hyperlinks,

  (find-evariable 'ee-buffer-name)
  (find-efunction 'ee-goto-position)
  (find-efunction 'ee-goto-rest)
  (find-efunction 'find-eoutput-rerun)
  (find-efunction 'find-epp)
  (find-efunction 'find-eppm)

  (find-eevfile "eev-blinks.el" "defvar ee-buffer-name")
  (find-eev     "eev-blinks.el" "ee-goto-position")
  (find-eev     "eev-blinks.el" "find-eoutput")
  (find-eev     "eev-blinks.el" "find-epp")

or with these URLs:

  http://anggtwu.net/eev-current/eev-blinks.el.html
  http://anggtwu.net/eev-current/eev-blinks.el.html#ee-goto-position
  http://anggtwu.net/eev-current/eev-blinks.el.html#find-eoutput
  http://anggtwu.net/eev-current/eev-blinks.el.html#find-epp

Cheers,
  Edrx


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

  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=CADs++6h7u-Zhh4Zn34oxAPuqGs9tGeyWYaF4YkN+fkgQJyQPfA@mail.gmail.com \
    --to=eduardoochs@gmail.com \
    --cc=heimeborgia@protonmail.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).