Compile without menubar; command subsystem

[Max Rottenkolber]

Hi scite-interest,

Can anyone give me instructions on how to compile scite without the menubar? I read in another thread that this is what I need to do in order to get rid of it.

Also I could not quite understand from the manual how to execute a specified 'go' command in the background (on linux) without sending its output back to scite (output window).

Cheers,
Max

[Philippe Lhoste]

On 13/11/2012 21:21, Max Rottenkolber wrote:
> Can anyone give me instructions on how to compile scite without the menubar? I read in
> another thread that this is what I need to do in order to get rid of it.

Not sure why you would want that. I suppose it would need a number of tweaks to various
files, so it isn't trivial (but probably not so hard).

> Also I could not quite understand from the manual how to execute a specified 'go'
> command in the background (on linux) without sending its output back to scite (output
> window).

SciTE has the command.quiet.number.filepattern property, but it is available only for
Windows, for an unknown reason.

--
Philippe Lhoste
-- (near) Paris -- France
-- http://Phi.Lho.free.fr
-- -- -- -- -- -- -- -- -- -- -- -- -- --

[Max Rottenkolber]

Philippe Lhoste <Phi...@GMX.net> wrote:

>On 13/11/2012 21:21, Max Rottenkolber wrote:
>> Can anyone give me instructions on how to compile scite without the
>menubar? I read in
>> another thread that this is what I need to do in order to get rid of
>it.
>
>Not sure why you would want that. I suppose it would need a number of
>tweaks to various
>files, so it isn't trivial (but probably not so hard).

I dont need the menu bar (at all) so for me it only wastes screen space. The devs could consider this a feature request: an option to hide the menu bar (just like the toolbar).

>> Also I could not quite understand from the manual how to execute a
>specified 'go'
>> command in the background (on linux) without sending its output back
>to scite (output
>> window).
>
>SciTE has the command.quiet.number.filepattern property, but it is
>available only for
>Windows, for an unknown reason.

I tried command.go.2.* but that doesnt work, which I think is a bug, since the documentation suggests that. (the doc is misleading too since it says 'command.go.subsystem.filepattern' where only filepattern is set italic.

Cheers,
Max