all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "scopeview ." <scopeview126@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: What's the best way to write complex emacs extension
Date: Tue, 4 Nov 2014 08:16:13 +0800	[thread overview]
Message-ID: <CANOM=vfwi2Vzbn=tnBN-GrCtyG1_hinNdSAUg7ofbO0nPMGQ0w@mail.gmail.com> (raw)
In-Reply-To: <jwvtx2i41gb.fsf-monnier+emacs@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 686 bytes --]

Thanks

I have used edebug for developing my elisp extension.

I just feel elisp + XML + c binary for complex extension is not so
convenient. Even with edebug, when some predication failed, I should guess
where it could be then set edebug function entry.

On Sun, Nov 2, 2014 at 1:27 PM, Stefan Monnier <monnier@iro.umontreal.ca>
wrote:

> > When I wrote my simple extension, pure elisp code is ok. But I found it
> is
> > hard to write complex elisp extension. Because when elisp predication
> > failed (for example stringp) it hard to find out the failed predication
> > place. (no file:function:line_number or backtrace)
>
> Options => Enter Debugger on Error
>
>
>         Stefan
>

[-- Attachment #2: Type: text/html, Size: 1147 bytes --]

  reply	other threads:[~2014-11-04  0:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-01 23:25 What's the best way to write complex emacs extension scopeview .
2014-11-02  4:12 ` Stephen J. Turnbull
2014-11-02  5:27 ` Stefan Monnier
2014-11-04  0:16   ` scopeview . [this message]
2014-11-04  2:59     ` Alexis
2014-11-02 11:52 ` Stephen Leake

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='CANOM=vfwi2Vzbn=tnBN-GrCtyG1_hinNdSAUg7ofbO0nPMGQ0w@mail.gmail.com' \
    --to=scopeview126@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.