diff options
author | Eduardo Chappa <chappa@washington.edu> | 2020-01-16 08:29:04 -0700 |
---|---|---|
committer | Eduardo Chappa <chappa@washington.edu> | 2020-01-16 08:29:04 -0700 |
commit | afbf1ef03d944a775cafbc02243f8eb8c15d096e (patch) | |
tree | 9b04017bf26a601a0a867fdd45dce94c2897827a /pith | |
parent | a6feb748e22af1b8cf032c08e91c2424c44ebd62 (diff) | |
download | alpine-afbf1ef03d944a775cafbc02243f8eb8c15d096e.tar.xz |
* Fix a few more misspellings in the source code of Alpine.
List contributed by Jens Schleusener.
Diffstat (limited to 'pith')
-rw-r--r-- | pith/mailview.c | 4 | ||||
-rw-r--r-- | pith/osdep/pw_stuff.c | 2 | ||||
-rw-r--r-- | pith/pattern.c | 2 | ||||
-rw-r--r-- | pith/pine.hlp | 2 | ||||
-rw-r--r-- | pith/save.c | 2 | ||||
-rw-r--r-- | pith/string.c | 2 |
6 files changed, 7 insertions, 7 deletions
diff --git a/pith/mailview.c b/pith/mailview.c index a56dd1d3..383d9b13 100644 --- a/pith/mailview.c +++ b/pith/mailview.c @@ -1289,7 +1289,7 @@ format_env_hdr(MAILSTREAM *stream, long int msgno, char *section, ENVELOPE *env, * occurrence of header "field". Set "start" to that. Set "end" to point one * position past all of the continuation lines that go with "field". * That is, if "end" is converted to a null - * character then the string "start" will be the next occurence of header + * character then the string "start" will be the next occurrence of header * "field" including all of its continuation lines. Assume we * have CRLF's as end of lines. * @@ -2466,7 +2466,7 @@ format_header(MAILSTREAM *stream, long int msgno, char *section, ENVELOPE *env, } else{ /* - * Go through h finding all occurences of this header + * Go through h finding all occurrences of this header * and all continuation lines, and output. */ for(current = h; diff --git a/pith/osdep/pw_stuff.c b/pith/osdep/pw_stuff.c index 8938f77c..328a0b93 100644 --- a/pith/osdep/pw_stuff.c +++ b/pith/osdep/pw_stuff.c @@ -35,7 +35,7 @@ static char *gcos_name(char *, char *); Pull the name out of the gcos field if we have that sort of /etc/passwd Args: gcos_field -- The long name or GCOS field to be parsed - logname -- Replaces occurences of & with logname string + logname -- Replaces occurrences of & with logname string Result: returns pointer to buffer with name ----*/ diff --git a/pith/pattern.c b/pith/pattern.c index 9b47d411..028111cd 100644 --- a/pith/pattern.c +++ b/pith/pattern.c @@ -6166,7 +6166,7 @@ calc_extra_hdrs(void) pat; pat = next_pattern(&pstate)){ /* - * This section wouldn't be necessary if sender was retreived + * This section wouldn't be necessary if sender was retrieved * from the envelope. But if not, we do need to add it. */ if(pat->action && pat->action->scorevalhdrtok diff --git a/pith/pine.hlp b/pith/pine.hlp index bc688725..a2146ccc 100644 --- a/pith/pine.hlp +++ b/pith/pine.hlp @@ -140,7 +140,7 @@ with help text for the config screen and the composer that didn't have any reasonable place to be called from. Dummy change to get revision in pine.hlp ============= h_revision ================= -Alpine Commit 386 2020-01-15 21:41:23 +Alpine Commit 389 2020-01-16 08:24:51 ============= h_news ================= <HTML> <HEAD> diff --git a/pith/save.c b/pith/save.c index 1065fc5d..9265b760 100644 --- a/pith/save.c +++ b/pith/save.c @@ -1711,7 +1711,7 @@ save_ex_output_line(char *line, long unsigned int *len, gf_io_t pc) /*---------------------------------------------------------------------- Save() helper function to create canonical date string from given header - Args: date -- buf to recieve canonical date string + Args: date -- buf to receive canonical date string header -- rfc822 header to fish date string from Result: date filled with canonicalized date in header, or null string diff --git a/pith/string.c b/pith/string.c index 92a9a65c..ff17e505 100644 --- a/pith/string.c +++ b/pith/string.c @@ -1093,7 +1093,7 @@ The following date formats are accepted: DD MM WKDAY YY MM HH:MM:SS ZZ All leading, intervening and trailing spaces tabs and commas are ignored. -The prefered formats are the first or second ones. If a field is unparsable +The preferred formats are the first or second ones. If a field is unparsable it's value is left as -1. ----*/ |