From mbk@choh001.cho.ge.com  Tue Oct  1 07:52:33 1996
X-VM-v5-Data: ([nil nil nil t t nil nil nil nil]
	[nil "Tue" " 1" "October" "1996" "10:51:50" "-0400" "Mike Krell" "mbk@choh001.cho.ge.com" "<199610011454.KAA23303@ns.ge.com>" "29" "Re: compiling within 19.34" "^From:" nil nil "10" nil nil nil nil]
	nil)
Received: from ns.ge.com (ns.ge.com [192.35.39.24]) by june.cs.washington.edu (8.7.6/7.2ju) with ESMTP id HAA18828 for <voelker@cs.washington.edu>; Tue, 1 Oct 1996 07:52:32 -0700
Received: from choh081.cho.ge.com ([3.16.17.81]) by ns.ge.com (8.7.5/8.7.3) with SMTP id KAA23303 for <voelker@cs.washington.edu>; Tue, 1 Oct 1996 10:54:58 -0400 (EDT)
Message-Id: <199610011454.KAA23303@ns.ge.com>
Received: by choh081.cho.ge.com 	(1.37.109.8/16.2) id AA04202; Tue, 1 Oct 1996 10:51:50 -0400
In-Reply-To: <199609290556.WAA28822@joker.cs.washington.edu>
References: <199609111314.JAA17067@ns.ge.com> 	<199609290556.WAA28822@joker.cs.washington.edu>
From: Mike Krell <mbk@choh001.cho.ge.com>
To: voelker@cs.washington.edu (Geoff Voelker)
Subject: Re: compiling within 19.34
Date: Tue, 1 Oct 1996 10:51:50 -0400

>From the quill of Geoff Voelker:

 > dunno if this is still haunting you, but it appears that stderr is being
 > redirected to some black hole.  can you check whether you get the same
 > behavior while using some other shell (like cmd.exe if you are NT)?

I fixed the problem by forcing bash to run an interactive shell.  I also
changed my bash startup files some so that now I have one which only does
environment variable settings, as so:

(setq shell-file-name "c:\\bash\\bin\\bash.exe")
(setq shell-command-switch "-rcfile c:\\mbk\\.bashrc_env -i -c")
(setq hexlify-command "hexl -hex ")
(setq dehexlify-command "hexl -hex -de ")

With these settings, I was still having a problem with hexl mode in that
saving a hexl buffer corrupted the file.  (It appeared to "hexlify" the
buffer contents _again_ before writing to the file instead of "dehexlifying"
them, if you follow me.)  I've just stumbled onto a fix for this problem
this morning: I need to quote the hexlify and dehexlify commands:
 
    (setq hexlify-command "\"hexl -hex \"")
    (setq dehexlify-command "\"hexl -hex -de \"")

I'm not sure why I need to do this, but it appears to work.

     Mike                                    mike.krell@cho.ge.com

"Never miss a good chance to shut up." -- Scott Beach's grandfather

From owner-ntemacs-users@june  Wed Oct  2 08:23:28 1996
X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil]
	[nil "Wed" " 2" "October" "1996" "10:23:28" "-0400" "Mike Krell" "mbk@choh001.cho.ge.com" nil "28" "hexl mode fix" "^From:" nil nil "10" nil nil nil nil]
	nil)
Received: from joker.cs.washington.edu (joker.cs.washington.edu [128.95.1.42]) by june.cs.washington.edu (8.7.6/7.2ju) with SMTP id IAA08861 for <voelker@june.cs.washington.edu>; Wed, 2 Oct 1996 08:23:28 -0700
Received: from june.cs.washington.edu (june.cs.washington.edu [128.95.1.4]) by joker.cs.washington.edu (8.6.12/7.2ws+) with ESMTP id IAA23166 for <voelker@joker.cs.washington.edu>; Wed, 2 Oct 1996 08:23:26 -0700
Received: from ns.ge.com (ns.ge.com [192.35.39.24]) by june.cs.washington.edu (8.7.6/7.2ju) with ESMTP id HAA05912 for <ntemacs-users@cs.washington.edu>; Wed, 2 Oct 1996 07:25:24 -0700
Received: from choh081.cho.ge.com ([3.16.17.81]) by ns.ge.com (8.7.5/8.7.3) with SMTP id KAA23270 for <ntemacs-users@cs.washington.edu>; Wed, 2 Oct 1996 10:26:52 -0400 (EDT)
Message-Id: <199610021426.KAA23270@ns.ge.com>
Received: by choh081.cho.ge.com 	(1.37.109.8/16.2) id AA04376; Wed, 2 Oct 1996 10:23:28 -0400
In-Reply-To: <199610020248.AA27931@fed3005.reston.ingr.com>
References: <199609261801.OAA13863@ns.ge.com> 	<199610020248.AA27931@fed3005.reston.ingr.com>
From: Mike Krell <mbk@choh001.cho.ge.com>
To: ntemacs-users@cs.washington.edu
Cc: dsrosing@ingr.com
Subject: hexl mode fix
Date: Wed, 2 Oct 1996 10:23:28 -0400

