From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: New variable message-generate-headers-last?
Date: Sat, 12 Apr 2003 23:01:23 +0200 [thread overview]
Message-ID: <m365pjo2fw.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <87fzonl9ln.fsf@orebokech.com>
Romain FRANCOISE <romain@orebokech.com> writes:
> 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...
There is already such a check in Message -- it will make the text
visible, and then query the user before sending. It would be nicer
to make the text be visible at once, though.
Instead of removing invisible and intangible from the list, I could
make the unhiding hook function just ignore the text that's marked
with `message-hidden', which is the case for the hidden header stuff.
Yes, I think I'll do that.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2003-04-12 21:01 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
2003-04-12 20:58 ` Romain FRANCOISE
2003-04-12 21:01 ` Lars Magne Ingebrigtsen [this message]
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=m365pjo2fw.fsf@quimbies.gnus.org \
--to=larsi@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).