From: Fabrice POPINEAU <popineau@esemetz.ese-metz.fr>
Subject: Re: UUdecode and NTemacs
Date: 07 Apr 1997 09:51:17 +0200 [thread overview]
Message-ID: <upvw7gtje.fsf@ese-metz.fr> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of 05 Apr 1997 12:49:31 +0200
>>>>> "Lars" == Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
Lars> Stainless Steel Rat <ratinox@peorth.gweep.net> writes:
>> On this Fabrice is correct; neither COMMAND.COM nor CMD.EXE
>> (the two Windows command interpreters) support CD with a drive
>> spec.
That may be the explanation for what follows.
>> 4DOS and 4NT do with the CDD command, but they are comercial
>> add-on shells. Also, COMMAND.COM does not have a command
>> separator character at all; not sure about CMD.EXE. 4DOS and
>> 4NT do; it is "^".
Lars> Well, I don't use GatesOS.
I wonder if I will ever be forgiven for running it :-)
Lars> Could someone mail me patches for these things?
I tried to debug this some weeks ago and was puzzled. Last weekn, I
thought that I had the solution, and I'm still puzzled. In fact, the
standard code *almost* works, provided you have:
(setq gnus-shell-command-separator "&")
But I'm getting various errors after the first "X u" processing, like:
- can't remove gnus-uu-work-dir
- try to select destroyed buffer when decoding in another group,
- ...
What is really strange is that if I apply the following patch,
everything is OK:
--- gnus-uu.el~ Thu Mar 13 01:29:04 1997
+++ g:/local/emacs/site-lisp/gnus/lisp/gnus-uu.el Mon Apr 07 09:50:16 1997
@@ -1416,9 +1416,10 @@
(start-process
"*uudecode*"
(get-buffer-create gnus-uu-output-buffer-name)
- shell-file-name shell-command-switch
- (format "cd %s %s uudecode" gnus-uu-work-dir
- gnus-shell-command-separator))))
+; shell-file-name shell-command-switch
+; (format "cd %s %s uudecode" gnus-uu-work-dir
+; gnus-shell-command-separator))))
+ "uudecode")))
(cd cdir)))
(set-process-sentinel
gnus-uu-uudecode-process 'gnus-uu-uudecode-sentinel)
May be this code should be conditionalized by the shell-file-name's
value:
(string-match "cmd\\.exe" shell-file-name)
--
Fabrice POPINEAU
------------------------
e-mail: popineau@ese-metz.fr | "God is real ...
Fabrice.POPINEAU@supelec.fr |
voice-mail: +33 (0) 387764715 | ... unless integer ?"
surface-mail: Supelec, 2 rue E. Belin, |
F-57078 Metz Cedex 3 |
next prev parent reply other threads:[~1997-04-07 7:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-04-04 8:59 Fabrice POPINEAU
1997-04-04 19:32 ` Lars Magne Ingebrigtsen
1997-04-04 23:08 ` Dewey M. Sasser
1997-04-04 23:17 ` Stainless Steel Rat
1997-04-05 10:49 ` Lars Magne Ingebrigtsen
1997-04-07 7:51 ` Fabrice POPINEAU [this message]
1997-04-07 16:42 ` Stainless Steel Rat
1997-04-07 8:01 ` Andy Eskilsson
1997-04-07 16:45 ` Stainless Steel Rat
1997-04-07 18:30 ` Scott Blachowicz
1997-04-07 19:00 ` Stainless Steel Rat
1997-04-07 19:41 ` Scott Blachowicz
1997-04-07 19:58 ` Richard Hoskins
1997-04-08 18:05 ` Andrew Innes
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=upvw7gtje.fsf@ese-metz.fr \
--to=popineau@esemetz.ese-metz.fr \
/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).