From:	fprintf AT iname DOT com (Stuart Hall)
Newsgroups:	comp.os.msdos.djgpp
Subject:	RHIDE question - not fully defined in the FAQs
Date:	Thu, 21 Jan 1999 17:24:23 GMT
Organization:	Connix - The Connecticut Internet Exchange
Lines:	34
Message-ID:	<36a760f2.14047580@news>
NNTP-Posting-Host:	m5.aetna.com
Mime-Version:	1.0
X-Newsreader:	Forte Agent 1.5/32.452
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Ok, I was reading about the ^space feature of the SET editor, and
RHIDE and could not get it to work.  The FAQs included on the SET
homepage, and the RHIDE help files I downloaded indicated that I
should look for a file called 'pmacros.txt' - which does not exist on
my PC.  I tried a bunch of different things, but none seemed to work
and the help files were not any more helpful than redefining what a
pseudo-macro was supposed to do.

As a first resort, I tried copying the file pmacro.pmc to a text file,
but to no avail.  Finally after several hours of playing and
searching, I changed the name of a file in the SHARE/RHIDE folder
called cpmacro.pmc to pmacro.pmc and voila! the predefined pseudo
macros now work perfectly!!!  I think this could be added to the help
files in 1.4.7, if they are not already there.  (I have 1.4 because of
an aversion to beta-software :-)

Here is what I would write:  "There are 32 predefined pseudo macros
available which will assist in writing C programs.  The filename is
cpmacro.pmc, and all that is needed is to change the filename to
pmacro.pmc.  If you wish to utilize your own macros, you will need to
either delete one or more of the 32 predefined macros by editing the
new pmacro.pmc or don't copy cpmacro.pmc, and simply write your own
macros into pmacro.pmc"

The SET documentation in the RHIDE help files is extremely misleading
by suggesting it is a text file.   

Stuart



----
Stuart Hall
Connecticut, USA

- Raw text -