[texworks] Call for Help: Testing for Tw 0.4.4

Stefan Löffler st.loeffler at gmail.com
Sun Apr 1 15:59:53 CEST 2012


On 2012-03-30 18:14, Andreas Hirsch wrote:
> Hi Stefan,
> quoting Stefan Löffler, [29.03.2012 12:22 +0100]:
>> Particular things that were changed recently and would benefit from testing:
>>  * the log parser (which was rewritten, mainly by Antonia and Henrik, to
>> handle long filenames, latexmk, etc.)
>>  * search/replace (in particular multi-line copy-to-search and
>> copy-to-replace, but also replace w/ wrapping)
> Could you give me a few hints what to test in detail?

Regarding the log parse: does it work as expected in normal situations
(i.e., does it display complete (meaningful, as far as they can be)
error messages, does it give (correct) line numbers, does it give
correct filenames, does clicking on the filename take you to the correct
line in the correct file.

Regarding search/replace: the new additions treat two things.

First, copy-to-search / copy-to-replace of multi-line strings (i.e.,
select 2 or more (possibly partial) lines of text, do copy-to-find, do
"find" or "find again"; it should correctly find the selected string
(previously, multi-line selections did not work)). See also:
Note that this automatically turns on the "reg exp" flag. Existing
strings should be escaped as necessary. Also, subsequent searches (even
without multiline) should succeed.

Second, "replace" with "wrap around" should work as expected now. See
also: http://code.google.com/p/texworks/issues/detail?id=144

In any case, normal search/replace should work as expected/before.

>>  * The issue http://code.google.com/p/texworks/issues/detail?id=568
>> which I can't be able to reproduce at the moment
> I was able to reproduce the situation:

Thanks for testing. In the meantime, I've been able to reproduce this,
too. I also found a workaround for this problem over at
In r980 and later, this issue should be gone.


More information about the texworks mailing list