On 15/06/2015 10:03 a.m., aparsloe wrote:
On 15/06/2015 6:18 a.m., Enrico Forestieri wrote:
On Sun, Jun 14, 2015 at 08:44:19PM +1200, aparsloe wrote:
I realise \jobname is highly unlikely to feature in math macros, but
the
problem arises more generally in preview insets where it may well
Am 09.06.2015 um 11:03 schrieb Guenter Milde:
The problem with the current code is this line:
ac_word = ac_prog.split(' ')[0]
Not, if you separate path and program call, e.g.
(path, ac_prog) = os.path.split("path to\binary of\inkscape --help")
would result in:
program call ac_p
Am 09.06.2015 um 20:38 schrieb Georg Baum:
Quoting a path with spaces is definitely needed for the command interpreter,
but in every sane programming language you do not need to do it if you
structure your program a bit. In this case, it means to put the path into
one variable, and the program n
Am 14.06.2015 um 17:58 schrieb Jürgen Spitzmüller:
I investigated: pandoc expects utf8 encoded input files. LyX has to take
care about that. The pandoc manual suggests to go via iconv:
If Pandoc is too buggy, we can revert the support for it.
For me it works, when I remove all appearances of
Am 09.06.2015 um 09:07 schrieb Kornel Benko:
This is only valid if you use 'make', which you doesn't.
For you (since you use visual studio + cmake) it should be
# msbuild /t:layouttranslations1
from the build directory.
Many thanks Kornel,
but this does also not work. What I now did i
Am 09.06.2015 um 14:52 schrieb Richard Heck:
On 06/09/2015 01:07 AM, Liviu Andronic wrote:
On Tue, Jun 9, 2015 at 12:22 AM, Uwe Stöhr wrote:
Am 04.06.2015 um 02:37 schrieb Uwe Stöhr:
Attached is a patch.
No opinions? Should we add support for Pandoc in LyX 2.2 or not?
From a user persp
On 15/06/2015 6:18 a.m., Enrico Forestieri wrote:
On Sun, Jun 14, 2015 at 08:44:19PM +1200, aparsloe wrote:
With all the work done on preview for 2.2, I wonder if the following case
has been considered?
Open a document, myfile.lyx. Define a math macro using \jobname, e.g. so
that the source
On Sun, Jun 14, 2015 at 09:40:46AM -0700, PhilipPirrip wrote:
> I'm bringing this up again with another idea:
> Would you consider adding support, either through a layout file or the
> document settings menu, for the inclusion of auxiliary files that need to be
> copied to the temporary folder whe
On Sun, Jun 14, 2015 at 08:44:19PM +1200, aparsloe wrote:
> With all the work done on preview for 2.2, I wonder if the following case
> has been considered?
>
> Open a document, myfile.lyx. Define a math macro using \jobname, e.g. so
> that the source pane shows \global\long\def\test{\jobname}. N
I'm bringing this up again with another idea:
Would you consider adding support, either through a layout file or the
document settings menu, for the inclusion of auxiliary files that need
to be copied to the temporary folder where and whenever LaTeX
compilation takes place.
This is a possible s
2015-06-14 17:52 GMT+02:00 Jürgen Spitzmüller:
> Hm. When I try to view odt of the Intro manual, pandoc breaks with this
> error:
>
> pandoc: Cannot decode byte '\xfc': Data.Text.Encoding.Fusion.streamUtf8:
> Invalid UTF-8 stream
> Systemcall.cpp (291): Systemcall: 'pandoc -s -f latex -o "Intro.od
2015-06-14 17:27 GMT+02:00 Uwe Stöhr:
> commit 643f9ad4da72a94cee9edc64555ef1a4e7b4b495
> Author: Uwe Stöhr
> Date: Sun Jun 14 17:27:21 2015 +0200
>
> configure.py: add support for pandoc and docx
>
> - make LyX aware of the docx format
> - add converters to odt and docx using the p
2015-06-14 16:04 GMT+02:00 Enrico Forestieri :
> I agree that this would have been better but, unfortunately, it doesn't
> fit the instant preview infrastructure. You wold have to output different
> definitions depending on whether you compile the whole set of snippets
> or only some of them. This
On Sun, Jun 14, 2015 at 01:34:40PM +0200, Jürgen Spitzmüller wrote:
> 2015-06-14 13:31 GMT+02:00 Enrico Forestieri :
>
> > Jürgen, this is going to become complicated and fragile. What about
> > following the same strategy used in stable?
> > This implies reverting bc47054b.
> >
>
> Since I do n
The attached patch checks for uncodable glyphs in the user preamble and
issues a warning if such glyphs are found (like we do in many other
situations).
Comments?
Jürgen
diff --git a/src/BufferParams.cpp b/src/BufferParams.cpp
index 269c74c..f42211b 100644
--- a/src/BufferParams.cpp
+++ b/src/Buf
2015-06-14 13:31 GMT+02:00 Enrico Forestieri :
> Jürgen, this is going to become complicated and fragile. What about
> following the same strategy used in stable?
> This implies reverting bc47054b.
>
Since I do not have time to investigate further, please do whatever you see
fit.
I would have pr
On Thu, Jun 04, 2015 at 07:25:25PM +0200, Enrico Forestieri wrote:
> On Thu, Jun 04, 2015 at 06:56:46PM +0200, Jürgen Spitzmüller wrote:
> > 2015-06-04 18:39 GMT+02:00 Enrico Forestieri :
> >
> > > Yes, I can reproduce in master. It does not occur in stable, where a
> > > different strategy is us
On Sun, Jun 14, 2015 at 2:27 AM, Jean-Marc Lasgouttes
wrote:
> Yes I'd prefer to see such a tag that yet another document setting or pref.
>
Placed the request here:
http://www.lyx.org/trac/ticket/9623
Liviu
> JMarc
>
>
> Le 14 juin 2015 02:19:07 CEST, Richard Heck a écrit :
>>
>> On 06/13/
With all the work done on preview for 2.2, I wonder if the following
case has been considered?
Open a document, myfile.lyx. Define a math macro using \jobname, e.g. so
that the source pane shows \global\long\def\test{\jobname}. Now in a
math inset write \test. In 2.1.3 this previews to somethi
19 matches
Mail list logo
