From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: Re: how to handle rtf
Date: Wed, 30 Jul 2014 15:18:44 +0200 [thread overview]
Message-ID: <87egx3ouh7.fsf@debian.uxu> (raw)
In-Reply-To: a05237dd-8488-45e7-887c-8862c7031819@googlegroups.com
renato.pontefice@gmail.com writes:
> No, I need to read, modify eand write .rtf
Why?
There seems to be only problems associated with that
and no advantages.
--
underground experts united
next prev parent reply other threads:[~2014-07-30 13:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-29 13:07 how to handle rtf renato.pontefice
2014-07-29 15:39 ` Danil Orlov
[not found] ` <mailman.6237.1406648406.1147.help-gnu-emacs@gnu.org>
2014-07-29 16:46 ` Emanuel Berg
2014-07-29 17:39 ` Grant Rettke
[not found] ` <mailman.6241.1406655598.1147.help-gnu-emacs@gnu.org>
2014-07-30 8:49 ` Joost Kremers
2014-07-30 8:58 ` renato.pontefice
2014-07-30 13:18 ` Emanuel Berg [this message]
2014-07-30 16:50 ` Rusi
2014-07-30 21:28 ` Emanuel Berg
2014-07-31 10:03 ` renato.pontefice
2014-07-31 10:30 ` Rusi
2014-07-31 13:15 ` renato.pontefice
2014-07-31 15:02 ` Rusi
2014-08-08 12:26 ` Hans BKK
2014-08-08 13:41 ` Eli Zaretskii
2014-08-08 14:09 ` Hans BKK
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=87egx3ouh7.fsf@debian.uxu \
--to=embe8573@student.uu.se \
--cc=help-gnu-emacs@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.
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).