/* Ok, the difference between send and receive:
* recv: BODY->filename is a suggested name, and Context|HEADER points
- * to the attachment in mailbox which is encooded
+ * to the attachment in mailbox which is encoded
* send: BODY->filename points to the un-encoded file which contains the
* attachment
*/
mutt_parse_mime_message (Context, cur);
mutt_message_hook (Context, cur, M_MESSAGEHOOK);
- /* see if crytpo is needed for this message. if so, we should exit curses */
+ /* see if crypto is needed for this message. if so, we should exit curses */
if (WithCrypto && cur->security)
{
if (cur->security & ENCRYPT)
#include <stdlib.h>
#include <sys/wait.h>
-/* Invokes a commmand on a pipe and optionally connects its stdin and stdout
+/* Invokes a command on a pipe and optionally connects its stdin and stdout
* to the specified handles.
*/
pid_t
/* This function allows the user to specify a command to read stdout from in
place of a normal file. If the last character in the string is a pipe (|),
- then we assume it is a commmand to run instead of a normal file. */
+ then we assume it is a command to run instead of a normal file. */
FILE *mutt_open_read (const char *path, pid_t *thepid)
{
FILE *f;
if (WithCrypto && msg->security)
{
/*
- * When reypling / forwarding, use the original message's
+ * When replying / forwarding, use the original message's
* crypto system. According to the documentation,
* smime_is_default should be disregarded here.
*
* don't want to do this when:
* 1) we are sending a key/cert
* 2) we are forwarding a message and the user doesn't want to edit it.
- * This is controled by the quadoption $forward_edit. However, if
+ * This is controlled by the quadoption $forward_edit. However, if
* both $edit_headers and $autoedit are set, we want to ignore the
* setting of $forward_edit because the user probably needs to add the
* recipients.