From: Bastien Guerry <bzg@altern.org>
To: emacs-orgmode@gnu.org
Subject: [Accepted] make export dispatcher go away promptly
Date: Fri, 4 Feb 2011 20:02:38 +0100 (CET) [thread overview]
Message-ID: <20110204190238.EB5E18786@myhost.localdomain> (raw)
In-Reply-To: m1oc6rq1q8.fsf@gmail.com
Patch 582 (http://patchwork.newartisans.com/patch/582/) is now "Accepted".
Maintainer comment: none
This relates to the following submission:
http://mid.gmane.org/%3Cm1oc6rq1q8.fsf%40gmail.com%3E
Here is the original message containing the patch:
> Content-Type: text/plain; charset="utf-8"
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> Subject: [Orgmode] make export dispatcher go away promptly
> Date: Fri, 04 Feb 2011 20:05:35 -0000
> From: Dan Davison <dandavison7@gmail.com>
> X-Patchwork-Id: 582
> Message-Id: <m1oc6rq1q8.fsf@gmail.com>
> To: emacs-orgmode@gnu.org
>
> Following on from Stephen's recent post, a
> thing-that-slightly-bothers-me is the way the export dispatcher window
> doesn't go away until export is complete. I've briefly looked at the
> code twice now and it wasn't obvious to me why the save-window-excursion
> (line 941 org-exp.el) wasn't already doing what I wanted. However, the
> change below seems to have the effect I wanted. While this particular
> solution may be a hack, I wonder whether people would prefer its
> behaviour? E.g. try exporting this:
>
> #+title: title
>
> #+begin_src sh :exports results
> sleep 5 && echo hello
> #+end_src
>
> export can often take several seconds and it's nice to be able to zone
> out looking at your org document rather than the dispatcher window.
>
> Modified lisp/org-exp.el
>
>
> (I see that (sit-for .0001) is used in a couple of places in Org for
> this effect, so maybe that should be used instead.)
>
> Dan
>
>
> diff --git a/lisp/org-exp.el b/lisp/org-exp.el
> index 13fa549..3d291e2 100644
> --- a/lisp/org-exp.el
> +++ b/lisp/org-exp.el
> @@ -963,6 +963,7 @@ value of `org-export-run-in-background'."
> (setq r1 (read-char-exclusive)))
> (error "No enclosing node with LaTeX_CLASS or EXPORT_FILE_NAME")
> )))))
> + (redisplay)
> (and bpos (goto-char bpos))
> (setq r2 (if (< r1 27) (+ r1 96) r1))
> (unless (setq ass (assq r2 cmds))
>
next prev parent reply other threads:[~2011-02-04 19:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-04 15:05 [PATCH] make export dispatcher go away promptly Dan Davison
2011-02-04 16:21 ` Carsten Dominik
2011-02-04 19:02 ` Bastien Guerry [this message]
2011-02-04 19:03 ` Bastien
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110204190238.EB5E18786@myhost.localdomain \
--to=bzg@altern.org \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).