unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Mike Ballard <dont_w@nt_spam.org>
Subject: 2nd try - Re: Odd Info problem
Date: Fri, 18 Jun 2004 01:23:12 GMT	[thread overview]
Message-ID: <m2acz1txgo.fsf@west_f1.net> (raw)
In-Reply-To: m2u0xkkt59.fsf@west_f1.net


Only top-posting to say I'll take bizarre hints/suggestions too...

Mike

On Thu Jun 17, I was peacefully napping until Mike Ballard said:

> Hi -
> 
> Although not what you might call a problem, more of an annoyance, is that
> I have my own (source-controlled) top-level Info "dir" file in a certain
> location (where there are no Info files). I set xref-face to a color I
> like and for years this has worked perfectly.
> 
> But now (and I have no idea what changed it; still using Emacs 21.1 as I
> have for the past couple years) bringing up Info in Emacs the xref-face
> color is gone.  When I highlight an Info topic face and select "list
> properties" nothing shows up.  So I renamed my "dir" to "dir.off",
> restarted Emacs and let it use the dir file in /usr/share/info.  xref-face
> is now back to the color I'd specified (and properties show up when
> selected).
> 
> But if I copy /usr/share/info/dir over my own top-level dir file
> (expecting xref-face to show up as I set it) xref-face reverts back to
> uncolored (and unspecified when I select "list properties").  Any idea
> what might be behind this?
> 
> You'd guess it has something to do with pointing Info to use my location's
> "dir" as its top-level but I've done it this way for years without any
> problems.  I'm using texinfo 4.5 if it matters (and prioritzed
> INFOPATH/DIR vars where my "dir" location is first).
> 
> Mike
> -- 
> 
> mikeballard at symbol verizon period net
> 
>   "If your main parachute fouls, deploy your reserve.  If your 
>    reserve is also fouled, you have the rest of your life to get
>    it straightened out."
> 

-- 

mikeballard at symbol verizon period net

  "If your main parachute fouls, deploy your reserve.  If your 
   reserve is also fouled you have the rest of your life to get
   it straightened out."

  reply	other threads:[~2004-06-18  1:23 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 ` Mike Ballard [this message]
2004-07-01 10:25 ` Kai Grossjohann

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=m2acz1txgo.fsf@west_f1.net \
    --to=dont_w@nt_spam.org \
    /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).