From: Fabrice POPINEAU <popineau@esemetz.ese-metz.fr>
Cc: ntemacs-users@cs.washington.edu
Subject: UUdecode and NTemacs
Date: Fri, 4 Apr 1997 10:59:10 +0200 (MET DST) [thread overview]
Message-ID: <199704040859.KAA27807@esemetz.ese-metz.fr> (raw)
Hi,
The following code in gnus-uu.el (5.4.36) needs some modification to
work under NTemacs:
;; Start a new uudecoding process.
(let ((cdir default-directory))
(unwind-protect
(progn
(cd gnus-uu-work-dir)
(setq gnus-uu-uudecode-process
(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))))
"uudecode")))
(cd cdir)))
There are 2 problems:
- gnus-uu-work-dir is "f:/tmp/gnusa00195" and if your shell is "cmd",
it can't 'cd' to some path with '/', it needs '\'
- anyway, I'm not sure NTemacs can accept "cd f:\\tmp\\gnusa00195 &&
uudecode" as a program to start.
As there was a (cd gnus-uu-work-dir) just before, is it useful to keep
the "cd tmpdir &&" into the starting process ?
Also, under NTemacs, shelex.exe would be a better viewer for most of
the files you want to decode.
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 reply other threads:[~1997-04-04 8:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-04-04 8:59 Fabrice POPINEAU [this message]
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
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=199704040859.KAA27807@esemetz.ese-metz.fr \
--to=popineau@esemetz.ese-metz.fr \
--cc=ntemacs-users@cs.washington.edu \
/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).