From: Hans Hagen <pragma@wxs.nl>
Cc: Giuseppe Bilotta <bourbaki@bigfoot.com>, ntg-context@ntg.nl
Subject: Re: A proposal for the sectioning commands--addendum
Date: Sun, 23 Jun 2002 21:39:21 +0200 [thread overview]
Message-ID: <5.1.0.14.1.20020623213307.034094c0@server-1> (raw)
In-Reply-To: <200206211201.27913.john@wexfordpress.com>
At 12:01 PM 6/21/2002 -0400, John Culleton wrote:
> > * in editors that allow folding: proper folding of whole sections.
> >
> > Hans, do you think you can implement this easily?
>Addendum to my previous comments:
>
>I use folding in GVim by putting a ``stop'' command just before each
>``start'' commnad. this is clumsy but it is easier to remember than what
>Bilotti proposes. Better would be an editor that did this kind of controlling
>automatically. Here is a sample of what I must do currently:
>
>%--1
>\chapter{The Best of Breed Software Packages}
>%++1
>%--2
>\section{Operating Systems}
>%++2
>%--3
>\subsection{Linux}
>%++3
>
>The above is not elegant but with the proper setup in .vimrc it works.
>
>I perhaps need to create a Vim macro that would put the befores and afters
>on the tags. (e.g. %--2 before and %++2 after)
>
>Incidentally I use Context not because it is ``structured'' but because it
>implements features not found in other incarnations of TeX, like hanging
>punctuation and sidebars.
right from the start the context syntax has been influenced and has
influenced the way we edit texts; here we use texedit which we wrote long
ago (in modula 2); due to some problems under win2k (the os2 mem model is
no longer supported so we cannot run sub jobs) we've rewritten this editor
in perl/tk. We're now in the process of switching. Since this editor is
under my control, i can tune it a bit to context and vise versa. Structure
based navigation is part of the game.
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
information: http://www.pragma-ade.com/roadmap.pdf
documentation: http://www.pragma-ade.com/showcase.pdf
-------------------------------------------------------------------------
next prev parent reply other threads:[~2002-06-23 19:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-21 13:46 A proposal for the sectioning commangs Giuseppe Bilotta
2002-06-21 15:27 ` John Culleton
2002-06-21 21:15 ` Re[2]: " Giuseppe Bilotta
2002-06-21 22:37 ` Duncan Hothersall
2002-06-22 2:24 ` John Culleton
2002-06-23 21:47 ` Re[2]: " Hans Hagen
2002-06-23 10:45 ` Hans Hagen
2002-06-21 16:01 ` A proposal for the sectioning commands--addendum John Culleton
2002-06-21 21:17 ` Re[2]: " Giuseppe Bilotta
2002-06-23 19:39 ` Hans Hagen [this message]
2002-06-23 21:42 ` Giuseppe Bilotta
2002-06-24 8:40 ` Hans Hagen
2002-06-24 8:55 ` Re[3]: " Giuseppe Bilotta
2002-06-24 18:06 ` texedit (was: something else) Henning Hraban Ramm
2002-06-25 15:47 ` Hans Hagen
2002-06-26 18:43 ` Henning Hraban Ramm
2002-06-27 16:54 ` Hans Hagen
2002-06-28 21:48 ` Henning Hraban Ramm
2002-06-23 10:43 ` A proposal for the sectioning commangs Hans Hagen
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=5.1.0.14.1.20020623213307.034094c0@server-1 \
--to=pragma@wxs.nl \
--cc=bourbaki@bigfoot.com \
--cc=ntg-context@ntg.nl \
/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).