I now have hexl mode working under windows 95 using bash.  For those
interested, here are the details:

First, as David Rosinger pointed out, you need to use a shell other than
windows 95's default command.com; I'm using bash.  This fixes the problem of
the subprocess not being invoked, but I had an additional problem with saving
a hexl mode buffer corrupting the file.  (It appeared to "hexlify" the buffer
contents _again_ before writing to the file instead of "dehexlifying" them,
if you follow me.)  I fixed this problem by putting extra double quotes
around the settings for hexlify-command and dehexlify-command as shown below.

Here are the settings from my .emacs file:

Note that .bashrc_env is a startup file which only sets environment variables.

(setq shell-file-name "c:\\bash\\bin\\bash.exe")
(setq shell-command-switch "-rcfile c:\\mbk\\.bashrc_env -i -c")
(setq hexlify-command "\"hexl -hex \"")
(setq dehexlify-command "\"hexl -hex -de \"")

These settings also cleaned up another problem I was having in which the
ouput from a makefile was not appearing in a compilation buffer.  

Hope this helps.

     Mike                                    mike.krell@cho.ge.com

"Start slow and taper off."  -- Walt Stack

From owner-ntemacs-users@june  Mon Dec  9 17:35:58 1996
X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil]
	[nil "" "10" "December" "1996" "08:39:27" "+1300" "Jason Rumney" "jasonr@pec.co.nz" nil "30" "Re: hexl mode on Win95" "^From:" nil nil "12" nil nil nil nil]
	nil)
Received: from joker.cs.washington.edu (joker.cs.washington.edu [128.95.1.42]) by june.cs.washington.edu (8.8.3+CSE/7.2ju) with SMTP id RAA22971 for <voelker@june.cs.washington.edu>; Mon, 9 Dec 1996 17:35:58 -0800
Received: from june.cs.washington.edu (june.cs.washington.edu [128.95.1.4]) by joker.cs.washington.edu (8.6.12/7.2ws+) with ESMTP id RAA22443 for <voelker@joker.cs.washington.edu>; Mon, 9 Dec 1996 17:35:57 -0800
Received: from janus.pec.co.nz (janus.pec.co.nz [202.20.64.195]) by june.cs.washington.edu (8.8.3+CSE/7.2ju) with SMTP id QAA20238 for <ntemacs-users@cs.washington.edu>; Mon, 9 Dec 1996 16:55:28 -0800
Received: from PACHINKO (pachinko.pec.co.nz [202.36.208.29]) by janus.pec.co.nz (8.6.11/8.6.11) with SMTP id NAA02210 for <ntemacs-users@cs.washington.edu>; Tue, 10 Dec 1996 13:56:11 +1300
References: <jjmcdafrqfo52.fsf@mdp23b.the.net>
X-Junk-Mail-Policy: http://www.pec.co.nz/~jasonr/rates.html
Mail-Copies-To: never
Mime-Version: 1.0 (generated by tm-edit 7.85)
Content-Type: text/plain; charset=US-ASCII
In-Reply-To: dssl's message of 07 Dec 1996 14:02:49 +0000
Message-ID: <wk3exftsls.fsf@pachinko.pec.co.nz>
Lines: 28
X-Mailer: Red Gnus v0.61/Emacs 19.34
From: Jason Rumney <jasonr@pec.co.nz>
To: ntemacs-users@cs.washington.edu
Subject: Re: hexl mode on Win95
Date: 10 Dec 1996 08:39:27 +1300

In article <jjmcdafrqfo52.fsf@mdp23b.the.net>, dssl <p-s@the.net> writes:

