alx/mu4e
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

* mu-cmd-server.c: add ugly work-around to ensure emacs interprets messages at once

Browse Source
This commit is contained in:
djcb
2011-10-18 10:40:41 +01:00
parent f51e78066e
commit 2010df4dad
1 changed files with 17 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
src/mu-cmd-server.c
View File

@ -668,6 +668,7 @@ cmd_view (MuStore *store, GSList *args, GError **err)
unsigned docid; unsigned docid;
char *sexp; char *sexp;
if (!check_param_num (args, 1, 1)) if (!check_param_num (args, 1, 1))
return server_error (NULL, MU_ERROR_IN_PARAMETERS, return server_error (NULL, MU_ERROR_IN_PARAMETERS,
"message <docid> <view|reply|forward>"); "message <docid> <view|reply|forward>");
@ -687,6 +688,22 @@ cmd_view (MuStore *store, GSList *args, GError **err)
send_expr ("(:view %s)\n", sexp); send_expr ("(:view %s)\n", sexp);
/* ugly, ugly... emacs reads/processes the data from the
* server in up-to 4096 byte blobs (see read_process_output in
* the emacs source code), and for longer messages, it may
* only start processing (showing) the message after more data
* comes, instead of immediately. As a work-around for this,
* here, we just send some 'filler data' as to 'flush the
* pipe', so to speak. hopefully, one day I can come up with a
* more elegant way to do this...*/
if (strlen (sexp) > 4000) {
int i;
const char* filler = ";; \n";
for (i = 0; i != 8; ++i)
write (fileno(stdout), filler, strlen (filler));
}
g_free (sexp); g_free (sexp);
return MU_OK; return MU_OK;