diff options
| -rw-r--r-- | INSTALL | 2 | ||||
| -rw-r--r-- | README.SECURITY | 2 | ||||
| -rw-r--r-- | README.SSL | 2 | ||||
| -rw-r--r-- | TODO | 2 | ||||
| -rw-r--r-- | configure.ac | 2 | ||||
| -rw-r--r-- | curs_lib.c | 2 | ||||
| -rw-r--r-- | help.c | 2 | ||||
| -rw-r--r-- | imap/message.c | 2 | ||||
| -rw-r--r-- | lib.c | 2 | ||||
| -rw-r--r-- | mh.c | 2 |
10 files changed, 10 insertions, 10 deletions
@@ -280,7 +280,7 @@ Solaris 2.6 For the real fix, applying Sun patches # 105490-05 (linker patch) and # 105210-17 (libc and malloc patch) from sunsolve.sun.com has been reported to stop these problems - from occuring. + from occurring. Linux diff --git a/README.SECURITY b/README.SECURITY index 90616328..20d59bd8 100644 --- a/README.SECURITY +++ b/README.SECURITY @@ -19,7 +19,7 @@ While we don't completely agree that this is an actual MUA problem - Backticks are handled specially when preparing % expandos for mailcap entries. This fix will keep the current problem from - occuring, but we are sure there are other possible mailcap entries + occurring, but we are sure there are other possible mailcap entries where this doesn't help. - We have added a configuration variable named $mailcap_sanitize, @@ -97,7 +97,7 @@ each of these, you use the following: openssl s_client -host <imap server> -port <port> -verify -debug -no_ssl2 openssl s_client -host <imap server> -port <port> -verify -debug -no_ssl3 -You can also combine the options until you get a successfull connect. Once +You can also combine the options until you get a successful connect. Once you know which options do not work, you can set the variables for non-working protocols to know. The variables for the protocols are ssl_use_tlsv1, ssl_use_sslv2, and ssl_use_sslv3. @@ -50,7 +50,7 @@ Problems are listed in approximate order of priority. Note: This still requires some thought, since we'd have to store per-entry data in the menu structure. As an alternative, we could extend the tag method to do something to more general flags. The - latter approach would make the implementation of propper + latter approach would make the implementation of proper tag-prefix behaviour more simple: Functions should only be applied when a message is tagged and visible. Additionally, we must not access a menu's max field directly any more: Adding an entry to a diff --git a/configure.ac b/configure.ac index 2e5e9490..324c7584 100644 --- a/configure.ac +++ b/configure.ac @@ -163,7 +163,7 @@ AC_ARG_ENABLE(smime, AS_HELP_STRING([--disable-smime],[Disable SMIME support]), ]) if test x$have_smime != xno ; then - AC_DEFINE(CRYPT_BACKEND_CLASSIC_SMIME, 1, [Define if you want clasic S/MIME support.]) + AC_DEFINE(CRYPT_BACKEND_CLASSIC_SMIME, 1, [Define if you want classic S/MIME support.]) MUTT_LIB_OBJECTS="$MUTT_LIB_OBJECTS smime.o crypt-mod-smime-classic.o" SMIMEAUX_TARGET="smime_keys" fi @@ -958,7 +958,7 @@ int mutt_charlen (const char *s, int *width) /* * mutt_strwidth is like mutt_strlen except that it returns the width - * refering to the number of characters cells. + * referring to the number of character cells. */ int mutt_strwidth (const char *s) @@ -204,7 +204,7 @@ static void format_line (FILE *f, int ismacro, fputs (t1, f); /* don't try to press string into one line with less than 40 characters. - The double paranthesis avoid a gcc warning, sigh ... */ + The double parenthesis avoids a gcc warning, sigh ... */ if ((split = COLS < 40)) { col_a = col = 0; diff --git a/imap/message.c b/imap/message.c index 38da127f..5cfbb1fe 100644 --- a/imap/message.c +++ b/imap/message.c @@ -547,7 +547,7 @@ int imap_fetch_message (MESSAGE *msg, CONTEXT *ctx, int msgno) * IMAP server doesn't know the message has been \Seen. So we capture * the server's notion of 'read' and if it differs from the message info * picked up in mutt_read_rfc822_header, we mark the message (and context - * changed). Another possiblity: ignore Status on IMAP?*/ + * changed). Another possibility: ignore Status on IMAP?*/ read = h->read; newenv = mutt_read_rfc822_header (msg->fp, h, 0, 0); mutt_merge_envelopes(h->env, &newenv); @@ -935,7 +935,7 @@ void mutt_remove_trailing_ws (char *s) /* * Write the concatened pathname (dir + "/" + fname) into dst. - * The slash is ommitted when dir or fname is of 0 length. + * The slash is omitted when dir or fname is of 0 length. * Returns NULL on error or a pointer to dst otherwise. */ char *mutt_concatn_path (char *dst, size_t dstlen, @@ -1583,7 +1583,7 @@ static int mh_rewrite_message (CONTEXT * ctx, int msgno) * number. Mutt does _not_ behave like this. * * Anyway, if this fails, the message is in the folder, so - * all what happens is that a concurrently runnung mutt will + * all what happens is that a concurrently running mutt will * lose flag modifications. */ |