Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 15 Apr 2001 16:13:38 -0700
From:      "Michael O'Henly" <michael@tenzo.com>
To:        freebsd-stable@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG
Cc:        "Ted Mittelstaedt" <tedm@toybox.placo.com>, Mike Meyer <mwm@mired.org>, scott@sawilson.org
Subject:   Re: Printer madness...
Message-ID:  <01041516133803.00452@h24-69-46-74.gv.shawcable.net>
In-Reply-To: <000001c0c573$9bc40680$1401a8c0@tedm.placo.com>
References:  <000001c0c573$9bc40680$1401a8c0@tedm.placo.com>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On Saturday 14 April 2001 23:16, Ted Mittelstaedt wrote:

> The /etc/printcap file needs to be _exactly_ correct, and I
> mean exact - one wrong character and it won't work.

Thanks to Ted, Mike, and Scott for help with this. I'm embarassed to admit 
that your first guess, Ted, was correct. I checked EVERY character in xemacs 
when I edited /etc/printcap and made sure that the indented lines began with 
a single tab and no spaces, etc. I even trimmed the last carriage return and 
made sure that when I put the cursor after the colon in the last line, xemacs 
said "end of file".

So after, say, eight hours of accumulated effort I started writing another 
plea for assistance to the list and began by inserting /etc/printcap into 
kmail. Lo and behold, at the end of the last line there were a bunch of 
garbage characters that were not visible in xemacs! I opened the file in vi 
(where the garbage chars were also not visible), deleted and reentered the 
last line -- and now it works perfectly. 

I'd hate to say that the moral of this story is not to trust xemacs. If you 
can't trust xemacs, what hope is there for humanity...?

M.

-- 
Michael O'Henly
TENZO Design

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?01041516133803.00452>