Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Tim X <timx@nospam.dev.null>
Subject: Re: How many use eMacs and Gnus on daily basis?
Date: Fri, 09 Jun 2006 18:27:10 +1000	[thread overview]
Message-ID: <87mzcmka3l.fsf@tiger.rapttech.com.au> (raw)
In-Reply-To: <ufyig1n2l.fsf@verizon.net>

Joe Fineman <joe_f@verizon.net> writes:

> me@privacy.net writes:
>
>> I'm curious what you do with emacs
>
> All personal & business writing & recordkeeping.
>
>> and gNus
>
> Email & newsgroups.
>
> Things I cannot yet do with Emacs:
>
> 1.  Deal with the Web.  I use w3m for one site that is all text, but
>     it is rather clunky, and I have not yet found out how to access
>     graphics with it.
>

Yes, this is an area where emacs is not as good as I wish. I use a
combination of w3m and w3. However, you can use the browse-url package
so that when you click on links or open html files, it all happens in
firefox (or mozilla or gaeleaon or whatever). 

> 2.  Edit Word .doc files.  I wish someone would reverse-engineer Word
>     to the extent of making it possible to edit the files in Emacs
>     without corrupting them.

Yes, word can be a bit of an issue. I use wv to convert word files
into either text or html. However, I noticed on the gnu.emacs.sources
list the other day someone is working on an ODF (open document format)
for emacs - this is what open office uses. Ultimately, this could
allow you to create documents in emacs and then use open office to
convert them into word files. 

Personally, I tell people not to send me word documents and when they
do, I tell them they need to convert them into pdf or some other open
format if they want me to read them. Not always a popular thing to do,
but so far I've managed to get away with it.

> -- 
Tim


-- 
tcross (at) rapttech dot com dot au

      parent reply	other threads:[~2006-06-09  8:27 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-07 14:34 me
2006-06-07 14:41 ` Hadron Quark
2006-06-07 15:05   ` me
2006-06-07 15:19     ` Hadron Quark
2006-06-07 15:40     ` Mark T.B. Carroll
2006-06-09  8:17       ` Tim X
2006-06-09  9:46         ` rambam
2006-06-07 15:46     ` Ted Zlatanov
2006-06-07 15:46     ` Malte Spiess
2006-06-09  8:13     ` Tim X
2006-06-09 13:49       ` me
2006-06-07 14:50 ` Mark T.B. Carroll
2006-06-07 15:48 ` David Z Maze
2006-06-07 15:49 ` Robert D. Crawford
2006-06-07 17:49   ` notbob
2006-06-08  8:09     ` Glyn Millington
2006-06-10  6:41   ` Joe Bush
2006-06-10  9:17     ` Tim X
2006-06-10 20:01     ` Robert D. Crawford
2006-06-12 17:27       ` Joe Bush
2006-06-08  0:57 ` Joe Fineman
2006-06-08  1:17   ` Bastien
2006-06-08  1:40   ` Johan Bockgård
2006-06-08  6:18     ` David Kastrup
2006-06-08  1:59   ` Robert D. Crawford
2006-06-08  3:03   ` me
2006-06-08 14:30     ` David Z Maze
2006-06-08 14:57       ` David Kastrup
2006-06-08 17:58       ` notbob
2006-06-08 18:33         ` David Kastrup
2006-06-08 14:46     ` Eric Eide
2006-06-09  8:27   ` Tim X [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87mzcmka3l.fsf@tiger.rapttech.com.au \
    --to=timx@nospam.dev.null \
    /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 NNTP newsgroup(s).