> I haven't used hexl mode before, so perhaps I don't understand, but
> when I open a file in hexl mode, I get a blank screen on win95.  Is
> this the expected behavior?  Or perhaps there is a prob with the setup
> I've got?

> Any clues would be appreciated.

COMMAND.COM will not accept input on stdin.  There are a number of
alternative shells you can use.  I use CMD32.EXE which comes with the
Win32 Perl 5 distribution (doesn't work interactively, but works well
for hexl, ediff, metamail, ftp and make).  The registry setting under
Software/GNU/Emacs/SHELL controls what your default shell is, or there
are some variables you can set in your .emacs

In addition to the SHELL environment variable, I have the following in
my .emacs (the path is probably not neccesary, but I did have problems
with the default options for dehexilifying.

(setq hexlify-command "D:\\Emacs-19.34\\bin\\hexl -iso")
(setq dehexlify-command "D:\\Emacs-19.34\\bin\\hexl -de")

-- 
---------------------------------------------------------------------------
You saw the video, you heard the soundtrack, well now go buy the softdrink.
        - Disposable Heroes of Hiphoprisy
-------------------------------- Jason Rumney <jasonr@pec.co.nz> ----------



From owner-ntemacs-users@trout  Tue Mar  4 16:28:16 1997
X-VM-v5-Data: ([nil nil nil nil nil nil nil nil nil]
	[nil "Tue" " 4" "March" "1997" "18:45:21" "" "Pete M. Wilson" "wilsonpm@gamewood.net" nil "14" "Hexl mode and UNC" "^From:" nil nil "3" nil nil nil nil]
	nil)
Received: from joker.cs.washington.edu (joker.cs.washington.edu [128.95.1.42]) by june.cs.washington.edu (8.8.5+CS/7.2ju) with SMTP id QAA29729 for <voelker@june.cs.washington.edu>; Tue, 4 Mar 1997 16:28:16 -0800
Received: from trout.cs.washington.edu (trout.cs.washington.edu [128.95.1.178]) by joker.cs.washington.edu (8.6.12/7.2ws+) with ESMTP id QAA19456 for <voelker@joker.cs.washington.edu>; Tue, 4 Mar 1997 16:28:15 -0800
Received: from june.cs.washington.edu (june.cs.washington.edu [128.95.1.4]) by trout.cs.washington.edu (8.8.5+CS/7.2ws+) with ESMTP id PAA12923 for <ntemacs-users@trout.cs.washington.edu>; Tue, 4 Mar 1997 15:45:32 -0800 (PST)
Received: from ns.gamewood.net (ns.gamewood.net [199.0.155.2]) by june.cs.washington.edu (8.8.5+CS/7.2ju) with SMTP id PAA25578 for <ntemacs-users@cs.washington.edu>; Tue, 4 Mar 1997 15:45:31 -0800
Received: from wilsonp.drmc.drhsi.org by ns.gamewood.net with SMTP (5.65/1.2-eef) 	id AA18603; Tue, 4 Mar 97 18:45:22 -0500
Message-Id: <9703042345.AA18603@ns.gamewood.net>
Comments: Authenticated sender is <wilsonpm@ns.gamewood.net>
Organization: Starlight Computer Wizardry
Priority: normal
In-Reply-To: <199703042223.OAA21921@joker.cs.washington.edu>
References: <c=US%a=_%p=Sanchez_Computer%l=OZ-970304193133Z-68523@oz.sanchez.com>
X-Mailer: Pegasus Mail for Win32 (v2.52)
From: "Pete M. Wilson" <wilsonpm@gamewood.net>
To: ntemacs-users@cs.washington.edu
Subject: Hexl mode and UNC
Date: Tue, 4 Mar 1997 18:45:21 -5


Using NT Emacs 19.34.1 (8/96) on Windows 95, I have a problem when I open 
a file on a UNC (to an NT server) and then try to start hexl mode. 
Basically, emacs stops responding and I have to terminate the process.

>From the Explorer, I shift-right-click a file and select Open in Emacs, 
and this launches emacs and opens the file (I don't live in emacs :-), 
then I do Alt-X hexl-mode <ENTER>. I see loading hexl mode...done if I 
haven't used hexl mode previously. Then emacs stops responding to all 
input and I have to terminate.

Pete M. Wilson
Gamewood Data Systems Internet Service
wilsonpm@gamewood.net

