* flymake and filenames matching [0-9]+.tex
@ 2010-11-26 19:09 Rob Browning
2010-11-27 20:26 ` Glenn Morris
0 siblings, 1 reply; 5+ messages in thread
From: Rob Browning @ 2010-11-26 19:09 UTC (permalink / raw)
To: emacs-devel
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: flymake and filenames matching [0-9]+.tex
2010-11-26 19:09 flymake and filenames matching [0-9]+.tex Rob Browning
@ 2010-11-27 20:26 ` Glenn Morris
2010-12-11 3:10 ` Rob Browning
0 siblings, 1 reply; 5+ messages in thread
From: Glenn Morris @ 2010-11-27 20:26 UTC (permalink / raw)
To: Rob Browning; +Cc: emacs-devel
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.
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: flymake and filenames matching [0-9]+.tex
2010-11-27 20:26 ` Glenn Morris
@ 2010-12-11 3:10 ` Rob Browning
2010-12-13 2:21 ` Glenn Morris
0 siblings, 1 reply; 5+ messages in thread
From: Rob Browning @ 2010-12-11 3:10 UTC (permalink / raw)
To: Glenn Morris; +Cc: emacs-devel
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
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2010-12-13 2:29 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-11-26 19:09 flymake and filenames matching [0-9]+.tex Rob Browning
2010-11-27 20:26 ` Glenn Morris
2010-12-11 3:10 ` Rob Browning
2010-12-13 2:21 ` Glenn Morris
2010-12-13 2:29 ` Rob Browning
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).