From: phillip.lord@newcastle.ac.uk (Phillip Lord)
To: Martin Kaffanke <martin@kaffanke.at>
Cc: help-gnu-emacs@gnu.org
Subject: Re: automate command after saving
Date: Thu, 19 Nov 2015 14:17:58 +0000 [thread overview]
Message-ID: <87lh9u6pk9.fsf@newcastle.ac.uk> (raw)
In-Reply-To: <87ziyamhx1.fsf@kaffanke.at> (Martin Kaffanke's message of "Thu, 19 Nov 2015 10:56:26 +0100")
You could do this using after-save-hook. So, something like
(add-hook 'after-save-hook
'pandoc-hook)
(defun pandoc-hook()
(compile "pandoc -t latex...."))
Personally, I do this outside Emacs, though, with this little bash
script.
#!/bin/bash
make $*
while inotifywait -r -e MODIFY --exclude ".#*" --exclude ".*~" .
do
make $*;
done;
Cheap, cheerful but effective.
Phil
Martin Kaffanke <martin@kaffanke.at> writes:
> Hi there,
>
> I'd like to run a command after saving, but just if I switch it on.
>
> Following scenario:
>
> When I write on an org file, before printing I look at the pdf version
> created by
>
> pandoc -t latex -o filename-without-org-but-with.pdf filename.org
>
> And then I switch to emacs to do corrections.
>
> Now I'd like to automatically run pandoc again when I switch back to
> evince (which automaticaly loads the pdf new when changed on disk).
>
> How could a make a switch for emacs to automatically run pandoc again
> after C-x C-s?
>
> Thanks for your Ideas,
> Martin
--
Phillip Lord, Phone: +44 (0) 191 208 7827
Lecturer in Bioinformatics, Email: phillip.lord@newcastle.ac.uk
School of Computing Science, http://homepages.cs.ncl.ac.uk/phillip.lord
Room 914 Claremont Tower, skype: russet_apples
Newcastle University, twitter: phillord
NE1 7RU
next prev parent reply other threads:[~2015-11-19 14:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 9:56 automate command after saving Martin Kaffanke
2015-11-19 14:17 ` Phillip Lord [this message]
2015-11-19 15:10 ` Marcin Borkowski
2015-11-19 19:03 ` Martin Kaffanke
[not found] ` <mailman.250.1447959815.31583.help-gnu-emacs@gnu.org>
2015-11-20 14:00 ` Joost Kremers
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=87lh9u6pk9.fsf@newcastle.ac.uk \
--to=phillip.lord@newcastle.ac.uk \
--cc=help-gnu-emacs@gnu.org \
--cc=martin@kaffanke.at \
/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).