From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: [vms] extending Lisp_Process
Date: Mon, 14 Jul 2003 11:50:03 -0400 [thread overview]
Message-ID: <E19c5aV-0003rt-IY@fencepost.gnu.org> (raw)
In-Reply-To: <E19c0MW-00008L-00@colo.agora-net.com> (message from Thien-Thi Nguyen on Mon, 14 Jul 2003 06:15:16 -0400)
for vms subprocess support, i would like to integrate Richard
Levitte's external VMS_PROC_STUFF structure into the Lisp_Process
structure. is that ok? something like:
struct Lisp_Process
{
#ifdef VMS
struct VMS_PROC_STUFF *vms_proc_stuff;
/* etc */
#endif
/* existing Lisp_Process members here */
};
As long as it's in a VMS conditional, I have no objection.
prev parent reply other threads:[~2003-07-14 15:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-14 10:15 [vms] extending Lisp_Process Thien-Thi Nguyen
2003-07-14 13:37 ` Stefan Monnier
2003-07-14 21:19 ` Thien-Thi Nguyen
2003-07-14 15:50 ` Richard Stallman [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E19c5aV-0003rt-IY@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).