[texworks] Mac OS X: request for testing

Otared Kavian otared at gmail.com
Mon Mar 7 05:30:21 CET 2016

Hi Stefan,

I am not familiar with the JS scripting you are using, but the version of babelLanguage.js which is sitting in 
is Version 0.3.1 with date 2012-03-20, and on line 41 there is only a comment. I don’t see what I can change there and make another test.
The first instance of the word « target » appears on line 62. 

By the way, another buglet I have observed in TeXworks concerns the behaviour of window bar in each opened file: in any other Mac application, when Command-clicking the title of the window (that is the name of the file which appears in the middle of the title bar), then one has access to the folder where the file resides. In recent TeXWorks this is not the case, but I think previously this was possible (though I am not sure…).

Regarding the reasons for which I am more TeXShop oreinted, I should say that the first and main reason is probably old habits, and then the fact that TeXShop has had the time to polish things and become more and more Mac savvy. One example is for instance the printing capabilities, another one is the ability to have a sort of Time Machine on each file, which permits to go back in time to any version from the beginning of the creation of the file, and view or copy whatever source text one may have changed during the time.
Also the concept of Engines in TeXShop is very useful when one desires to use different TeX engines on one’s machine (in my case I use often the beta versions of ConTeXt, along with TeXLive).

Indeed the idea of having a cross platform TeX editor is a wonderful one, and I have been advertizing TeXWorks from the beginning.
Thank you for all the work you are doing on TeXWorks.

Best regards: OK

> On 07 Mar 2016, at 04:49, Stefan Löffler <st.loeffler at gmail.com> wrote:
> Hi Otared,
> On 06.03.2016 09:09, Otared Kavian wrote:
>> • After having modified the Preferences according to what you suggested, when Enable QtScript debugger is chosen, a window appears showing the error message:
>> Sun Mar 6 14:46:42 2016 Uncaught exception at /Users/kavian/Library/TeXworks/scripts/babelLanguage.js:41: ReferenceError: Can't find variable: target
>> When this window is closed after having closed the source file TeXWorks crashes… But it does not crash when one closes the debugger window before the source file, and doing this the error window 
>> 	Script "Babel language": ReferenceError: Can't find variable: target
>> is shown again.
>> • When I uncheck the boxes next to Scripts > Scripting TeXworks > Manage Scripts > Hook Scripts the above mentioned behaviour does not change. By the way, there are two instances of « Babel language » under the item Hooks. Maybe one of them is spurious?
> This probably explains everything. The fact that you have two scripts is
> definitely atypical - there should only be one script. The fact that the
> particular error you mention occurs on line 41 suggests to me that the
> "wrong" script dates back to pre-2010: back then
> (https://github.com/TeXworks/texworks/blob/738af76f981be14dd6ba3ed250d8b994e819fd74/res/resfiles/scripts/babelLanguage.js),
> Tw used a slightly different way of communicating with scripts. Since
> then, quite a few things have changed, so the old script is no longer
> running - instead it throws the error. You can simply remove it (it
> should be identifiable by the string "// Version: 0.1" on line 5).
>> Actually I use rather TeXShop, so the behaviour I am reporting on is in order to help you, and other developpers to nail down the culprits, and moreover these buglets are not really important.
> Thanks a lot for testing!
> BTW: is there anything in particular that TeXShop does better in your
> opinion that should be improved in Tw?
> Best,
> Stefan

More information about the texworks mailing list