Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Emacs markup language
Date: Tue, 18 May 2004 16:30:35 +0200	[thread overview]
Message-ID: <m33c5x4xkk.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <rjisetc29u.fsf@sheridan.dina.kvl.dk>

Per Abrahamsen <abraham@dina.kvl.dk> writes:

> 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). 

That's an idea...  let's see

@title Configuring Gnus for reading news
@node Server name and port
@variable server :string (gnus-getenv-nntpserver)
@variable port :number 119
@validate
(let ((stream
        (condition-case err
           (open-network-stream "nntpd" nil server port)
          (error (setq error err)))))
   (if (memq (process-status stream) '(open run))
       (progn
         (delete-process stream)
         t)
     nil)))
@end validate
@result gnus-select-method (list server port)
@text
To read Usenet news with Gnus, you first have to tell
Gnus where the news server is.

The server name is @variable{server}; port number @variable{port}.
@end text


That was kinda pleasant to write, actually, and it's readable (and
therefore maintainable). 

And when there's a branch (when setting up mail, between pop and
file, say), we could have

@next Pop
@next Local file access

with different nodes called that, of course.

And each assistant would be in its own file, so that'd be the "name
space" that we're talking about.  .ass probably isn't the best suffix
to use, though.  .ast?  .fry?

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen




  reply	other threads:[~2004-05-18 14:30 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-18 13:07 Per Abrahamsen
2004-05-18 14:30 ` Lars Magne Ingebrigtsen [this message]
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=m33c5x4xkk.fsf@quimbies.gnus.org \
    --to=larsi@gnus.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 NNTP newsgroup(s).