Re: chktex warnings on some tex constructs used by lyx

Uer Regex. \noindent\shadowbox{\begin{minipage}[t]{1\columnwidth - 2\fboxsep - 2\fboxrule - \shadowsize}% Wrong length of dash may have been used. This is wrong. Bug in chktex. But the LaTeX code output here is really ugly. JMarc

chktex warnings on some tex constructs used by lyx

Here are some examples used in Additional.lyx (to be seen in Additional.tex) features of \LaTeX . You ought to remove spaces in front of punctuation. heavily on \LyX 's interaction Use ` to begin quotation, not '. HTML. And lastly, there's

Re: Use chktex with knitr?

On Mon, Jul 06, 2015 at 05:13:15AM -0400, Scott Kostyshak wrote: On Mon, Jul 06, 2015 at 11:04:37AM +0200, Jean-Marc Lasgouttes wrote: Le 06/07/2015 00:44, Scott Kostyshak a écrit : chktex is enabled as follows: enable = params().isLatex() !lyxrc.chktex_command.empty

Re: Use chktex with knitr?

On Mon, Jul 06, 2015 at 05:13:15AM -0400, Scott Kostyshak wrote: > On Mon, Jul 06, 2015 at 11:04:37AM +0200, Jean-Marc Lasgouttes wrote: > > Le 06/07/2015 00:44, Scott Kostyshak a écrit : > > >chktex is enabled as follows: > > > > > >enable = params().isLa

Re: Use chktex with knitr?

Le 06/07/2015 00:44, Scott Kostyshak a écrit : chktex is enabled as follows: enable = params().isLatex() !lyxrc.chktex_command.empty(); This excludes it from running when knitr is in the document. Is there any easy way to have it run on the .tex file that is ultimately produced by knitr

Re: Use chktex with knitr?

On Mon, Jul 06, 2015 at 11:25:57AM +0200, Liviu Andronic wrote: On Mon, Jul 6, 2015 at 11:08 AM, Jean-Marc Lasgouttes lasgout...@lyx.org wrote: Le 06/07/2015 00:44, Scott Kostyshak a écrit : chktex is enabled as follows: enable = params().isLatex() !lyxrc.chktex_command.empty

Re: Use chktex with knitr?

Le 06/07/2015 00:44, Scott Kostyshak a écrit : chktex is enabled as follows: enable = params().isLatex() !lyxrc.chktex_command.empty(); This excludes it from running when knitr is in the document. Is there any easy way to have it run on the .tex file that is ultimately produced by knitr

Re: Use chktex with knitr?

On Mon, Jul 06, 2015 at 11:04:37AM +0200, Jean-Marc Lasgouttes wrote: Le 06/07/2015 00:44, Scott Kostyshak a écrit : chktex is enabled as follows: enable = params().isLatex() !lyxrc.chktex_command.empty(); This excludes it from running when knitr is in the document. Is there any easy way

Re: Use chktex with knitr?

On Mon, Jul 06, 2015 at 11:08:01AM +0200, Jean-Marc Lasgouttes wrote: Le 06/07/2015 00:44, Scott Kostyshak a écrit : chktex is enabled as follows: enable = params().isLatex() !lyxrc.chktex_command.empty(); This excludes it from running when knitr is in the document. Is there any easy way

Re: Use chktex with knitr?

On Mon, Jul 6, 2015 at 11:08 AM, Jean-Marc Lasgouttes lasgout...@lyx.org wrote: Le 06/07/2015 00:44, Scott Kostyshak a écrit : chktex is enabled as follows: enable = params().isLatex() !lyxrc.chktex_command.empty(); This excludes it from running when knitr is in the document. Is there any

Re: Use chktex with knitr?

On Mon, Jul 6, 2015 at 11:45 AM, Scott Kostyshak skost...@lyx.org wrote: On Mon, Jul 06, 2015 at 11:25:57AM +0200, Liviu Andronic wrote: On Mon, Jul 6, 2015 at 11:08 AM, Jean-Marc Lasgouttes lasgout...@lyx.org wrote: Le 06/07/2015 00:44, Scott Kostyshak a écrit : chktex is enabled

Re: Use chktex with knitr?

commenting out is that chunks may output LaTeX elements used elsewhere in the document. For instance, `xtable(iris, label = asdf)` would contain a label that would be used in non-chunk LaTeX code as a cross-ref, probably generating issues as far as chktex is concerned (if the chunks

Re: Use chktex with knitr?

Le 06/07/2015 00:44, Scott Kostyshak a écrit : chktex is enabled as follows: enable = params().isLatex() && !lyxrc.chktex_command.empty(); This excludes it from running when knitr is in the document. Is there any easy way to have it run on the .tex file that is ultimately produced

Re: Use chktex with knitr?

Le 06/07/2015 00:44, Scott Kostyshak a écrit : chktex is enabled as follows: enable = params().isLatex() && !lyxrc.chktex_command.empty(); This excludes it from running when knitr is in the document. Is there any easy way to have it run on the .tex file that is ultimately produced

Re: Use chktex with knitr?

On Mon, Jul 06, 2015 at 11:04:37AM +0200, Jean-Marc Lasgouttes wrote: > Le 06/07/2015 00:44, Scott Kostyshak a écrit : > >chktex is enabled as follows: > > > >enable = params().isLatex() && !lyxrc.chktex_command.empty(); > > > >This excludes it f

Re: Use chktex with knitr?

On Mon, Jul 06, 2015 at 11:08:01AM +0200, Jean-Marc Lasgouttes wrote: > Le 06/07/2015 00:44, Scott Kostyshak a écrit : > >chktex is enabled as follows: > > > >enable = params().isLatex() && !lyxrc.chktex_command.empty(); > > > >This excludes it f

Re: Use chktex with knitr?

On Mon, Jul 6, 2015 at 11:08 AM, Jean-Marc Lasgouttes <lasgout...@lyx.org> wrote: > Le 06/07/2015 00:44, Scott Kostyshak a écrit : >> >> chktex is enabled as follows: >> >> enable = params().isLatex() && !lyxrc.chktex_command.empty(); >&

Re: Use chktex with knitr?

On Mon, Jul 06, 2015 at 11:25:57AM +0200, Liviu Andronic wrote: > On Mon, Jul 6, 2015 at 11:08 AM, Jean-Marc Lasgouttes > <lasgout...@lyx.org> wrote: > > Le 06/07/2015 00:44, Scott Kostyshak a écrit : > >> > >> chktex is enabled as follows:

Re: Use chktex with knitr?

/2015 00:44, Scott Kostyshak a écrit : >> >> >> >> chktex is enabled as follows: >> >> >> >> enable = params().isLatex() && !lyxrc.chktex_command.empty(); >> >> >> >> This excludes it from running when knitr is in the document. Is there >

Re: Use chktex with knitr?

other argument against commenting out is that chunks may output > LaTeX elements used elsewhere in the document. For instance, > `xtable(iris, label = "asdf")` would contain a label that would be > used in non-chunk LaTeX code as a cross-ref, probably generating > issues as far

Use chktex with knitr?

chktex is enabled as follows:

Re: Use chktex with knitr?

chktex is enabled as follows: enable = params().isLatex() !lyxrc.chktex_command.empty(); This excludes it from running when knitr is in the document. Is there any easy way to have it run on the .tex file that is ultimately produced by knitr? Scott

Use chktex with knitr?

chktex is enabled as follows:

Re: Use chktex with knitr?

chktex is enabled as follows: enable = params().isLatex() && !lyxrc.chktex_command.empty(); This excludes it from running when knitr is in the document. Is there any easy way to have it run on the .tex file that is ultimately produced by knitr? Scott

Re: chktex alternative

Steffen Ohrendorf steffen.ohrendorf at gmx.de writes: Am Mittwoch, 14. Dezember 2011, 17:35:27 schrieb Steffen Ohrendorf: Hi mailing list! I started an experimental project 3 days ago, trying to resemble the chktex functionality in Perl, because I think the tool is somehow outdated

Re: chktex alternative

Steffen Ohrendorf gmx.de> writes: > Am Mittwoch, 14. Dezember 2011, 17:35:27 schrieb Steffen Ohrendorf: > > Hi mailing list! > > > > I started an experimental project 3 days ago, trying to resemble the chktex > > functionality in Perl, because I think the tool

Re: chktex alternative

Am Mittwoch, 14. Dezember 2011, 17:35:27 schrieb Steffen Ohrendorf: Hi mailing list! I started an experimental project 3 days ago, trying to resemble the chktex functionality in Perl, because I think the tool is somehow outdated. The script is still buggy (mainly because it's my first touch

Re: chktex alternative

Am Mittwoch, 14. Dezember 2011, 17:35:27 schrieb Steffen Ohrendorf: > Hi mailing list! > > I started an experimental project 3 days ago, trying to resemble the chktex > functionality in Perl, because I think the tool is somehow outdated. The > script is still buggy (mainly becaus

chktex alternative

Hi mailing list! I started an experimental project 3 days ago, trying to resemble the chktex functionality in Perl, because I think the tool is somehow outdated. The script is still buggy (mainly because it's my first touch with Perl), but maybe some of you want to give it a try. Here's

chktex alternative

Hi mailing list! I started an experimental project 3 days ago, trying to resemble the chktex functionality in Perl, because I think the tool is somehow outdated. The script is still buggy (mainly because it's my first touch with Perl), but maybe some of you want to give it a try. Here's

Re: #6574: ChkTeX selects entire paragraph, rather than just line where error occurs.

Le 06/03/2010 04:00, John McCabe-Dansted a écrit : On Sat, Mar 6, 2010 at 3:46 AM, Tommaso Cucinottatomm...@lyx.org wrote: Probably you have more experience than me in using chktex, so, please, comment on this. In the meantime, I'm leaving just the standard linelen from the RC file also

Re: #6574: ChkTeX selects entire paragraph, rather than just line where error occurs.

Le 06/03/2010 04:00, John McCabe-Dansted a écrit : On Sat, Mar 6, 2010 at 3:46 AM, Tommaso Cucinotta<tomm...@lyx.org> wrote: Probably you have more experience than me in using chktex, so, please, comment on this. In the meantime, I'm leaving just the standard linelen from the RC fil

Re: #6574: ChkTeX selects entire paragraph, rather than just line where error occurs.

with linebreaks. I will try setting the ChkTeX linelen to 1 and seeing what breaks. This might uncover some bugs in LyX-GC where errors get missed if they are split onto multiple lines. As of now, I get a stupid === Warning 36 in /tmp/lyx_tmpdir.TJ8403/lyx_tmpbuf0/good-bad-ugly.tex line 102: You

Re: #6574: ChkTeX selects entire paragraph, rather than just line where error occurs.

On Sat, Mar 6, 2010 at 3:46 AM, Tommaso Cucinotta tomm...@lyx.org wrote: Probably you have more experience than me in using chktex, so, please, comment on this. In the meantime, I'm leaving just the standard linelen from the RC file also for chktex. Yes that looks like a chktex bug. May

Re: #6574: ChkTeX selects entire paragraph, rather than just line where error occurs.

with linebreaks. I will try setting the ChkTeX linelen to 1 and seeing what breaks. This might uncover some bugs in LyX-GC where errors get missed if they are split onto multiple lines. As of now, I get a stupid === Warning 36 in /tmp/lyx_tmpdir.TJ8403/lyx_tmpbuf0/good-bad-ugly.tex line 102: You

Re: #6574: ChkTeX selects entire paragraph, rather than just line where error occurs.

On Sat, Mar 6, 2010 at 3:46 AM, Tommaso Cucinotta <tomm...@lyx.org> wrote: > Probably you have more experience than me in using chktex, so, please, > comment on this. In the meantime, I'm leaving just the standard linelen from > the RC file also for chktex. Yes that looks like a

Re: #6574: ChkTeX selects entire paragraph, rather than just line where error occurs.

, you set it to the smallest possible value, like 1 or similar. AFAICS, you would likely get much more precise identification of the possible issues, by chktex, wouldn't you (unless it stops working, if there's just 1 word per-line) ? T.

Re: #6574: ChkTeX selects entire paragraph, rather than just line where error occurs.

identification of the possible issues, by chktex, wouldn't you (unless it stops working, if there's just 1 word per-line) ? I was wondering that too. We could do this with LaTeX too. The one place we really don't want to do this is with the File-Export and view source options. There seem to be two issues

Re: #6574: ChkTeX selects entire paragraph, rather than just line where error occurs.

, you set it to the smallest possible value, like 1 or similar. AFAICS, you would likely get much more precise identification of the possible issues, by chktex, wouldn't you (unless it stops working, if there's just 1 word per-line) ? T.

Re: #6574: ChkTeX selects entire paragraph, rather than just line where error occurs.

get much more precise identification of the > possible issues, by chktex, wouldn't you (unless it stops working, if > there's just 1 word per-line) ? I was wondering that too. We could do this with LaTeX too. The one place we really don't want to do this is with the File->Export and view source

[Patch] fix #6574: ChkTeX selects entire paragraph, rather than just line where error occurs

On Wed, Mar 3, 2010 at 11:38 AM, LyX Ticket Tracker t...@lyx.org wrote: #6574: ChkTeX selects entire paragraph, rather than just line where error occurs. Ticket URL: http://www.lyx.org/trac/ticket/6574 This regression from LyX 1.6.x can be fixed just by adding the line

Re: #6574: ChkTeX selects entire paragraph, rather than just line where error occurs.

LyX Ticket Tracker wrote: 2) Press F8 to activate ChkTeX. Thanks for highlighting this tool, I didn't know there was something like that. In 2.0.0svn the entire paragraph is selected, the Good the Bad and the Ugly. In LyX 1.6.x, only the line containing Good is selected. This bug makes

Re: #6574: ChkTeX selects entire paragraph, rather than just line where error occurs.

On Thu, Mar 4, 2010 at 2:06 AM, Tommaso Cucinotta tomm...@lyx.org wrote: LyX Ticket Tracker wrote:  2) Press F8 to activate ChkTeX. Thanks for highlighting this tool, I didn't know there was something like that. I mostly use it for: http://wiki.lyx.org/Tools/LyX-GrammarChecker which

