unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Michael Slass <miknrene@drizzle.com>
Subject: Re: (Newbie) How to turn AutoFill-mode on/off
Date: Sun, 24 Nov 2002 21:31:47 GMT	[thread overview]
Message-ID: <m365umsl49.fsf@localhost.localdomain> (raw)
In-Reply-To: mailman.1038163968.29194.help-gnu-emacs@gnu.org

ken <ken@cleveland.lug.net> writes:

>Kai,
>
>Thanks for the introduction.  :)  
>
>Years ago I gave LaTeX a fair try-- much more than a half hour-- and
>came away from it quite unsatisfied.  To my way of thinking, html is
>more intuitive and much easier to write in as well as to read.  
>Moreover, html is the lingua franca of the web and docs so formatted
>drop into it without modification and without need for a plug-in;
>correct me if I'm mistaken, but LaTex docs don't.
>
>Of course LaTeX has its place.  If I were involved in high-end 
>typesetting, I'd definitely revisit it.  But its not the only tool 
>available for formatting documents and not necessarily always the best 
>for every job.
>

No one is arguing either of these points; I believe most of the
contention has been about what degree of complexity of a document
warrants the transition from HTML to LaTeX.  IIRC, in your first post
on this subject, you said that HTML was good for anything up to and
including a master's thesis, and I suspect that common opinion is
against you on this head.  I'm not sure where is a better spot to
plant the arbitrary transition point, but I am sure that it's well
south of the master's thesis.

All the best,

-- 
Mike Slass

  parent reply	other threads:[~2002-11-24 21:31 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-23 19:07 (Newbie) How to turn AutoFill-mode on/off Elaine Sims
2002-11-23 19:30 ` Michael Slass
2002-11-23 19:38   ` Elaine Sims
2002-11-23 19:56     ` Michael Slass
2002-11-23 20:09       ` Elaine Sims
2002-11-24  0:53     ` ken
2002-11-24  2:07       ` Alan Shutko
2002-11-24 14:06         ` ken
2002-11-24 15:06           ` Kai Großjohann
2002-11-24 16:30             ` David Kastrup
2002-11-24 18:51             ` ken
     [not found]             ` <mailman.1038163968.29194.help-gnu-emacs@gnu.org>
2002-11-24 21:31               ` Michael Slass [this message]
2002-11-24 23:19                 ` ken
2002-11-25  4:22                   ` Alan Shutko
2002-11-25  5:50                     ` Eli Zaretskii
2002-11-25  6:03                       ` Eli Zaretskii
     [not found]                     ` <ats@acm.org>
2002-11-25 14:54                       ` Peter S Galbraith
2002-11-25 14:57                     ` Kester Clegg
     [not found]                     ` <mailman.1038236120.7841.help-gnu-emacs@gnu.org>
2002-11-25 15:59                       ` Stefan Monnier <foo@acm.com>
2002-11-25  9:53                   ` Kai Großjohann
2002-11-24 21:33               ` Benjamin Lewis
2002-11-24  4:30       ` Benjamin Lewis
2002-11-25  5:56     ` Jim Janney
2002-11-25 15:01     ` Kester Clegg
     [not found] <mailman.1038203481.9643.help-gnu-emacs@gnu.org>
2002-11-25 11:09 ` Oliver Scholz
2002-11-25 15:08 ` Alan Shutko

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=m365umsl49.fsf@localhost.localdomain \
    --to=miknrene@drizzle.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).