Differences From Artifact [1e7754cff3]:

• File unix/uxpty.c — part of check-in [df1c22fdcb] at 2005-02-06 09:14:34 on branch trunk — Encapsulated most of the pty backend's variables into a proper data structure, in preparation for wanting more than one of them in a single process. This can't be done cleanly, because the whole business with pty_pre_init pre-allocating the pty rather assumes we want a known number of the things before we drop privileges; so there's a horrid hack to make pty_pre_init work on platforms that have at most one pty instance per process, but at the same time things ought to work sensibly with more than one per process _if_ pty_pre_init isn't required. (user: simon size: 24970)

To Artifact [6be3c5c3d6]:

• File unix/uxpty.c — part of check-in [0632fdc578] at 2005-02-06 09:52:00 on branch trunk — Reinstate the broken -e option in pterm. Also I've just worked out a much better way of handling pty_argv which doesn't require uxpty.c to be linked in to Unix PuTTY and PuTTYtel. (user: simon size: 24952)

167
168
169
170
171
172
173
174
175
176
177
178
179
180
181

/*
 * pty_argv is a grievous hack to allow a proper argv to be passed
 * through from the Unix command line. Again, it doesn't really
 * make sense outside a one-pty-per-process setup.
 */
char **pty_argv;
int use_pty_argv;

static void pty_close(Pty pty);

#ifndef OMIT_UTMP
static void setup_utmp(char *ttyname, char *location)
{
#ifdef HAVE_LASTLOG

<

167
168
169
170
171
172
173

174
175
176
177
178
179
180

/*
 * pty_argv is a grievous hack to allow a proper argv to be passed
 * through from the Unix command line. Again, it doesn't really
 * make sense outside a one-pty-per-process setup.
 */
char **pty_argv;


static void pty_close(Pty pty);

#ifndef OMIT_UTMP
static void setup_utmp(char *ttyname, char *location)
{
#ifdef HAVE_LASTLOG