mirror of
https://git.tartarus.org/simon/putty.git
synced 2025-01-09 17:38:00 +00:00
Fix a few 'triple letter in place of double' typos.
A user wrote in to point out the one in winhandl.c, and out of sheer curiosity, I grepped the whole source base for '([a-zA-Z])\1\1' to see if there were any others. Of course there are a lot of perfectly sensible ones, like 'www' or 'Grrr', not to mention any amount of 0xFFFF and the iiii/bbbb emphasis system in Halibut code paragraphs, but I did spot one more in the recently added udp.but section on traits, and another in a variable name in uxagentsock.c.
This commit is contained in:
parent
7c27cdc16e
commit
f7adf7bca0
@ -778,7 +778,7 @@ or other of the subtypes depending on what it finds out about the
|
||||
machine it's running on. That top-level selector vtable is nearly
|
||||
always the one used by client code. (Except for the test suite, which
|
||||
has to instantiate both of the subtypes in order to make sure they
|
||||
both passs the tests.)
|
||||
both pass the tests.)
|
||||
|
||||
\lcont{
|
||||
|
||||
|
@ -16,7 +16,7 @@ Socket *platform_make_agent_socket(
|
||||
Plug *plug, const char *dirprefix, char **error, char **name)
|
||||
{
|
||||
char *username, *socketdir, *socketname, *errw;
|
||||
const char *errr;
|
||||
const char *err;
|
||||
Socket *sock;
|
||||
|
||||
*name = NULL;
|
||||
@ -35,8 +35,8 @@ Socket *platform_make_agent_socket(
|
||||
|
||||
socketname = dupprintf("%s/pageant.%d", socketdir, (int)getpid());
|
||||
sock = new_unix_listener(unix_sock_addr(socketname), plug);
|
||||
if ((errr = sk_socket_error(sock)) != NULL) {
|
||||
*error = dupprintf("%s: %s\n", socketname, errr);
|
||||
if ((err = sk_socket_error(sock)) != NULL) {
|
||||
*error = dupprintf("%s: %s\n", socketname, err);
|
||||
sk_close(sock);
|
||||
sfree(socketname);
|
||||
rmdir(socketdir);
|
||||
|
@ -201,7 +201,7 @@ static DWORD WINAPI handle_input_threadfunc(void *param)
|
||||
}
|
||||
|
||||
/*
|
||||
* This is called after a succcessful read, or from the
|
||||
* This is called after a successful read, or from the
|
||||
* `unthrottle' function. It decides whether or not to begin a new
|
||||
* read operation.
|
||||
*/
|
||||
|
Loading…
Reference in New Issue
Block a user