[Patch] "fix #6574: ChkTeX selects entire paragraph, rather than just line where error occurs"

On Wed, Mar 3, 2010 at 11:38 AM, LyX Ticket Tracker <t...@lyx.org> wrote: > #6574: ChkTeX selects entire paragraph, rather than just line where error > occurs. > Ticket URL: <http://www.lyx.org/trac/ticket/6574> This regression from LyX 1.6.x can be fixed ju

Re: #6574: ChkTeX selects entire paragraph, rather than just line where error occurs.

LyX Ticket Tracker wrote: 2) Press F8 to activate ChkTeX. Thanks for highlighting this tool, I didn't know there was something like that. In 2.0.0svn the entire paragraph is selected, the Good the Bad and the Ugly. In LyX 1.6.x, only the line containing "Good" is selected

Re: #6574: ChkTeX selects entire paragraph, rather than just line where error occurs.

On Thu, Mar 4, 2010 at 2:06 AM, Tommaso Cucinotta <tomm...@lyx.org> wrote: > LyX Ticket Tracker wrote: >> >>  2) Press F8 to activate ChkTeX. >> > > Thanks for highlighting this tool, I didn't know there was something like > that. I mostly use it

chktex window restarts from first line

Hello, I just chktexed my French translation of xypic and I was quite bored by this behaviour: as soon as I go to the LyX window to correct an error, the selection jumps back to the first line in the chktex window instead of staying located on the current error. In addition, the first two

