From: Kai Grossjohann <kai@emptydomain.de>
Subject: Re: Odd Info problem
Date: Thu, 01 Jul 2004 12:25:47 +0200 [thread overview]
Message-ID: <864qosowgk.fsf@rumba.de.uu.net> (raw)
In-Reply-To: m2u0xkkt59.fsf@west_f1.net
I'm not sure I understand what's happening. You have two
directories, /own for your own dir file and /usr/share/info for the
"standard" dir file. And you have two dir files, dir.own for your
own and dir.standard for the standard one.
Now you have a file /own/dir with the contents of dir.own, and the
xref face is gone. Then you remove /own/dir and use
/usr/share/info/dir instead, with the contents of dir.standard, and
the xref face is back again.
Then comes the part I don't understand. Either you tried to use
/own/dir with the contents of dir.standard, or you tried
/usr/share/info/dir with the contents of dir.own. Which one is it?
If it was the latter, then perhaps dir.own exceeds
font-lock-maximum-size?
Kai
prev parent reply other threads:[~2004-07-01 10:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-10 2:06 Odd Info problem Mike Ballard
2004-06-18 1:23 ` 2nd try - " Mike Ballard
2004-07-01 10:25 ` Kai Grossjohann [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=864qosowgk.fsf@rumba.de.uu.net \
--to=kai@emptydomain.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).