From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: Emacs Org mode <emacs-orgmode@gnu.org>
Subject: Re: Indentation of backend definitioon
Date: Thu, 14 Mar 2013 23:32:22 +0100 [thread overview]
Message-ID: <87mwu5bojt.fsf@gmail.com> (raw)
In-Reply-To: <CBB542D5-8D8F-41BA-B73D-9CFC41E0B30D@gmail.com> (Carsten Dominik's message of "Thu, 14 Mar 2013 07:52:19 +0100")
Hello,
Carsten Dominik <carsten.dominik@gmail.com> writes:
> I propose the following patch to improve the automatic
> indentation of the backend definition macros in ox.el.
>
> - Carsten
>
> diff --git a/lisp/ox.el b/lisp/ox.el
> index c5b6d7c..31983b2 100644
> --- a/lisp/ox.el
> +++ b/lisp/ox.el
> @@ -987,6 +987,7 @@ keywords are understood:
> ',export-block))
> ;; Splice in the body, if any.
> ,@body)))
> +(put 'org-export-define-backend 'lisp-indent-function 1)
>
> (defmacro org-export-define-derived-backend (child parent &rest body)
> "Create a new back-end as a variant of an existing one.
> @@ -1078,6 +1079,7 @@ The back-end could then be called with, for example:
> ',export-block))
> ;; Splice in the body, if any.
> ,@body)))
> +(put 'org-export-define-derived-backend 'lisp-indent-function 2)
>
> (defun org-export-backend-parent (backend)
> "Return back-end from which BACKEND is derived, or nil."
> @@ -5201,6 +5203,7 @@ and
> (message "Process '%s' exited abnormally" p))
> (unless org-export-async-debug
> (delete-file ,,temp-file)))))))))))))
> +(put 'org-export-async-start 'lisp-indent-function 1)
>
> (defun org-export-add-to-stack (source backend &optional process)
> "Add a new result to export stack if not present already.
Isn't it the default behaviour (see `declare' in definitions)?
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2013-03-14 22:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-14 6:52 Indentation of backend definitioon Carsten Dominik
2013-03-14 22:32 ` Nicolas Goaziou [this message]
2013-03-15 6:33 ` Carsten Dominik
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=87mwu5bojt.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=carsten.dominik@gmail.com \
--cc=emacs-orgmode@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.