Date: Thu, 8 Aug 2002 08:25:09 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Karl Berry <karl AT freefriends DOT org>
cc: kodea AT mail DOT ru, help-texinfo AT gnu DOT org, djgpp AT delorie DOT com
Subject: Re: Re[2]: Info: Custom Key Bindings
In-Reply-To: <200208071520.g77FKkI14354@f7.net>
Message-ID: <Pine.SUN.3.91.1020808082332.4988G-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Wed, 7 Aug 2002, Karl Berry wrote:

>     #var
>     scroll-step=1
> 
> Maybe the file is actually getting read but this setting is not being
> honored for whatever reason.  Can you try doing some key rebindings or
> other changes to check that out?

That'd be my suggestion as well.

> Actually, you should be able to tell if the file is getting read if you
> run  ls -lu _info  before and after running info.  If Windows has an
> atime, I don't really know that for sure I guess ...

Windows does have atime, but I'm not sure it's updated every time the 
file is read.  If we come to the conclusion that nothing in the _info file 
seems to take effect in the session, the best way to debug this would be 
to step into the code with a debugger and see what happens there.