From: vroonhof@math.ethz.ch
Cc: ding@ifi.uio.no
Subject: Re: emacsclient + w3 = ?
Date: Thu, 14 Dec 1995 11:16:58 +0100 [thread overview]
Message-ID: <199512141016.LAA01016@goedel.math.ethz.ch> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of 14 Dec 1995 09:32:46 +0100
>>>>> "Lars" == Lars Magne Ingebrigtsen <larsi@ifi.uio.no> writes:
BTW Supercite complained about "Mail header From Ding not RFC-compliant" or
something like that when citing this.
Lars> Now, I've looked at the emacsclient thingie, and it seems
Lars> that emacsclient just delivers some string to the Emacs
Lars> server. This string is always interpreted as a file name.
Lars> (I think.) If it were possible to feed the Emacs server
Lars> some random elisp form, that would make implementing this
Lars> stuff very easy. Or is it possible already?
gnudoit (i.e. from gnuserver) does this. I prefer the emacsclient
IPC method of using a named pipe however. It would be very nice if
there was some 'emacsdoit'.
Jan
P.S. Now if only emacsserver would place the pipe in the home dir by
default in stead of in /tmp
next prev parent reply other threads:[~1995-12-14 10:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-12-14 8:32 Lars Magne Ingebrigtsen
1995-12-14 9:58 ` Kai Grossjohann
1995-12-14 10:16 ` vroonhof [this message]
1995-12-14 13:29 ` William Perry
1995-12-14 20:00 ` Steven L. Baur
1995-12-15 19:14 ` Lars Magne Ingebrigtsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199512141016.LAA01016@goedel.math.ethz.ch \
--to=vroonhof@math.ethz.ch \
--cc=ding@ifi.uio.no \
/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.
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 NNTP newsgroup(s).