[dev-context] SciTE on linux

[Hans Hagen]

Taco Hoekwater wrote:

> SciTE is slowly growing on me. Hans, can you remove or guard
> these lines from context.properties, please?
>
>   # WINDOWS-ONLY!!
>   eol.mode=CRLF
>
ok

> Some bits of my user file may be of interest:
>
>   # from tex.properties, accidentally? cleaned by context.properties
>   file.patterns.tex=*.tex;*.sty;

not here

>   # also from tex.properties, but with 'cls' added
>   file.patterns.latex=*.tex;*.sty;*.aux;*.toc;*.idx;*.cls;

ok

>
>   # these were undefined, it seems
>   filter.tex=plain TeX|$(file.patterns.tex)|
>   filter.latex=LaTeX|$(file.patterns.latex)|
>
i hope that does not clash

>   # invented by me
>   file.patterns.texmplog=*.log;*.blg;*.ilg;*.err;*.fls
>   filter.log=TeX&MP logs|$(file.patterns.texmplog)|

isn't that: filter.texmplog

>
>   open.filter=$(all.files)

?

> \ # .......................
>   # ...........
>
>   # personal preference: i like tabs
>   tabbar.hide.one=0

what does this one do?

>
>   # rxvt is a reasonable default on linux
>   name.context.console=rxvt
>   # but konsole is the kde terminal, and I like that even better
>   name.context.console=konsole

ok

>
>   # the shell script to call xpdf in server mode
>   name.context.acrobat=xpdfopen

ok

>
>   # patched texexec
>   name.context.texexec=texmfstart texexec.pl --xpdf

ok, i introduced

name.texexec.flag.pdfopen=--autopdf --xpdf

>
>   # bugfix for Gtk version of SciTE
>   command.compile.$(file.patterns.context)= \
>           $(name.context.texexec) --pdf $(FileNameExt)
>   command.build.$(file.patterns.context)= \
>           $(name.context.texexec) --autopdf --pdf $(FileNameExt)
>
>
> I had to create separate compile and build commands. With SciTE on 
> linux, when the pdf browser is started from within texexec, the build
> command never exits: the menu remain disabled after the first run,
> until such time as you quit the browser manually. It does not matter
> whether texmfstart returns to the commandline, Scite waits for all
> the (grand)children to exit.

so maybe it's better in gtk mode to omit --autopdf ?

>
> Setting
>
>    command.build.subsystem.$(file.patterns.context)=2
>
> does not help, because then I get nothing in the output window. So
> now I do first Ctrl-f7 (compile), then F5 (go), then F7 thereafter.
>
> Not ideal, but I could not come up with a better solution.
>
>
>
> Hans Hagen wrote:
>
>> Taco Hoekwater wrote:
>>
>>> Hans Hagen wrote:
>>>
>>>> so we need:
>>>>
>>>> if PLAT_WIN
>>>>    font.monospace=font:LMTypewriter10,size:16.5
>>>>    font.errorfont=font:LMTypewriter10,size:11.5
>>>>
>>>> if PLAT_GTK
>>>>    font.monospace=font:!LMTypewriter10 Regular,size:16.5
>>>>    font.errorfont=font:!LMTypewriter10 Regular,size:11.5
>>>
>>>
>>>
>> can't we add your variant to the distribution (font part or tex live)?
>>
>> btw, such things fit into the font cd project
>>
>>>
>>> Not so sure. Perhaps you should not set the font on linux
>>> at all. I had to do perform quite some magic to get a usable
>>> lmtypewriter on linux, and I doubt many people will want to
>>> go through that (on X11, not setting any font is much better
>>> than attempting to set a non-existant one).
>>
>>
>>
>>
>> scite ignores that, at least on windows, it then uses its fall back font
>>
>> Hans
>


-- 

-----------------------------------------------------------------
                                          Hans Hagen | PRAGMA ADE
              Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                             | www.pragma-pod.nl
-----------------------------------------------------------------