chktex window restarts from first line

Hello, I just chktexed my French translation of xypic and I was quite bored by this behaviour: as soon as I go to the LyX window to correct an error, the selection jumps back to the first line in the chktex window instead of staying located on the current error. In addition, the first two

Re: [patch] #2179 LaTeX and chktex error handling problem

John McCabe-Dansted wrote: The patch relies on the fact that the the ErrorList dialog is only updated before it is shown. Thus we can safely prevent updateContents from regenerating the list of errors unless showEvent has been called. Regenerating the list of Errors is problematic because

Re: [patch] #2179 LaTeX and chktex error handling problem

On Wed, Aug 5, 2009 at 4:46 PM, Jürgen Spitzmüllersp...@lyx.org wrote: Well, at least I have it installed, and I played a bit with it in the past. To me, it looks interesting and useful, especially since there is a German GC available. So I am a potential user. I have found another regression

Re: [patch] #2179 LaTeX and chktex error handling problem

John McCabe-Dansted wrote: > The patch relies on the fact that the the ErrorList dialog is only > updated before it is shown. Thus we can safely prevent updateContents > from regenerating the list of errors unless showEvent has been called. > Regenerating the list of Errors is problematic because

Re: [patch] #2179 LaTeX and chktex error handling problem

On Wed, Aug 5, 2009 at 4:46 PM, Jürgen Spitzmüller wrote: > Well, at least I have it installed, and I played a bit with it in the past. To > me, it looks interesting and useful, especially since there is a German GC > available. So I am a potential user. I have found another

