From: Martin Jambon <martin_jambon@emailuser.net>
To: skaller <skaller@ozemail.com.au>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Printing text with holes
Date: Tue, 30 Sep 2003 19:48:20 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.40.0309301909590.2454-100000@pc-bioinfo1> (raw)
In-Reply-To: <1064879263.4015.139.camel@pelican>
On 30 Sep 2003, skaller wrote:
> You have it easy. You're mainly concerned with nice line breaks.
> Consider if you were formatting a plain text table and needed
> to have a view of *column* positions. That's where you start
> renaming all your variables to exactly 4 letters so you can check
> that things line up vertically .. :)
>
> I have this kind of problem (vaguely) in Felix and the only
> solution I found was "suck it and see".
>
> [I'm generating C++ and I want the output layout to look nice ..]
So we need some kind of WYSIWYG editors.
Imagine your source code contains "special regions", that you can edit
using a custom WYSIaWYG editor (what you see is almost what you get),
called from your favorite text editor.
Maybe it would be enough to specify line-breaking keywords and tabulation
marks to generate a minimalist WYSIaWYG editor.
(*BEGIN { tabs = [Before "<td>"; Before "<th>"; Before "</tr>"];
newlines = [After "<br>"; After "</tr>"] } *)
<table>
<tr><th>$header_number_1</th><th>$short</th></tr>
<tr><td>$x</td><td>$y</td></tr>
</table>
(*END *)
would be displayed as:
<table>
<tr><th>$header_number_1</th><th>$short</th></tr>
<tr><td>$x</td> <td>$y</td> </tr>
</table>
(+ syntax highlighting for fake spaces, insertions, keywords, ...)
-- Martin
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2003-09-30 17:49 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-29 13:16 Martin Jambon
2003-09-29 14:10 ` Christian Lindig
2003-09-29 16:25 ` Benjamin Geer
2003-09-29 16:39 ` Brian Hurt
2003-09-29 17:45 ` Jean-Marc EBER
2003-09-29 18:22 ` Brian Hurt
2003-09-29 20:48 ` Pierre Weis
2003-09-29 21:52 ` Richard Jones
2003-09-29 22:07 ` Fred Yankowski
2003-09-29 22:14 ` Daniel M. Albro
2003-09-29 22:19 ` Richard Jones
2003-09-29 22:23 ` Matthieu Sozeau
2003-09-30 3:56 ` Brian Hurt
2003-09-30 4:40 ` Brian Hurt
2003-09-30 6:11 ` David Brown
2003-09-29 18:57 ` Martin Jambon
2003-09-29 21:25 ` Pierre Weis
2003-09-30 12:52 ` skaller
2003-09-30 17:48 ` Martin Jambon [this message]
2003-09-29 18:16 ` Richard Jones
2003-09-29 17:00 ` Pierre Weis
2003-09-29 17:03 ` Karl Zilles
2003-09-29 21:47 ` Pierre Weis
2003-09-30 7:20 ` Jean-Christophe Filliatre
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=Pine.LNX.4.40.0309301909590.2454-100000@pc-bioinfo1 \
--to=martin_jambon@emailuser.net \
--cc=caml-list@inria.fr \
--cc=skaller@ozemail.com.au \
/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