[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [vile] Error finding
From: |
Paul van Tilburg |
Subject: |
Re: [vile] Error finding |
Date: |
Thu, 14 Aug 2008 08:34:07 +0200 |
User-agent: |
Mutt/1.5.18 (2008-05-17) |
On Wed, Aug 13, 2008 at 10:33:14AM -0400, Paul Fox wrote:
> paul van tilburg wrote:
> > On Thu, Aug 07, 2008 at 08:28:08AM -0400, Thomas Dickey wrote:
> > > It sounds essentially as if you need a macro that loads the file and sets
> > > the error-buffer to it. Here's a quick try at it - seems to work:
> > >
> > > store-procedure layers
> > > ~local %cbufname
> > > setv %cbufname $cbufname
> > > ~quiet edit-file 'foo.err'
> > > error-buffer 'foo.err'
> > > buffer %cbufname
> > > ~endm
> >
> > Ok, that works, thanks. It is a start though, because there are a few
> issues.
> > If the filename is longer than 20 (?) chars, the buffername will not
> > match the filename anymore.
> > Also, when I save, the LaTeX file is recompiled, the .err file is
> > replaced but vile doesn't notice that. I can switch to it, answer yes
> > to the reload? question, switch back and then use ^X-^X again. Is
> > there any way to automate this in the sense that.. where should I hook
> > that up?
>
> i sort of missed the beginning of this thread -- i guess the
> compilation step isn't being done as a result of a command you
> run explicitly? [...]
Indeed, it is not. It is compiled when the main file or any of its includes
is change (i.e. saved in vile). So maybe I need to make a
of a macro simulating the behaviour of ^X-^X that also "reloads" the
Error Buffer.
Paul
--
PhD Student @ Eindhoven | email: address@hidden
University of Technology, The Netherlands | JID: address@hidden
>>> Using the Power of Debian GNU/Linux <<< | GnuPG key ID: 0x50064181