home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.windows.x
- Path: sparky!uunet!snorkelwacker.mit.edu!thunder.mcrcim.mcgill.edu!mouse
- From: mouse@thunder.mcrcim.mcgill.edu (der Mouse)
- Subject: Re: Help: setting up icon font name in .Xdefaults ruins openwin-init
- Message-ID: <1992Jul24.182427.29712@thunder.mcrcim.mcgill.edu>
- Organization: McGill Research Centre for Intelligent Machines
- References: <1992Jul19.113052.20522@u.washington.edu> <1992Jul19.115459.20877@u.washington.edu>
- Date: Fri, 24 Jul 92 18:24:27 GMT
- Lines: 32
-
- In article <1992Jul19.115459.20877@u.washington.edu>, sue@byron.u.washington.edu (Shu-Chen Eclipse) writes:
-
- > I dumpted xlsfonts to a file and used textedit to copy some long
- > schoolbook font names to my .Xdefaults file, [...]. Problem is the
- > lines are then so long that they wrap around to the next line.
-
- > When I next log-in, openwini-init bombs, some tools with these overly
- > long lines fail to open with complaints about not being able to find
- > the font name fragment on the 1st line [...]
-
- > Quesiton: is there a shorter way to name these fonts, "schoolbook"
- > fonts in particular.
-
- That's the wrong fix. Instead, use a real editor, one that knows how
- to deal with lines longer than one screen line. It sounds as though
- textedit actually broke the line into two lines in the file, instead of
- just displaying one file line as two screen lines.
-
- > why is this happening, I would have thought that whatever read
- > openwin-init would be smart enough to keep reading the whole line and
- > not stop at 80 charate4rs, afterall, saveworkspace allowed this to
- > begin with.
-
- It probably is. The problem is, I feel sure, that your editor has
- actually broken that long line into two lines. Use a sane editor like
- vi or even ed to join those two lines back together and see if it
- doesn't work for you then.
-
- der Mouse
-
- mouse@larry.mcrcim.mcgill.edu
-