From: Peter Dyballa <Peter_Dyballa@Web.DE>
To: Pierre Lorenzon <devel@pollock-nageoire.net>, psdc1978@gmail.com
Cc: GNU Emacs List <help-gnu-emacs@gnu.org>
Subject: Re: Useful key sequences for latex in emacs
Date: Wed, 16 Mar 2011 20:20:46 +0100 [thread overview]
Message-ID: <B1EDE271-7738-437E-8DEE-D40B0161EC00@Web.DE> (raw)
In-Reply-To: <20110317.001209.488384143.devel@pollock-nageoire.net>
Am 17.03.2011 um 01:12 schrieb Pierre Lorenzon:
> A lot of key sequences will be made available by auctex for inserting
> commands, environements etc ...
And AUCTeX even ask for parameters or input!
--
Greetings
Pete
"Evolution" o __o _o _
°\___o /0~ -\<, ^\___ /=\\_/-%
oo~_______ /\ /\______/ \_________O/ O_______________o===>-->O--o____
next prev parent reply other threads:[~2011-03-16 19:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-16 10:45 Useful key sequences for latex in emacs Pedro Costa
2011-03-16 21:51 ` Steve Revilak
2011-03-17 0:12 ` Pierre Lorenzon
2011-03-16 19:20 ` Peter Dyballa [this message]
2011-03-16 19:23 ` Henri-Paul Indiogine
2011-03-16 22:56 ` Suvayu Ali
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=B1EDE271-7738-437E-8DEE-D40B0161EC00@Web.DE \
--to=peter_dyballa@web.de \
--cc=devel@pollock-nageoire.net \
--cc=help-gnu-emacs@gnu.org \
--cc=psdc1978@gmail.com \
/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).