> "Joost" == Joost Verburg <[EMAIL PROTECTED]> writes:
Joost> Bo Peng wrote:
>> Done. Although I do not know why you want to write a new hidecmd.c.
Joost> Did you ask Jean-Marc to review the patch? It's quite trivial,
Joost> but I think he would have liked to see it.
I did not think it would
I have written a wrapper that sets environment variables etc. based on
the settings of the LyX installer, contains an icon and version
information and shows the console output when LyX crashes (with
bug-report instructions).
This sounds very good and I can not wait to see it working (and use it
Bo Peng wrote:
Done. Although I do not know why you want to write a new hidecmd.c.
Did you ask Jean-Marc to review the patch? It's quite trivial, but I
think he would have liked to see it.
I have written a wrapper that sets environment variables etc. based on
the settings of the LyX install
> The patch is attached. Please read instructions in hidecmd.C on how to
> use it and test if the patch works as expected.
Thanks! It works fine. Please upload only the change to os_win32.C. I'm
going to write a new wrapper to replace hidecmd.c tomorrow.
Done. Although I do not know why you wan
Bo Peng wrote:
The patch is attached. Please read instructions in hidecmd.C on how to
use it and test if the patch works as expected.
Thanks! It works fine. Please upload only the change to os_win32.C. I'm
going to write a new wrapper to replace hidecmd.c tomorrow.
Joost
> Bo, can you please post the patch again?
Yes. I will prepare one today.
Hi, Joost,
The patch is attached. Please read instructions in hidecmd.C on how to
use it and test if the patch works as expected.
Thanks.
Bo
Index: src/support/os_win32.C
> It looks good, but as always I'll have to see it before saying 'yes'.
Bo, can you please post the patch again?
Yes. I will prepare one today.
> Concerning the use of a wrapper, I am OK with it as long as LyX can
> run (maybe not as well) without the wrapper. Otherwise, this has to
> become
Jean-Marc Lasgouttes wrote:
It looks good, but as always I'll have to see it before saying 'yes'.
Bo, can you please post the patch again?
Concerning the use of a wrapper, I am OK with it as long as LyX can
run (maybe not as well) without the wrapper. Otherwise, this has to
become part of LyX
> "Joost" == Joost Verburg <[EMAIL PROTECTED]> writes:
Joost> Do you agree to apply the patch to 1.4? I will create a Windows
Joost> wrapper that handles everything including debug output. I can
Joost> even add a quality feedback wizard that allows users to report
Joost> crashes automatically.
Jean-Marc Lasgouttes wrote:
Or we could have a 'show console' menu entry. It would be useful for
other platforms too, but I am not sure how to do it.
I'm not sure. If someone wants console output, LyX can be started from
the terminal. Windows users can also start lyxc.exe. There should not be
> "Joost" == Joost Verburg <[EMAIL PROTECTED]> writes:
Joost> I think they should only be displayed when something is wrong
Joost> (the wrapper can do that). It is not a good thing to show lists
Joost> of console output the first time a user starts LyX, especially
Joost> not on Windows.
Or we
Joost Verburg wrote:
> I think they should only be displayed when something is wrong (the
> wrapper can do that). It is not a good thing to show lists of console
> output the first time a user starts LyX, especially not on Windows.
I agree, but I would expect this to happen after pressing the rec
Georg Baum wrote:
The log file is fine for e.g. messages from converters etc, but in the case
of configure.py the best solution would be if a new window would pop up
where one could watch the messages in real time, since these are normally
more important.
I think they should only be displayed w
Joost Verburg wrote:
> Jean-Marc Lasgouttes wrote:
>> Something clearly needs to be done for the console in windows.
>> Actually it should always be hidden, but it should be possible for the
>> user to recover its content if needed. I do not know how this could be
>> done, though.
>
> The method
Jean-Marc Lasgouttes wrote:
Something clearly needs to be done for the console in windows.
Actually it should always be hidden, but it should be possible for the
user to recover its content if needed. I do not know how this could be
done, though.
The method in LyX 1.5 solves this problem. The w
> "Joost" == Joost Verburg <[EMAIL PROTECTED]> writes:
Joost> Hi, If I remember correctly, LyX 1.5 on Windows is now a
Joost> console application. A wrapper will be used to setup the
Joost> environment and hide the console window.
Joost> Can the new method be applied to 1.4 as well? I think t
Jean-Marc, is this OK for 1.4? Bo, you added this feature to 1.5, right?
Is everything identical for 1.4?
The patch is minimal in that it removes the console hiding lines (10
lines?) and add a wrapper (hidecmd.c) file. It should not break
anything.
Bo
17 matches
Mail list logo
