On Sat, Dec 19, 2009 at 09:33:15PM -0500, Ben M. wrote:
> On Sat, Dec 19, 2009 at 9:14 PM, Enrico Forestieri wrote:
> > On Sat, Dec 19, 2009 at 07:04:09PM -0500, Ben M. wrote:
> >> Yes, there must be a better way. For instance, I noticed that an
> >> executed command inherits its environment from
On Sat, Dec 19, 2009 at 9:14 PM, Enrico Forestieri wrote:
> On Sat, Dec 19, 2009 at 07:04:09PM -0500, Ben M. wrote:
>> Yes, there must be a better way. For instance, I noticed that an
>> executed command inherits its environment from LyX, e.g. "PATH
>> prefix." Why not create environment variable
On Sat, Dec 19, 2009 at 09:18:23PM -0500, Ben M. wrote:
> Thanks so much to both of you for all the feedback!
>
> On Sat, Dec 19, 2009 at 9:05 PM, Enrico Forestieri wrote:
> > On Sat, Dec 19, 2009 at 10:23:17AM -0500, rgheck wrote:
> >> This will be hard to get right, since you can install LyX a
Thanks so much to both of you for all the feedback!
On Sat, Dec 19, 2009 at 9:05 PM, Enrico Forestieri wrote:
> On Sat, Dec 19, 2009 at 10:23:17AM -0500, rgheck wrote:
>> This will be hard to get right, since you can install LyX anywhere.
>
> True, but those will surely catch 99% of cases.
Won't
On Sat, Dec 19, 2009 at 07:04:09PM -0500, Ben M. wrote:
> On Sat, Dec 19, 2009 at 10:23 AM, rgheck wrote:
> >> LYXSYSDIRS = ["/usr/share/lyx", "/usr/local/share/lyx",
> >> "/opt/share/lyx"]
> >>
> > This will be hard to get right, since you can install LyX anywhere.
> >
> >> LYXBASEDIR = ["
On Sat, Dec 19, 2009 at 10:23:17AM -0500, rgheck wrote:
> >if OSTYPE == "macos":
> >LYXSYSDIRS = ["/Applications/LyX.app/Contents/Resources"]
> >LYXBASEDIR = ["LyX" + version_suffix]
> >old_dir = os.getcwd()
> >os.chdir(HOME + "/Library/Application Support")
> >elif OSTYPE == "win3
On Sat, Dec 19, 2009 at 06:58:29AM -0500, Ben M. wrote:
> Okay, here's a very rough draft. This is the first thing I've written
> in Python, so some things are very ugly. It works for me under Win32,
> but I haven't tested under anything else.
I also tested it on Linux and Cygwin. See comments
On Sat, Dec 19, 2009 at 10:23 AM, rgheck wrote:
>> LYXSYSDIRS = ["/usr/share/lyx", "/usr/local/share/lyx",
>> "/opt/share/lyx"]
>>
> This will be hard to get right, since you can install LyX anywhere.
>
>> LYXBASEDIR = [".lyx" + version_suffix]
>>
> This again will be hard to get right. (For
Abdelrazak Younes wrote:
> On 19/12/2009 12:43, Peter Kümmel wrote:
>>> I implemented that approach now in trunk. But by cloning the Buffer as
>>> this was the cleanest approach and less intrusive approach. It works
>>> well except for the lack of feedback on the background processing.
>>>
>>> Abde
Vincent van Ravesteijn wrote:
>> When I change the function parameter for format from docstring to
>> std:string I get linker errors with mavc, because of missing
>> previewAndDestroy and exportAndDestroy, stange.
>> Thereforethe from_utf8 function.
>>
>> Peter
>>
>>
> I can just change the form
Abdelrazak Younes wrote:
>> No not here. Would this patch be OK?
>>
>
> Yes, my bad.
Any ideas why
static docstring exportAndDestroy(Buffer * buffer, std::string const & format)
does not work? Qt without stl support?
Peter
When I change the function parameter for format from docstring to
std:string I get linker errors with mavc, because of missing
previewAndDestroy and exportAndDestroy, stange.
Thereforethe from_utf8 function.
Peter
I can just change the format type to string without any problems (msvc
as we
On 19/12/2009 20:31, Peter Kümmel wrote:
Vincent van Ravesteijn wrote:
But preview is still broken under Windows.
Peter
I didn't fix it ?
Vincent
No not here. Would this patch be OK?
Yes, my bad.
Abdel.
Enrico Forestieri wrote:
> On Sat, Dec 19, 2009 at 07:20:57PM +0100, Peter Kümmel wrote:
>
>> OK, htlatex needs the ! as argument and ! has here no bash functionality.
>> Under Windows unquoted should work, because no bash there.
>> But what should we do on Linux? As the bug report says single quo
Vincent van Ravesteijn wrote:
>> But preview is still broken under Windows.
>>
>> Peter
>>
>
> I didn't fix it ?
>
> Vincent
>
No not here. Would this patch be OK?
Index: src/frontends/qt4/GuiView.cpp
===
--- src/frontends/qt4/
On Sat, Dec 19, 2009 at 07:20:57PM +0100, Peter Kümmel wrote:
> OK, htlatex needs the ! as argument and ! has here no bash functionality.
> Under Windows unquoted should work, because no bash there.
> But what should we do on Linux? As the bug report says single quotes does not
> work.
> One way
But preview is still broken under Windows.
Peter
I didn't fix it ?
Vincent
Peter Kümmel wrote:
> If it's really needed I could move it to trunk, would not be very complicated.
yes it would be nice to have it. i even imagine line of checkboxes on the top
each for one debug level to toggle - that would be quite useful for debugging
purposes. also user reports could be more
Pavel Sanda wrote:
> Abdelrazak Younes wrote:
>> 2) Use the same signal/slot mechanism for Buffer::message().
>
> btw in the old process branch there was implemnted new output window for
> console
> messages. how hard it would be to make it work the current trunk? it would be
> good
> to have th
Enrico Forestieri wrote:
> On Sat, Dec 19, 2009 at 12:35:17PM +0100, Peter Kümmel wrote:
>> Am Samstag, den 19.12.2009, 12:22 +0100 schrieb Peter Kümmel:
>>> The doc to htlatex says:
>>> "In some platforms the double quotes should be replaced with single
>>> right-quotes, and in some cases they mig
Tommaso Cucinotta wrote:
> in the lyx trac tickets, what is the difference between:
> 1. tagging a bug with the "fixedintrunk" keyword (but not closing it)
This bug is still there in the latest stable version.
> 2. closing a bug with the "resolve as fixed"
The latest stable release contains the
Tommaso Cucinotta schreef:
Hello,
in the lyx trac tickets, what is the difference between:
1. tagging a bug with the "fixedintrunk" keyword (but not closing it)
2. closing a bug with the "resolve as fixed"
Assuming one of the bugs of the "advanced search" facility is fixed
(which only exists i
On Sat, Dec 19, 2009 at 12:35:17PM +0100, Peter Kümmel wrote:
> Am Samstag, den 19.12.2009, 12:22 +0100 schrieb Peter Kümmel:
> > The doc to htlatex says:
> > "In some platforms the double quotes should be replaced with single
> > right-quotes, and in some cases they might be omitted."
> > http://w
Hello,
in the lyx trac tickets, what is the difference between:
1. tagging a bug with the "fixedintrunk" keyword (but not closing it)
2. closing a bug with the "resolve as fixed"
Assuming one of the bugs of the "advanced search" facility is fixed
(which only exists in trunk), which one applies
On 19/12/2009 16:42, Enrico Forestieri wrote:
I've reworked the parser for QProcess in order to implement a shell-like parser
also accounting for single-quote quoting in a platform independent way. I am
going to commit the patch, but the last changes by Abdel broke output generation
as I am not a
On 19/12/2009 16:46, v...@lyx.org wrote:
Author: vfr Date: Sat Dec 19 16:46:45 2009 New Revision: 32589 URL:
http://www.lyx.org/trac/changeset/32589
Log: Fix the threaded preview and reenable it.
Good boy :-)
Buffer::Impl::inset was set in the ctor Buffer::Impl::Impl to be a
clone. However,
On Saturday 19 December 2009 15:42:47 Enrico Forestieri wrote:
> > Furthermore, lyx2lyx still fails if the path contains a '
> > character. This is branch. I didn't test trunk.
>
> Then, there's a quoting problem in python, too.
That only depends on the way we are passing the arguments:
$ cat t
On Sat, Dec 19, 2009 at 02:53:05PM +0100, Pavel Sanda wrote:
> Abdelrazak Younes wrote:
> > On 19/12/2009 12:54, Abdelrazak Younes wrote:
> >> Menu -> view or update (pdflatex or dvi) works fine here (as well as
> >> Ctrl+D or T)
> >
> > Hum, it does not work anymore... latex complain about an em
Abdelrazak Younes schreef:
On 19/12/2009 14:53, Pavel Sanda wrote:
Abdelrazak Younes wrote:
On 19/12/2009 12:54, Abdelrazak Younes wrote:
Menu -> view or update (pdflatex or dvi) works fine here (as well as
Ctrl+D or T)
Hum, it does not work anymore... latex complain about an
On Sat, Dec 19, 2009 at 02:38:29PM +0100, Jürgen Spitzmüller wrote:
> Peter Kümmel wrote:
> > I could not reproduce this bug with trunk:
> > - USB-stick name : Stick'N'Go
> > - copied BRANCH_1_4_X/lib to stick
> > - opened UserGuide.lyx from stick
> > - PDF is generated without errors
> >
> > Is t
On 12/19/2009 06:58 AM, Ben M. wrote:
On Fri, Dec 18, 2009 at 5:42 PM, Enrico Forestieri wrote:
Yep, as I said, in development/tools there is a shell script (lyxeditor)
that parses the preferences file and lyxrc.dist for the lyxpipe definition.
It works on Linux, MacOS, and Cygwin. It would
FYI I'm offline for the next two weeks (starting from tomorrow).
Have a nice time everybody, see you next year.
Jürgen
On 19/12/2009 14:53, Pavel Sanda wrote:
Abdelrazak Younes wrote:
On 19/12/2009 12:54, Abdelrazak Younes wrote:
Menu -> view or update (pdflatex or dvi) works fine here (as well as
Ctrl+D or T)
Hum, it does not work anymore... latex complain about an empty file...
weird... It
Abdelrazak Younes wrote:
> On 19/12/2009 12:54, Abdelrazak Younes wrote:
>> Menu -> view or update (pdflatex or dvi) works fine here (as well as
>> Ctrl+D or T)
>
> Hum, it does not work anymore... latex complain about an empty file...
> weird... It was working just fine yesterday before I commit
Peter Kümmel wrote:
> I could not reproduce this bug with trunk:
> - USB-stick name : Stick'N'Go
> - copied BRANCH_1_4_X/lib to stick
> - opened UserGuide.lyx from stick
> - PDF is generated without errors
>
> Is this the right way to reproduce?
> If yes then, it is not a bug for trunk any more.
On 19/12/2009 14:18, Abdelrazak Younes wrote:
On 19/12/2009 12:54, Abdelrazak Younes wrote:
Menu -> view or update (pdflatex or dvi) works fine here (as well as
Ctrl+D or T)
Hum, it does not work anymore... latex complain about an empty file...
weird... It was working just fine yesterday befo
On 19/12/2009 12:54, Abdelrazak Younes wrote:
Menu -> view or update (pdflatex or dvi) works fine here (as well as
Ctrl+D or T)
Hum, it does not work anymore... latex complain about an empty file...
weird... It was working just fine yesterday before I commit.
Abdel.
Abdelrazak Younes wrote:
> 2) Use the same signal/slot mechanism for Buffer::message().
btw in the old process branch there was implemnted new output window for console
messages. how hard it would be to make it work the current trunk? it would be
good
to have this for latex output in background a
On Fri, Dec 18, 2009 at 5:42 PM, Enrico Forestieri wrote:
> Yep, as I said, in development/tools there is a shell script (lyxeditor)
> that parses the preferences file and lyxrc.dist for the lyxpipe definition.
> It works on Linux, MacOS, and Cygwin. It would be easy to extend it to
> also work on
On 19/12/2009 12:43, Peter Kümmel wrote:
I implemented that approach now in trunk. But by cloning the Buffer as
this was the cleanest approach and less intrusive approach. It works
well except for the lack of feedback on the background processing.
Abdel.
Great, if it works we could remove
> I implemented that approach now in trunk. But by cloning the Buffer as
> this was the cleanest approach and less intrusive approach. It works
> well except for the lack of feedback on the background processing.
>
> Abdel.
Great, if it works we could remove
QCoreApplication::processEvents(QEve
Am Samstag, den 19.12.2009, 12:22 +0100 schrieb Peter Kümmel:
> Am Freitag, den 18.12.2009, 23:33 +0100 schrieb Enrico Forestieri:
> > > configure.py should still be OK, because the quotes
> > > the are du to spaces in filenames only, hope I'm not
> > > totally wrong here, too.
> >
> > I don't use
On 10/12/2009 15:43, Abdelrazak Younes wrote:
Pavel Sanda wrote:
Jean-Marc Lasgouttes wrote:
the real work
on our buffer structure can be fast enough IMO.
it is not? pavel
It is, and that is not the problem. The LateX export can happen in
the main thread. The problem is elsewhere in that we
Am Samstag, den 19.12.2009, 09:25 +0100 schrieb Jürgen Spitzmüller:
> Enrico Forestieri wrote:
> > > Thanks, I didn't thought someone likes single quotes
> > > in his filenames. I've reverted the Systemcall.cpp patch.
> >
> > Thanks. I have also committed a patch such that file names can now also
Am Freitag, den 18.12.2009, 23:33 +0100 schrieb Enrico Forestieri:
> > configure.py should still be OK, because the quotes
> > the are du to spaces in filenames only, hope I'm not
> > totally wrong here, too.
>
> I don't use htlatex, so I really don't know. However, if the single quotes
> were mea
Enrico Forestieri wrote:
> > Thanks, I didn't thought someone likes single quotes
> > in his filenames. I've reverted the Systemcall.cpp patch.
>
> Thanks. I have also committed a patch such that file names can now also
> contain the double quote character. Note that on *nix you can use any
> char
46 matches
Mail list logo
