From: Jorgen Schaefer <forcer@forcix.cx>
To: Nic Ferrier <nferrier@ferrier.me.uk>
Cc: emacs-devel@gnu.org
Subject: Re: Best practice for mocking functions/prompts/etc.
Date: Sun, 9 Nov 2014 12:05:10 +0100 [thread overview]
Message-ID: <20141109120510.2f5a099c@forcix> (raw)
In-Reply-To: <87d28wmzi8.fsf@ferrier.me.uk>
On Sun, 09 Nov 2014 10:36:47 +0000
Nic Ferrier <nferrier@ferrier.me.uk> wrote:
> Jorgen Schaefer <forcer@forcix.cx> writes:
>
> >> There are elisp mocking libs. But with lisp you don't really need
> >> them.
> >
> > Yep. I know how I would do this in my own package, and I know how I
> > can do this with Emacs "on-board" libraries. The latter feels rather
> > cumbersome to me, so I figured I'd ask if there are recommended
> > ways / best practices for packages that are meant to go into the
> > Emacs repository that I am missing. :-)
>
> And I don't think there are. The mocking stuff doesn't go anywhere
> because we don't need it very often... except in your use case.
>
> Make something!
I just had a quick talk off the list with Nic, because it seemed to me
we were talking past each other, and indeed we were! :-)
The question I had, which I seem to have not explained well, was:
How do we mock this case in the Emacs "core" (i.e. the main Emacs
repository), as we can not use existing mock libraries (that I know of)
because they are not part of Emacs.
I can obviously write my own, as Nic suggests above, or just use the
default verbose options, as I have in the initial mail, but I figured
I'd ask first if there was something I am missing before reinventing the
wheel. :-)
Regards,
Jorgen
next prev parent reply other threads:[~2014-11-09 11:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-08 18:34 Best practice for mocking functions/prompts/etc Jorgen Schaefer
2014-11-08 23:17 ` Nic Ferrier
2014-11-09 8:59 ` Jorgen Schaefer
2014-11-09 10:36 ` Nic Ferrier
2014-11-09 11:05 ` Jorgen Schaefer [this message]
2014-11-09 0:56 ` Lars Magne Ingebrigtsen
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=20141109120510.2f5a099c@forcix \
--to=forcer@forcix.cx \
--cc=emacs-devel@gnu.org \
--cc=nferrier@ferrier.me.uk \
/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.