all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: David Bremner <david@tethera.net>
Cc: 18513@debbugs.gnu.org,
	Daniel Kahn Gillmor <dkg@fifthhorseman.net>,
	Daiki Ueno <ueno@gnu.org>
Subject: bug#18513: 24.3; message-mode sends unencrypted on error
Date: Mon, 23 Sep 2019 15:53:50 +0200	[thread overview]
Message-ID: <87ftkn6rv5.fsf@gnus.org> (raw)
In-Reply-To: <877e5zjjdh.fsf@tethera.net> (David Bremner's message of "Mon, 23 Sep 2019 09:18:50 -0300")

David Bremner <david@tethera.net> writes:

> I don't think the fact that we can't do a perfect job is a reason not to
> improve the error checking. There are many errors that can be detected
> that currently are not. Is erroring on an unknown mml tag (which
> nonethless actually looks like a tag) actually difficult?

It's not difficult to bug out on <#unknown>, but since Message mode
buffers mostly free text, doing so would lead to people having their
emails fail if they were to type such a thing by hand.  MML is only
recognised if it's one of the keywords it er recognises.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2019-09-23 13:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-20  6:12 bug#18513: 24.3; message-mode sends unencrypted on error David Bremner
2014-09-29 11:09 ` Daiki Ueno
2014-09-29 12:14   ` David Bremner
2014-09-30  1:36     ` Daiki Ueno
2019-09-23 11:46     ` Lars Ingebrigtsen
2019-09-23 12:18       ` David Bremner
2019-09-23 13:53         ` Lars Ingebrigtsen [this message]
2019-09-24 10:49           ` Daniel Kahn Gillmor
2019-09-25 13:05             ` Lars Ingebrigtsen
2014-10-01  1:28   ` Glenn Morris
2014-10-01  2:32     ` Daiki Ueno

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=87ftkn6rv5.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=18513@debbugs.gnu.org \
    --cc=david@tethera.net \
    --cc=dkg@fifthhorseman.net \
    --cc=ueno@gnu.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.