Re: [patch] #2179 LaTeX and chktex error handling problem

John McCabe-Dansted wrote: Attached is a patch that does (2). I admit that I do not really understand what you are doing with the patch. Jürgen

Re: [patch] #2179 LaTeX and chktex error handling problem

On Tue, Aug 4, 2009 at 10:30 PM, Jürgen Spitzmüllersp...@lyx.org wrote: John McCabe-Dansted wrote: Attached is a patch that does (2). I admit that I do not really understand what you are doing with the patch. The patch relies on the fact that the the ErrorList dialog is only updated before it

Re: [patch] #2179 LaTeX and chktex error handling problem

John McCabe-Dansted wrote: > Attached is a patch that does (2). I admit that I do not really understand what you are doing with the patch. Jürgen

Re: [patch] #2179 LaTeX and chktex error handling problem

On Tue, Aug 4, 2009 at 10:30 PM, Jürgen Spitzmüller wrote: > John McCabe-Dansted wrote: >> Attached is a patch that does (2). > > I admit that I do not really understand what you are doing with the patch. The patch relies on the fact that the the ErrorList dialog is only updated

[patch] #2179 LaTeX and chktex error handling problem

How does this patch look? I thought it would be cleaner if I could avoid needing to add the variable bool need_to_set_row, however I cannot see how this could be done. If I put setCurrentRow(0) in GuiErrorList::showEvent it doesn't do anything, and calling setCurrentRow(0) on every update was the

