procyberian/emacs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

(main) [HAVE_SOCKETS]: Use two separate stdio

Browse source 
streams, one for sending and one for reading the reply.
This commit is contained in:
Richard M. Stallman 1996-07-23 14:18:34 +00:00
parent 236ebf3525
commit 23a7488dea
1 changed files with 21 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

29
lib-src/emacsclient.c
View file

@ -63,7 +63,7 @@ main (argc, argv)
{
char system_name[32];
int s, i;
FILE *out;
FILE *out, *in;
struct sockaddr_un server;
char *homedir, *cwd, *str;
char string[BUFSIZ];
@ -132,6 +132,8 @@ main (argc, argv)
perror ("connect");
exit (1);
}
/* We use the stream OUT to send our command to the server. */
if ((out = fdopen (s, "r+")) == NULL)
{
fprintf (stderr, "%s: ", argv[0]);
@ -139,6 +141,18 @@ main (argc, argv)
exit (1);
}
/* We use the stream IN to read the response.
We used to use just one stream for both output and input
on the socket, but reversing direction works nonportably:
on some systems, the output appears as the first input;
on other systems it does not. */
if ((in = fdopen (s, "r+")) == NULL)
{
fprintf (stderr, "%s: ", argv[0]);
perror ("fdopen");
exit (1);
}
#ifdef BSD
cwd = getwd (string);
#else
@ -170,15 +184,14 @@ main (argc, argv)
printf ("Waiting for Emacs...");
fflush (stdout);
rewind (out); /* re-read the output */
str = fgets (string, BUFSIZ, out);
printf ("\n");
/* Now, wait for an answer and print any messages. */
/* Now, wait for an answer and print any messages. On some systems,
the first line we read will actually be the output we just sent.
We can't predict whether that will happen, so if it does, we
detect it by recognizing `Client: ' at the beginning. */
while (str = fgets (string, BUFSIZ, out))
while (str = fgets (string, BUFSIZ, in))
printf ("%s", str);
return 0;
}