Gnus development mailing list
 help / color / mirror / Atom feed
From: wmperry@aventail.com (William M. Perry)
Cc: ding@gnus.org
Subject: Re: Writing enriched text
Date: 21 Apr 1999 12:51:12 -0500	[thread overview]
Message-ID: <86ogkhhnfz.fsf@kramer.bp.aventail.com> (raw)
In-Reply-To: Oscar Figueiredo's message of "21 Apr 1999 19:29:21 +0200"

Oscar Figueiredo <Oscar.Figueiredo@di.epfl.ch> writes:

> >>>>> "Alan" == Alan Shutko <ats@acm.org> writes:
> 
>   Alan> Kai.Grossjohann@CS.Uni-Dortmund.DE writes:
>   >> Or, we need a way to dissect a buffer into areas each of which is
>   >> edited in a different mode.  OLE, anyone?
> 
>   Alan> We _definately_ need this.  This would make help writing javascript in
>   Alan> html, yacc, lex, web, and tons of other places.  If you figure out how
>   Alan> to do this....
> 
> This has been more or less done already though not exactly as you would
> expect: look for "indirect buffers" in Emacs 20.something and XEmacs 21.2

What would be ideal is if you could change the syntax table and keymaps in
an extent/text property region.  I know you can do this for keymaps, but I
don't think you can durrently to it for syntax tables.

Then instead of an indirect _buffer_, you would have a region of the buffer
that would in effect be in 'sgml-mode' or 'enriched-mode'.  But you would
still really want the bindings of 'message-mode' to be in effect, so this
points to using minor modes instead of mixing major ones... hmmmm :(

We just need really studly minor mode versions of sgml-mode and
enriched-mode that integrate really well with mail-mode or message-mode.

-Bill P.


  reply	other threads:[~1999-04-21 17:51 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-04-20 20:55 François Pinard
1999-04-20 21:26 ` Colin Rafferty
1999-04-20 21:43   ` Hrvoje Niksic
1999-04-20 21:44   ` François Pinard
1999-04-21 13:49     ` Colin Rafferty
1999-04-21 14:09       ` Kai.Grossjohann
1999-04-21 14:43         ` Colin Rafferty
1999-04-22 15:04           ` Kai.Grossjohann
1999-04-22 15:24             ` Colin Rafferty
1999-04-22 16:01               ` Kai.Grossjohann
1999-04-23 12:56             ` Hrvoje Niksic
1999-04-23 13:25               ` Kai.Grossjohann
1999-04-23 13:37                 ` Hrvoje Niksic
1999-04-23 14:58                   ` William M. Perry
1999-04-23 15:45                     ` Per Abrahamsen
1999-04-22 15:55           ` Jan Vroonhof
     [not found]           ` <vaf676o7l3p.fsf@ramses.cs.uni-dortmund.de <byd80whcpl.fsf@bolzano.math.ethz.ch>
1999-04-22 16:54             ` Colin Rafferty
1999-04-20 21:52   ` David Hedbor
1999-04-20 22:42     ` Hrvoje Niksic
1999-04-20 23:08       ` Bruce Stephens
1999-04-20 23:20         ` David Hedbor
1999-04-21  0:04   ` enriched bug (was Re: Writing enriched text) Stainless Steel Rat
1999-04-21  0:08     ` Hrvoje Niksic
1999-04-22  7:52   ` Can't read this! " Jaap-Henk Hoepman
1999-04-22  9:09     ` Lee Willis
1999-04-23 14:50       ` Justin Sheehy
1999-04-21  7:26 ` Writing enriched text Kai.Grossjohann
1999-04-21 12:48   ` William M. Perry
1999-04-21 13:43     ` Laura Conrad
1999-04-21 13:45     ` Kai.Grossjohann
1999-04-21 15:03       ` Alan Shutko
1999-04-21 17:29         ` Oscar Figueiredo
1999-04-21 17:51           ` William M. Perry [this message]
1999-04-22 15:01           ` Kai.Grossjohann
1999-04-23 20:39             ` François Pinard
1999-04-25 18:17             ` Hrvoje Niksic
1999-04-25 21:34               ` Kai.Grossjohann
1999-04-21 19:08       ` Lars Magne Ingebrigtsen
1999-04-21 21:41         ` Hrvoje Niksic
1999-04-22  7:24           ` Colin Marquardt
1999-04-22  8:41             ` Hrvoje Niksic
1999-04-22 15:37           ` Jan Vroonhof
     [not found]           ` <k8z <byiuaohdim.fsf@bolzano.math.ethz.ch>
1999-04-23  7:42             ` Colin Marquardt
1999-04-23 20:44           ` François Pinard
1999-04-25 18:14             ` Hrvoje Niksic
     [not found]     ` <knn202ks3v.fsf@concord.com>
1999-04-21 14:22       ` William M. Perry
1999-04-24 15:17   ` François Pinard

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=86ogkhhnfz.fsf@kramer.bp.aventail.com \
    --to=wmperry@aventail.com \
    --cc=ding@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).