From: Eli Zaretskii <eliz@gnu.org>
Cc: lekktu@gmail.com, emacs-devel@gnu.org, emacs-pretest-bug@gnu.org,
F.J.Wright@qmul.ac.uk
Subject: Re: Emacsclient/server filename quoting error
Date: Fri, 15 Dec 2006 17:54:31 +0200 [thread overview]
Message-ID: <uhcvxw3wo.fsf@gnu.org> (raw)
In-Reply-To: <20061215.161438.180093727.wl@gnu.org> (message from Werner LEMBERG on Fri, 15 Dec 2006 16:14:38 +0100 (CET))
> Date: Fri, 15 Dec 2006 16:14:38 +0100 (CET)
> Cc: eliz@gnu.org, F.J.Wright@qmul.ac.uk, emacs-devel@gnu.org,
> emacs-pretest-bug@gnu.org
> From: Werner LEMBERG <wl@gnu.org>
>
> Since those issues are full of subtleties I suggest that you have a
> look at the gnulib CVS (at savannah.gnu.org), inspecting the files
> `execute.c' and `pipe.c':
>
> http://cvs.savannah.gnu.org/viewcvs/gnulib/lib/execute.c?rev=1.7&root=gnulib&view=log
> http://cvs.savannah.gnu.org/viewcvs/gnulib/lib/pipe.c?rev=1.6&root=gnulib&view=log
Thanks, but I see nothing in these source files that could shed any
light on the case in point.
> Similar code is used in groff too.
Groff builds a pipe of several programs and then runs that pipe. By
contrast, emacsclient needs to run a single program, and doesn't need
to read/write its standard streams. So the complexity of the above
URLs is not needed.
next prev parent reply other threads:[~2006-12-15 15:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <001701c71c53$1be9a9f0$041df159@Monolith>
2006-12-15 10:31 ` Emacsclient/server filename quoting error Juanma Barranquero
2006-12-15 11:06 ` Eli Zaretskii
2006-12-15 12:07 ` Juanma Barranquero
2006-12-15 14:19 ` Eli Zaretskii
2006-12-15 15:42 ` Juanma Barranquero
2006-12-15 15:50 ` David Kastrup
2006-12-15 16:03 ` Juanma Barranquero
2006-12-15 15:52 ` Eli Zaretskii
2006-12-15 15:14 ` Werner LEMBERG
2006-12-15 15:41 ` Juanma Barranquero
2006-12-15 15:54 ` Eli Zaretskii [this message]
2006-12-17 17:24 ` Francis Wright
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=uhcvxw3wo.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=F.J.Wright@qmul.ac.uk \
--cc=emacs-devel@gnu.org \
--cc=emacs-pretest-bug@gnu.org \
--cc=lekktu@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.