flymake and filenames matching [0-9]+.tex

flymake and filenames matching [0-9]+.tex

[Rob Browning]

A Debian bug has been filed against emacs23[1] complaining that flymake
won't work on TeX files whose names end in [0-9]+.tex.

Since there is a regex in flymake-allowed-file-name-masks that matches
those filenames, I suspect the behavior is intentional -- I was hoping
someone could verify that.

  [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=599003

Thanks
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4

Re: flymake and filenames matching [0-9]+.tex

[Glenn Morris]

Rob Browning wrote:

> A Debian bug has been filed against emacs23[1] complaining that flymake
> won't work on TeX files whose names end in [0-9]+.tex.
>
> Since there is a regex in flymake-allowed-file-name-masks that matches
> those filenames, I suspect the behavior is intentional -- I was hoping
> someone could verify that.

I suspect whoever wrote that used the convention:

  master.tex:
  %% This is the master file.

  %% These are included files. These cannot be latex'd directly,
  %% instead latex the main file.
  \input{chapter1.tex}
  \input{chapter2.tex}

Who knows how widespread that convention is, but since it is a
defcustom, anyone can change their personal setting.

It seems a bit limited, since eg it does not work for \include as well
(easily fixed though), and it does not work if the .tex extension is
omitted from the \input command.

Re: flymake and filenames matching [0-9]+.tex

[Rob Browning]

Glenn Morris <rgm@gnu.org> writes:

> I suspect whoever wrote that used the convention:
>
>   master.tex:
>   %% This is the master file.
>
>   %% These are included files. These cannot be latex'd directly,
>   %% instead latex the main file.
>   \input{chapter1.tex}
>   \input{chapter2.tex}
>
> Who knows how widespread that convention is, but since it is a
> defcustom, anyone can change their personal setting.
>
> It seems a bit limited, since eg it does not work for \include as well
> (easily fixed though), and it does not work if the .tex extension is
> omitted from the \input command.

So would you say this should be considered a bug or intended behavior?
I'm just trying to determine the appropriate way to handle the original
report.

Thanks
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4

Re: flymake and filenames matching [0-9]+.tex

[Glenn Morris]

Rob Browning wrote:

> So would you say this should be considered a bug or intended behavior?

Both? :)

I filed a bug about improving it:

http://debbugs.gnu.org/cgi/bugreport.cgi?bug=7627

Meantime, anyone affected can customize their value of
flymake-allowed-file-name-masks.

Re: flymake and filenames matching [0-9]+.tex

[Rob Browning]

forwarded 599003 bug-gnu-emacs@gnu.org
thanks

Glenn Morris <rgm@gnu.org> writes:

> Rob Browning wrote:
>
>> So would you say this should be considered a bug or intended behavior?
>
> Both? :)
>
> I filed a bug about improving it:
>
> http://debbugs.gnu.org/cgi/bugreport.cgi?bug=7627

That's perfect.  I'll mark it as forwarded for now.

Thanks
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4