On 07/04/2012 02:29 AM, Scott Kostyshak wrote:
*From:* Richard Heck [rgh...@comcast.net]
*Sent:* Monday, May 21, 2012 10:20 AM
OK, I see the problem.
Richard, are you able to add this to your todo list? Should I open a
trac ticket?
Sure, thanks.
rh
On 07/04/2012 02:29 AM, Scott Kostyshak wrote:
*From:* Richard Heck [rgh...@comcast.net]
*Sent:* Monday, May 21, 2012 10:20 AM
>OK, I see the problem.
Richard, are you able to add this to your todo list? Should I open a
trac ticket?
Sure, thanks.
rh
From: Richard Heck [rgh...@comcast.net]
Sent: Monday, May 21, 2012 10:20 AM
OK, I see the problem.
Richard, are you able to add this to your todo list? Should I open a trac
ticket?
Thanks,
Scott
From: Richard Heck [rgh...@comcast.net]
Sent: Monday, May 21, 2012 10:20 AM
>OK, I see the problem.
Richard, are you able to add this to your todo list? Should I open a trac
ticket?
Thanks,
Scott
From: Richard Heck [rgh...@comcast.net]
Sent: Monday, May 21, 2012 10:20 AM
That said, the error message is wrong. If there were no text classes, then we
would have told the user this at the beginning of LyX:execCommands(). I guess
the question, then, is: If initial configuration failed, what
From: Richard Heck [rgh...@comcast.net]
Sent: Monday, May 21, 2012 10:20 AM
>That said, the error message is wrong. If there were no text classes, then we
>would have told the user this at >the beginning of LyX:execCommands(). I guess
>the question, then, is: If initial configuration failed,
On 05/21/2012 01:57 AM, Scott Kostyshak wrote:
*From:* Richard Heck [rgh...@comcast.net]
*Sent:* Sunday, May 20, 2012 9:53 AM
I think the GUI is accessible at this point---if use_gui is true. So
you might just try something like:
if (use_gui)
frontend::Alert(...);
else
On 05/21/2012 01:57 AM, Scott Kostyshak wrote:
*From:* Richard Heck [rgh...@comcast.net]
*Sent:* Sunday, May 20, 2012 9:53 AM
>I think the GUI is accessible at this point---if use_gui is true. So
you might just try something like:
>if (use_gui)
>frontend::Alert(...);
>else
>
On 05/19/2012 10:54 PM, Scott Kostyshak wrote:
When you reconfigure by going to Tools Reconfigure, if the python
script returns a non-zero exit status, a useful GUI error is
displayed. However, when configure is run from LyX.cpp on the first
run, you can only see if there is an error in the
From: Richard Heck [rgh...@comcast.net]
Sent: Sunday, May 20, 2012 9:53 AM
I think the GUI is accessible at this point---if use_gui is true. So you might
just try something like:
if (use_gui)
frontend::Alert(...);
else
LYXERR0(...);
at the relevant point. If not, then we
On 05/19/2012 10:54 PM, Scott Kostyshak wrote:
When you reconfigure by going to Tools > Reconfigure, if the python
script returns a non-zero exit status, a useful GUI error is
displayed. However, when configure is run from LyX.cpp on the first
run, you can only see if there is an error in the
From: Richard Heck [rgh...@comcast.net]
Sent: Sunday, May 20, 2012 9:53 AM
>I think the GUI is accessible at this point---if use_gui is true. So you might
>just try something like:
>if (use_gui)
>frontend::Alert(...);
>else
>LYXERR0(...);
>at the relevant point. If not,
12 matches
Mail list logo
