From: Romain FRANCOISE <romain@orebokech.com>
Subject: Re: New variable message-generate-headers-last?
Date: Sat, 12 Apr 2003 22:55:00 +0200 [thread overview]
Message-ID: <87fzonl9ln.fsf@orebokech.com> (raw)
In-Reply-To: <m3smsno3hr.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Sat, 12 Apr 2003 22:38:40 +0200")
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> How about if I just remove intangible and invisible from
> `message-forbidden-properties'?
Would that mean that one could compose a message with invisible text
(e.g. from a cut & paste), and send it as-is without knowing it? If
yes, Message should check the body for text with such special
properties and warn before sending, I think... (I really don't know if
these properties "survive" a cut & paste.)
(Or: in Message buffers, change buffer-invisibility-spec so that only
the '(header) value makes text become invisible, this way text copied
with the invisible property set to t would still be visible.)
> Invisible headers aren't an ideal solution, either, but it's safer, I
> think...
In Larsi we trust. :-)
--
Romain FRANCOISE <romain@orebokech.com> | I'm flooded out with energy,
it's a miracle -- http://orebokech.com/ | energy and deceit.
next prev parent reply other threads:[~2003-04-12 20:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-01 21:24 Sebastian D.B. Krause
2003-04-02 13:22 ` Kai Großjohann
2003-04-02 15:28 ` Sebastian D.B. Krause
2003-04-02 18:16 ` Kai Großjohann
2003-04-12 20:05 ` Lars Magne Ingebrigtsen
2003-04-12 20:23 ` Lars Magne Ingebrigtsen
2003-04-12 20:29 ` Romain FRANCOISE
2003-04-12 20:38 ` Lars Magne Ingebrigtsen
2003-04-12 20:55 ` Romain FRANCOISE [this message]
2003-04-12 20:58 ` Romain FRANCOISE
2003-04-12 21:01 ` Lars Magne Ingebrigtsen
2003-04-12 22:27 ` Sebastian D.B. Krause
2003-04-12 23:22 ` Lars Magne Ingebrigtsen
2003-04-13 8:07 ` Kai Großjohann
2003-04-13 13:29 ` Lars Magne Ingebrigtsen
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=87fzonl9ln.fsf@orebokech.com \
--to=romain@orebokech.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).