Re: [patch] #2179 LaTeX and chktex error handling problem

OK, I noticed a problem in the last patch. It would cause the error in the ErrorListDialog to become unhighlighted when clicking on the main window. The root cause of the problem appears to be that GuiDialog::updateView calls updateContents, which causes ErrorListDialog to reread all the error

[patch] #2179 LaTeX and chktex error handling problem

How does this patch look? I thought it would be cleaner if I could avoid needing to add the variable "bool need_to_set_row", however I cannot see how this could be done. If I put setCurrentRow(0) in GuiErrorList::showEvent it doesn't do anything, and calling setCurrentRow(0) on every update was

Re: [patch] #2179 LaTeX and chktex error handling problem

OK, I noticed a problem in the last patch. It would cause the error in the ErrorListDialog to become unhighlighted when clicking on the main window. The root cause of the problem appears to be that GuiDialog::updateView calls updateContents, which causes ErrorListDialog to reread all the error

Re: [PATCH] Fix ChkTeX in 1.5.0svn

Has this patch been applied in the mean-time? Michael Georg Baum schrieb: John McCabe-Dansted wrote: On 1/30/07, Georg Baum [EMAIL PROTECTED] wrote: I don't understand why we need to create an absolute path here: Because in 1.5.0svn (but not 1.4.4svn) we get: Assertion

Re: [PATCH] Fix ChkTeX in 1.5.0svn

On 2/7/07, Michael Gerz [EMAIL PROTECTED] wrote: Has this patch been applied in the mean-time? Apparently so. -- John C. McCabe-Dansted PhD Student University of Western Australia

