Re: [vile] [Too many levels of files]

[Thomas Dickey]

On Sat, May 24, 2014 at 12:41:05PM -0400, Wayne Cuddy wrote:
> On Fri, May 23, 2014 at 05:33:29PM -0400, Thomas Dickey wrote:
> > On Fri, May 23, 2014 at 04:22:34PM -0400, Wayne Cuddy wrote:
> > > On Fri, May 23, 2014 at 02:44:02PM -0400, Thomas Dickey wrote:
> > > > On Fri, May 23, 2014 at 01:37:01PM -0400, Wayne Cuddy wrote:
> > > > > When running vile on OpenBSD is seems there is something that is
> > > > > triggering the message [Too many levels of files] to appear in the
> > > > > status line at the bottom.
> > > > 
> > > > That will happen if there's more than 9 levels of macros.
> > > > (It's hardcoded - hasn't been a need to make it configurable).
> > > >  
> > > > > I typically run vile on Linux (primarily), HP-UX and recently
> > > > > OpenBSD. I only ever see this message on OpenBSD and it seems to be

Which release of OpenBSD is this, by the way?
(I have a VM with 5.3, but haven't noticed a problem there - but mostly
am just running test-compiles)

> > > > > triggered by some key sequence but I can't for the life of me figure
> > > > > out what is causing it.
> > > > 
> > > > offhand, the only thing that comes to mind is some macro which is
> > > > recurring, e.g., by calling itself.
> > > 
> > > I use the same configuration on all my systems and I don't "think" I have
> > > any macros that do that. Once the [Too many ...] message appears does
> > > that mean that the execution would terminate? If I hit escape and it
> > 
> > It means that the expression-evaluation will return an error - and
> > since that's usually handled correctly, we'd expect the error to propagate
> > up and terminate the macro.  (If "~force" was used, that might be ignored).
> > 
> > > aborts I'm wondering why the message appears again within a few seconds.
> > 
> > I don't have a good guess...
> > 
> > > I'll try running with '-D' to see if I notice anything interesting if it
> > > happens again.
> 
> It turns out that running with -D helped determine the problem. The
> autocolor-hook is executing repeatedly. I have autocolor=5000. But I'm
> not sending the editor any input when this is happening. It happens on
> the console, in xterm windows as well as in xvile. I set nohighlight and
> the problem went away. I set X focus to another window and it still
> happened. I have a copy of the trace log (-D) if that will help? I was
> editing my .fvwmrc file at the time... here is what the tail end of
> trace log shows.

hmm - 5000 should be a "long time".  But supposing that the configure checks
to support a timed-wait aren't working properly (or OpenBSD isn't working...),
and that the timer returns right away, there could be some hole which allows
the hook to recur into itself.

-- 
Thomas E. Dickey <address@hidden>
http://invisible-island.net
ftp://invisible-island.net

signature.asc
Description: Digital signature