On Wed, Aug 16, 2000 at 11:09:14AM -0400, Hal Burgiss wrote:
> On Wed, Aug 16, 2000 at 09:35:08AM -0500, Bret Hughes wrote:
> > Hal Burgiss wrote:
> >
> > > On Wed, Aug 16, 2000 at 05:54:44PM +0800, Stephen Liu wrote:
> > > > Hi All People,
> > > >
> > > >
> > > > but following strange symbols ap
HOWTO files are in plain text if they've been installed or whatever. like
Sound-HOWTO (from /usr/doc/HOWTO) is in plain text. Use pico or vi :)
On Wed, 16 Aug 2000, Stephen Liu wrote:
> Hi All People,
>
> Kindly advise what shall be the right Editor to read HOW-TO files in RH 6.2
>
> I tried t
Hal Burgiss wrote:
> > > Try 'cat $HOWTO | col -bx | less'.
> > >
> >
> > why is he having to do this? I use a browser (netscape), and less
> > all the time with no problems. Just surious.
>
> I used to know exactly why, but escapes me ATM ;( You notice that text
> HOWTOs from LDP don't have th
On Wed, Aug 16, 2000 at 09:35:08AM -0500, Bret Hughes wrote:
> Hal Burgiss wrote:
>
> > On Wed, Aug 16, 2000 at 05:54:44PM +0800, Stephen Liu wrote:
> > > Hi All People,
> > >
> > >
> > > but following strange symbols appears inside their content
> > >
> > > 2#2.#.3#3.#. I#I/#/O#O A#Ad#dd#dr#re#
Hal Burgiss wrote:
> On Wed, Aug 16, 2000 at 05:54:44PM +0800, Stephen Liu wrote:
> > Hi All People,
> >
> > Kindly advise what shall be the right Editor to read HOW-TO files in RH 6.2
> >
> > I tried to read them with following Editors/application:
> >
> > - Kde Advance Editor
> > - Linux Star O
On Wed, Aug 16, 2000 at 05:54:44PM +0800, Stephen Liu wrote:
> Hi All People,
>
> Kindly advise what shall be the right Editor to read HOW-TO files in RH 6.2
>
> I tried to read them with following Editors/application:
>
> - Kde Advance Editor
> - Linux Star Office
> - Linux Netscape
> - M$Winw
Hi All People,
Kindly advise what shall be the right Editor to read HOW-TO files in RH 6.2
I tried to read them with following Editors/application:
- Kde Advance Editor
- Linux Star Office
- Linux Netscape
- M$Winword
- M$Wordpad
but following strange symbols appears inside their content
2#2.