Re: [PATCH] Fix ChkTeX in 1.5.0svn

Has this patch been applied in the mean-time? Michael Georg Baum schrieb: John McCabe-Dansted wrote: On 1/30/07, Georg Baum <[EMAIL PROTECTED]> wrote: I don't understand why we need to create an absolute path here: Because in 1.5.0svn (but not 1.4.4svn) we get: Assertion

Re: [PATCH] Fix ChkTeX in 1.5.0svn

On 2/7/07, Michael Gerz <[EMAIL PROTECTED]> wrote: Has this patch been applied in the mean-time? Apparently so. -- John C. McCabe-Dansted PhD Student University of Western Australia

[PATCH] Fix ChkTeX in 1.5.0svn

to 'path', and ChkTeX gets only relative names, so how can it output the file to a wrong directory? Because the current code in SVN is string const name = getLatexName(false); which does create an absolute path, but it creates a wrong one. If an absolute path is needed then the addPath version

[PATCH] Fix ChkTeX in 1.5.0svn

to 'path', and ChkTeX gets only relative names, so how can it output the file to a wrong directory? Because the current code in SVN is string const name = getLatexName(false); which does create an absolute path, but it creates a wrong one. If an absolute path is needed then the addPath

Re: [PATCH] Fix ChkTeX in 1.5.0svn

John McCabe-Dansted wrote: On 1/30/07, Georg Baum [EMAIL PROTECTED] wrote: I don't understand why we need to create an absolute path here: Because in 1.5.0svn (but not 1.4.4svn) we get: Assertion triggered in lyx::support::FileName::FileName(const std::string) by failing check

Re: [PATCH] Fix ChkTeX in 1.5.0svn

Am Mittwoch, 31. Januar 2007 12:34 schrieb John McCabe-Dansted: So, what do you think of the patch below:? It does not apply. Please send one against current svn, and as attachment please, then it is easier for me to apply. Georg

Re: [PATCH] Fix ChkTeX in 1.5.0svn

to send as well. (I just assumed it was more convenient to read) Most of the patch seems to be already applied. However, in r16997 if you run ChkTeX n times, you get n copies of the errors. Attached patch fixes this problem. -- John C. McCabe-Dansted PhD Student University of Western Australia Index

[PATCH] Fix ChkTeX in 1.5.0svn

t; The current > directory is set to 'path', and ChkTeX gets only relative names, so how can > it output the file to a wrong directory? Because the current code in SVN is string const name = getLatexName(false); which does create an absolute path, but it creates a wrong one.

[PATCH] Fix ChkTeX in 1.5.0svn

t; The current > directory is set to 'path', and ChkTeX gets only relative names, so how can > it output the file to a wrong directory? Because the current code in SVN is string const name = getLatexName(false); which does create an absolute path, but it creates a wrong one.

Re: [PATCH] Fix ChkTeX in 1.5.0svn

John McCabe-Dansted wrote: > > On 1/30/07, Georg Baum > <[EMAIL PROTECTED]> wrote: >> I don't understand why we need to create an absolute path here: > > Because in 1.5.0svn (but not 1.4.4svn) we get: > Assertion triggered in lyx::support::FileName::FileName(const > std::string&) by

Re: [PATCH] Fix ChkTeX in 1.5.0svn

Am Mittwoch, 31. Januar 2007 12:34 schrieb John McCabe-Dansted: > So, what do you think of the patch below:? It does not apply. Please send one against current svn, and as attachment please, then it is easier for me to apply. Georg

Re: [PATCH] Fix ChkTeX in 1.5.0svn

er for me to send as well. (I just assumed it was more convenient to read) Most of the patch seems to be already applied. However, in r16997 if you run ChkTeX n times, you get n copies of the errors. Attached patch fixes this problem. -- John C. McCabe-Dansted PhD Student University of Western

Re: [PATCH] Fix ChkTeX in 1.5.0svn

José == José Matos [EMAIL PROTECTED] writes: José Any objection to apply this patch to trunk? The second part is fine, the first looks bad: @@ -1145,8 +1145,8 @@ busy(true); // get LaTeX-Filename - string const name = getLatexName(false); string const path =

