From: "Pseudo" <cradate@yahoo.de>
Subject: Re: Emacs 'destroys' latex files
Date: 17 Jan 2007 05:52:41 -0800 [thread overview]
Message-ID: <1169041961.753070.106780@s34g2000cwa.googlegroups.com> (raw)
In-Reply-To: <mailman.3196.1169036509.2155.help-gnu-emacs@gnu.org>
Hi Nikos,
removing the whole packet causes of course least trouble. That's what I
did :=)
Cheers! Pseudo
next prev parent reply other threads:[~2007-01-17 13:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-16 16:30 Emacs 'destroys' latex files Pseudo
2007-01-16 16:59 ` Maarten Bergvelt
2007-01-16 18:38 ` Pseudo
2007-01-16 18:55 ` Maarten Bergvelt
2007-01-17 2:35 ` Nikos Apostolakis
[not found] ` <mailman.3177.1169001640.2155.help-gnu-emacs@gnu.org>
2007-01-17 9:53 ` Pseudo
2007-01-17 12:21 ` Nikos Apostolakis
[not found] ` <mailman.3196.1169036509.2155.help-gnu-emacs@gnu.org>
2007-01-17 13:52 ` Pseudo [this message]
2007-01-16 22:49 ` David Kastrup
2007-01-16 18:36 ` Peter Dyballa
2007-01-18 3:12 ` Stefan Monnier
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=1169041961.753070.106780@s34g2000cwa.googlegroups.com \
--to=cradate@yahoo.de \
/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).