From: Lloyd Zusman <ljz@asfast.com>
Subject: Another proposal about `mml-parse'.
Date: 22 Dec 2000 21:15:14 -0500 [thread overview]
Message-ID: <lt3dffq3wt.fsf@asfast.com> (raw)
In thinking about how I'd like to use the `mml-parse' function within
`mml-secure-part', it occurs to me that it would be useful to make use
of another entry within structure that `mml-parse' returns in addition
to `sign', `encrypt', and `contents'. I'd like to propose that along
with `contents' there be an entry named `location' or something
similar, whose value would be the point at which the mml tag appears
within the message buffer.
With this piece of information, it would then be very easy to use
`mml-parse' to locate the `#part' tags that contain the mml directives
that separate the message buffer, thereby making it easy to alter or
delete these tags, if desired. Since `mml-parse-1' (the helper
function for `mml-parse') already knows the exact points at which the
mml tags exist, it seems to me that it would be very easy for this
extra `location' information to be added to the results of
`mml-parse'.
Thoughts?
By the way, I forgot to mention this in my previous message concerning
`mml-parse': I'm planning to make all the changes I'm discussing here,
after I get feedback from all of you; and then I'll post the patches
here.
--
Lloyd Zusman
ljz@asfast.com
next reply other threads:[~2000-12-23 2:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-23 2:15 Lloyd Zusman [this message]
2000-12-23 15:46 ` Simon Josefsson
2000-12-24 2:34 ` Lloyd Zusman
2000-12-25 1:50 ` First patch affecting `mml-parse' (was: Another proposal about `mml-parse'.) Lloyd Zusman
2000-12-25 2:11 ` Simon Josefsson
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=lt3dffq3wt.fsf@asfast.com \
--to=ljz@asfast.com \
/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).