Re: [PATCH] Fix ChkTeX in 1.5.0svn

it is supposed to work nowadays. I don't understand why we need to create an absolute path here: The current directory is set to 'path', and ChkTeX gets only relative names, so how can it output the file to a wrong directory? If an absolute path is needed then the addPath version is almost OK

Re: [PATCH] Fix ChkTeX in 1.5.0svn

> "José" == José Matos <[EMAIL PROTECTED]> writes: José> Any objection to apply this patch to trunk? The second part is fine, the first looks bad: @@ -1145,8 +1145,8 @@ busy(true); // get LaTeX-Filename - string const name = getLatexName(false); string

Re: [PATCH] Fix ChkTeX in 1.5.0svn

ast it should be > string const name = addPath(path, getLatexName()); > > Georg, comments? I am not sure how it is supposed to work nowadays. I don't understand why we need to create an absolute path here: The current directory is set to 'path', and ChkTeX gets only relative names, s

Re: [PATCH] Fix ChkTeX in 1.5.0svn

On Sunday 28 January 2007 4:36:22 am John McCabe-Dansted wrote: On 1/23/07, John McCabe-Dansted [EMAIL PROTECTED] wrote: ChkTex does not create .tex file before running chktex, causing could not run chktex successfully error. This is caused by runChkTeX outputting the .tex file to the same

Re: [PATCH] Fix ChkTeX in 1.5.0svn

On Sunday 28 January 2007 4:36:22 am John McCabe-Dansted wrote: > On 1/23/07, John McCabe-Dansted <[EMAIL PROTECTED]> wrote: > > ChkTex does not create .tex file before running chktex, causing "could > > not run chktex successfully" error. > > This is caused

[PATCH] Fix ChkTeX in 1.5.0svn

On 1/23/07, John McCabe-Dansted [EMAIL PROTECTED] wrote: ChkTex does not create .tex file before running chktex, causing could not run chktex successfully error. This is caused by runChkTeX outputting the .tex file to the same directory as the lyx file. Fixed in the patch below. Even if .tex

[PATCH] Fix ChkTeX in 1.5.0svn

On 1/23/07, John McCabe-Dansted <[EMAIL PROTECTED]> wrote: > ChkTex does not create .tex file before running chktex, causing "could > not run chktex successfully" error. This is caused by runChkTeX outputting the .tex file to the same directory as the lyx file. Fixed in th

Re: chktex support

Michael == Michael Gerz [EMAIL PROTECTED] writes: Michael Hello, do we still want to support chktex for 1.5.0? IMHO its Michael benefit is rather limited in the LyX world. I think it is useful. What would we gain by removing it? JMarc

Re: chktex support

>>>>> "Michael" == Michael Gerz <[EMAIL PROTECTED]> writes: Michael> Hello, do we still want to support chktex for 1.5.0? IMHO its Michael> benefit is rather limited in the LyX world. I think it is useful. What would we gain by removing it? JMarc

Re: chktex support

Michael Gerz wrote: do we still want to support chktex for 1.5.0? IMHO its benefit is rather limited in the LyX world. I use it rarely personally, but I guess John McCabe-Dansted will object: http://wiki.lyx.org/Tools/LyX-GrammarChecker Jürgen

Re: chktex support

Michael Gerz wrote: > do we still want to support chktex for 1.5.0? IMHO its benefit is rather > limited in the LyX world. I use it rarely personally, but I guess John McCabe-Dansted will object: http://wiki.lyx.org/Tools/LyX-GrammarChecker Jürgen

chktex support

Hello, do we still want to support chktex for 1.5.0? IMHO its benefit is rather limited in the LyX world. Michael

chktex support

Hello, do we still want to support chktex for 1.5.0? IMHO its benefit is rather limited in the LyX world. Michael

Re: [PATCH] Bug 2179: LaTeX and chktex error handling problems.

