Gnus development mailing list
 help / color / mirror / Atom feed
From: Per Abrahamsen <abraham@dina.kvl.dk>
Subject: Emacs markup language
Date: Tue, 18 May 2004 15:07:09 +0200	[thread overview]
Message-ID: <rjisetc29u.fsf@sheridan.dina.kvl.dk> (raw)

The problem of *not* using w3 for saints is that one have to invent
another markup language, and who want yet another markup language?

But Emacs (and GNU) already has its own simple markup language, namely
Texinfo (it also has info, but info sucks as a markup language, so
let's forget that).  So maybe the way to go would be to create a
texi-browser extended with embedded Emacs Lisp and saint-specific
tags.  We might even start with the "embedded Emacs Lisp and
saint-specific tags", but in a "may eventually grow into a
texi-browser" forward thinking way.




             reply	other threads:[~2004-05-18 13:07 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-18 13:07 Per Abrahamsen [this message]
2004-05-18 14:30 ` Lars Magne Ingebrigtsen
2004-05-18 15:08   ` Jonas Steverud
2004-05-18 15:16     ` Lars Magne Ingebrigtsen
2004-05-18 15:41       ` Timothy Brown
2004-05-18 15:47         ` Lars Magne Ingebrigtsen
2004-05-18 18:41           ` Ted Zlatanov
2004-05-18 19:05             ` Lars Magne Ingebrigtsen
2004-05-18 20:27               ` Ted Zlatanov
2004-05-18 20:45                 ` Lars Magne Ingebrigtsen
2004-05-18 19:07       ` Norman Walsh
2004-05-19 15:16         ` Manoj Srivastava
2004-05-19 18:12           ` Ted Zlatanov
2004-05-19 20:36             ` Steinar Bang
2004-05-20 21:24           ` Kai Grossjohann
2004-05-21  5:41             ` Alex Ott
2004-05-21 14:06             ` Ted Zlatanov
2004-05-24 18:06             ` Norman Walsh
2004-05-24 18:06           ` Norman Walsh
2004-05-18 18:25   ` Group renaming doesn't rename score files Max Froumentin
2004-05-19 23:37     ` Lars Magne Ingebrigtsen
2004-05-20  3:36       ` Kevin Greiner
2004-05-20 16:51         ` Lars Magne Ingebrigtsen

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=rjisetc29u.fsf@sheridan.dina.kvl.dk \
    --to=abraham@dina.kvl.dk \
    /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).