Gnus development mailing list
 help / color / mirror / Atom feed
From: Per Abrahamsen <abraham@dina.kvl.dk>
Subject: Re: Wizards (was: Re: Oort Version)
Date: 28 Mar 2001 17:58:59 +0200	[thread overview]
Message-ID: <rj3dbx28cc.fsf@ssv2.dina.kvl.dk> (raw)
In-Reply-To: <vxksnjyc5n3.fsf@cinnamon.vanillaknot.com> (Karl Kleinpaste's message of "28 Mar 2001 09:47:12 -0500")

Karl Kleinpaste <karl@charcoal.com> writes:

> Do you still have the code?  It would be worth looking at today.  Rot
> can be cut out.

It may be in W3.  W3 is build upon the same widget library as
customize, and the primary idea was to have a html tag that expanded
into a customize widget, and the secondary idea was to have Emacs Lisp
as an HTML script language (instead of ECMAscript)...

Hey, I actually have a demo-page from back then!  Look at 

        http://www.dina.kvl.dk/~abraham/custom/gnus.html

with w3 to get an idea of what I was trying to achieve.

W3 *is* FSF signed, but I don't think anyone is working on integrating
it.  W3 need to be a "core feature" of both Emacs and XEmacs for this
approach to be feasible, simple minded customization should not
require any extra packages.

The alternative is to write an ad-hoc markup langauge, which I think
is silly.  I'd much rather have W3 used everywhere. 

> Do you mean by using a long (contorted?) list of alternate selectors?
> That could get really hairy, I would think.  But it would be good for
> a first pass.

I don't understand what you mean, but then again, I have never used
the : or ! features.  It was just a thought.

Maybe the best option would be to drop the fancy split, and write a
third value for nnmail-split-methods, say nnmail-split-common, which
understood some not very flexible but easy to understand options.

The default syntax is very simple, too simple for common tasks.

The recursive nature of nnmail-split-fancy is way cool and very
powerful if you have a CS degree, and utter gibberish if not.

The nnmail-split-common should understand some simple lists
corresponding to common splits.  Maybe junk, people, lists, and other.

> > A problem is that BBDB is FSF code, which makes it problematic to
> ( s/is/isn't/ ?)

Yes.

> So let's provide BBDB auto-graft iff we detect that BBDB is
> available.  Can "require" be wrapped inside "ignore-errors"?

Yes.  It doesn't really interest me though, the vast majorioty of
ordinary users just use what is bundled.

> I wish I had any experience using VM, but I've never once invoked it
> except by accident.

It is a long time since I used VM, but Kyle Jones write beautiful code
with nice and clear apis.  I just wish he would agree to sign papers.

> But how does this interact with users who run >1 simultaneous Emacs?

Badly.


  reply	other threads:[~2001-03-28 15:58 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-26 19:00 Oort Version Jake Colman
2001-03-26 20:05 ` Kai Großjohann
2001-03-26 20:29   ` Karl Kleinpaste
2001-03-27 21:02     ` Simon Josefsson
2001-03-27 21:33       ` Steven E. Harris
2001-03-27 22:29         ` Robin S. Socha
2001-03-28  0:13           ` Karl Kleinpaste
2001-03-28  0:38             ` Colin Marquardt
2001-03-28 18:06               ` Josh Huber
2001-03-28  3:40             ` Simon Josefsson
2001-03-28 18:51               ` Samuel Padgett
2001-03-28  7:13             ` Christoph Conrad
2001-03-28  7:13             ` Christoph Conrad
2001-03-28  7:15             ` Christoph Conrad
2001-03-28  7:21             ` Christoph Conrad
2001-03-28  8:43               ` Christoph Conrad
2001-03-28 13:59             ` Wizards (was: Re: Oort Version) Per Abrahamsen
2001-03-28 14:47               ` Karl Kleinpaste
2001-03-28 15:58                 ` Per Abrahamsen [this message]
2001-03-28 16:34                 ` Paul Jarc
2001-03-28 22:38                 ` Alex Schroeder
2001-03-28 19:03               ` Samuel Padgett

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=rj3dbx28cc.fsf@ssv2.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).