Jean-Marc Lasgouttes wrote: Abdelrazak == Abdelrazak Younes [EMAIL PROTECTED] writes: Abdelrazak OK, now I understand the problem, sorry for my autism ;-). Abdelrazak Then the fix is even simpler for this particular dialog: Abdelrazak just transfer the code in update_contents() to Abdelrazak

Re: [PATCH] Bug 2179: LaTeX and chktex error handling problems.

and the patch... Abdel. Index: QErrorList.C === --- QErrorList.C(revision 14623) +++ QErrorList.C(working copy) @@ -58,8 +58,8 @@ dialog_-errorsLW-addItem(toqstr(it-error)); } -

Re: [PATCH] Bug 2179: LaTeX and chktex error handling problems.

Abdelrazak == Abdelrazak Younes [EMAIL PROTECTED] writes: Abdelrazak Indeed. We could ask QErrorList to re-instantiate the Abdelrazak dialog... But what about this simpler patch instead? The Abdelrazak dialog will not remember its last position but this can be Abdelrazak implemented easily. Did

Re: [PATCH] Bug 2179: LaTeX and chktex error handling problems.

Jean-Marc Lasgouttes wrote: Abdelrazak == Abdelrazak Younes [EMAIL PROTECTED] writes: Abdelrazak Indeed. We could ask QErrorList to re-instantiate the Abdelrazak dialog... But what about this simpler patch instead? The Abdelrazak dialog will not remember its last position but this can be

Re: [PATCH] Bug 2179: LaTeX and chktex error handling problems.

Abdelrazak == Abdelrazak Younes [EMAIL PROTECTED] writes: Abdelrazak Conclusion: for 1.4, please go ahead as it is obviously Abdelrazak the right fix. For 1.5, be warned that, if you implement Abdelrazak it, I might erase it sometimes in the feature ;-) I applied it to 1.4 and did nothing for

Re: [PATCH] Bug 2179: LaTeX and chktex error handling problems.

Jean-Marc Lasgouttes wrote: "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes: Abdelrazak> OK, now I understand the problem, sorry for my autism ;-). Abdelrazak> Then the fix is even simpler for this particular dialog: Abdelrazak> just transfer the code in update_contents() to

Re: [PATCH] Bug 2179: LaTeX and chktex error handling problems.

and the patch... Abdel. Index: QErrorList.C === --- QErrorList.C(revision 14623) +++ QErrorList.C(working copy) @@ -58,8 +58,8 @@ dialog_->errorsLW->addItem(toqstr(it->error)); } -

Re: [PATCH] Bug 2179: LaTeX and chktex error handling problems.

> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes: Abdelrazak> Indeed. We could ask QErrorList to re-instantiate the Abdelrazak> dialog... But what about this simpler patch instead? The Abdelrazak> dialog will not remember its last position but this can be Abdelrazak> implemented

Re: [PATCH] Bug 2179: LaTeX and chktex error handling problems.

Jean-Marc Lasgouttes wrote: "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes: Abdelrazak> Indeed. We could ask QErrorList to re-instantiate the Abdelrazak> dialog... But what about this simpler patch instead? The Abdelrazak> dialog will not remember its last position but this can

Re: [PATCH] Bug 2179: LaTeX and chktex error handling problems.

> "Abdelrazak" == Abdelrazak Younes <[EMAIL PROTECTED]> writes: Abdelrazak> Conclusion: for 1.4, please go ahead as it is obviously Abdelrazak> the right fix. For 1.5, be warned that, if you implement Abdelrazak> it, I might erase it sometimes in the feature ;-) I applied it to 1.4 and did

[PATCH] Bug 2179: LaTeX and chktex error handling problems.

The following patch fixes the highly annoying behaviour of the errorlist inset: every time it gets focus, it acts as if the first error has been selected. This means in practice that it is not possible to fix an error without closing the dialog. This patch is for 1.4. It adds a flag telling

Re: [PATCH] Bug 2179: LaTeX and chktex error handling problems.

Jean-Marc Lasgouttes wrote: The following patch fixes the highly annoying behaviour of the errorlist inset: every time it gets focus, it acts as if the first error has been selected. This means in practice that it is not possible to fix an error without closing the dialog. This patch is for

  1   2   >