From: Kester Clegg <kester@cs.york.ac.uk>
Subject: Re: key binding two commands
Date: 21 Nov 2003 11:50:59 +0000 [thread overview]
Message-ID: <yqrad6qos7w.fsf@cs.york.ac.uk> (raw)
In-Reply-To: v9brr69hls.fsf@marauder.physik.uni-ulm.de
Reiner Steib <4.uce.03.r.s@nurfuerspam.de> writes:
> But a better solution IMHO would be to advice `TeX-command-master':
>
> (defadvice TeX-command-master (around rs-TeX-command-master-save activate)
> "Save buffer before `TeX-command-master'"
> (message "Saving buffer")
> (save-buffer)
> ad-do-it)
>
> Bye, Reiner.
Excellent - thanks for that.
--
************************************************************************
Kester Clegg Dept. of Computer Science,
Research Assistant (UTC) University of York,
Tel (01904) 43 27 49 email: kester at cs.york.ac.uk
************************************************************************
next prev parent reply other threads:[~2003-11-21 11:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-21 9:11 key binding two commands Kester Clegg
2003-11-21 9:49 ` Reiner Steib
2003-11-21 11:50 ` Kester Clegg [this message]
2003-11-21 16:49 ` Kevin Rodgers
2003-11-25 14:11 ` Reiner Steib
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=yqrad6qos7w.fsf@cs.york.ac.uk \
--to=kester@cs.york.ac.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.
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).