Re: [LyX/master] Partial fix for #9740 "XeTeX/LuaTeX with TeX fonts problems".

Guenter Milde wrote: > Just to be sure we don't misunderstand: The question is about tests > compiling the documentation "as-is" (i.e. with *TeX fonts*) using > XeTeX. Thanks for the clarification, I think we misunderstood. For XeTeX + TeX fonts I agree. > For me, Development.lyx compiles fine

Re: [LyX/master] Fix export with polyglossia and uninvert a manual

Scott Kostyshak wrote: > -% increase link area for cross-references and autoname them, > -\AtBeginDocument{\renewcommand{\ref}[1]{\mbox{\autoref{#1 > -\addto\extrasfrench{% > - \renewcommand*{\equationautorefname}[1]{}% > - \renewcommand{\sectionautorefname}{sec.\negthinspace}% > - \renewcomma

Re: status update on the export tests

Scott Kostyshak wrote: > The following tests are currently expected to fail because of issues with > nested language handling and polyglossia. Georg, if you still have > interest and time for fixing this type of issue, take a look at these: > > export/doc/nb/Intro_pdf5_systemF > export/doc/sk/Int

Re: [LyX/master] colored-boxes.lyx: new example file for the tcolorbox.module

Scott Kostyshak wrote: > On Fri, Oct 23, 2015 at 10:01:42AM +0200, Jean-Marc Lasgouttes wrote: > >> >It saves some time because I don't need to write all the sime "see >> >sec._" (where _ is a half space) but only "see ". Furthermore one has a >> >larger area to click on in the PDF. personally it

Re: [LyX/master] Revert the box alignment part of 8010b90c

Uwe Stöhr wrote: > Hi Georg, > > it is OK with me if you reverted this for good reasons, I only want to > understand why you reverted and how the feature I implemented will be > available now. I reverted to get rid of a regression you introduced. If you want more details, please read the commit

Re: [LyX/master] Partial fix for #9740 "XeTeX/LuaTeX with TeX fonts problems".

Guenter Milde wrote: > On 2015-10-21, Scott Kostyshak wrote: > >> It compiles fine before this commit. > > Yes, but only "per accident": Development.lyx only uses some non-ASCII > characters, and these are also at the same place in Unicode and T1. It was not by accident. It did compile before c

Re: Many tex2lyx failing now on master

Richard Heck wrote: > Yes, I was just talking about the mention of lyx2lyx, so maybe we are at > cross purposes. But one certainly could have two format N .lyx files and > two format N+1 .lyx files---one each for forward and one for backward > conversion---and test whether lyx2lyx gets you the rig

Re: [PATCH] Re: Regression in lyx2lyx box alignment

Jean-Marc Lasgouttes wrote: > Actually fixing this for LR boxes (so-called makebox in the code) is not > difficult because we have the framework for table cells already. I > propose to put that in master. Would it be OK? I did not know that mechanism. This looks indeed nice. However, I wonder wh

Re: When to court Qt 5.6?

Vincent van Ravesteijn wrote: > First, it looks like that the 2010 libraries can work with at least MSVC > 2012. Is that because MSVC 2010 is or was also installed on the same > machine? If so, releasing such a hybrid might give troubles that won't be > foreseen. So, better to warn Uwe as he claim

Re: Many tex2lyx failing now on master

Guenter Milde wrote: > Maybe a suggestion to provide a minimal example of the new feature > requiring the file format change in form of a *.lyx or *.tex file that > can either be simply added to the test base (if tex2lyx works fine) or > put on in a set of "TODO examples". > > Whether we provide

Re: Many tex2lyx failing now on master

Guenter Milde wrote: > On 2015-10-20, Georg Baum wrote: > >> Just to avoid future errors: I assume that you did check before that a >> simple update of the format number is OK, and that no tex2lyx source code >> changes are needed? How to do such checks in des

Re: Regression in lyx2lyx box alignment

Uwe Stöhr wrote: > Nevertheless one must discuss how useful the tests are if they make so > many troubled what anybody just changed a layout file without touching > tex2lyx. I still think that the main purpose of the tex2lyx tests should > be to test tex2lyx capabilities. Exactly, and this is wha

Re: Regression in lyx2lyx box alignment

Jean-Marc Lasgouttes wrote: > Le 20/10/2015 23:46, Uwe Stöhr a écrit : >> Georg, attached are 2 documents, one created with LyX 2.1. where I used >> the paragraph settings to center, one created with LyX 2.2. You see the >> difference: The Paragraph-alignment added a paragraph of course leading >>

Re: Regression in lyx2lyx box alignment

Uwe Stöhr wrote: > ( I see now in mail-archive.com this thread. It would have been nice to > send me at least a direct mail to assure that I am informed. In the past > I could read the list via NNTP but my ISP dropped that feature. When I > am abroad I don't read mail-archive.com .) Do you mean t

Re: Regression in lyx2lyx box alignment

Scott Kostyshak wrote: > After rereading the below email I just realized I often use the term > "we" and "us". Sorry about that. I do not mean to pretend like I am > speaking on behalf of everyone (I do not forget that I am a relative > newcommer here!). Instead of taking the time to correct all t

Re: When to court Qt 5.6?

Uwe Stöhr wrote: > Besides this I am still using MSVC 2010. I need to update to MSVC 2012 > or newer and this is another challenge. I already tested MSVC 2012 with > Qt 5.5 with success. Let's see what Qt 5.6 supports and if I can then > still compile LyX 2.1.x with Qt 4.x and MSVC 2010 on the sam

Re: Many tex2lyx failing now on master

Guenter Milde wrote: > On 2015-10-19, Uwe Stöhr wrote: > >> I don't understand what I made wrong. I only changed something in a >> module and added a fileformat change for lyx2lyx. I did not change any >> tex2lxy test file nor did I change tex2lyx code. It is all documented in Development.lyx.

Re: LyX's master is now uncompilable

Guillaume Munch wrote: > I'll let Vincent decide whether he wants to make this change. Sure, our messages crossed each other, I would not have suggested that if I knew that he had time to test. The compilation error could btw easily be fixed by moving the implementation of the methods in a .cp

Re: Many tex2lyx failing now on master

Guenter Milde wrote: > I updated the lyxformat number in the src/tex2lyx/test/*.lyx.lyx files and > now all tex2lyx tests pass here. Very good. Just to avoid future errors: I assume that you did check before that a simple update of the format number is OK, and that no tex2lyx source code chang

Re: LyX's master is now uncompilable

Guillaume Munch wrote: > The former. If we are supposed to include support/docstream.h to use > odocstringstream, shouldn't the latter be defined in docstream.h instead > of strfwd.h? (or the fix be moved to strfwd.h which is already included > by docstream.h via docstring.h?) That was the missin

Re: bug 9626: new handling of "LyX" is unintuitive

PhilipPirrip wrote: > On 10/18/2015 02:01 PM, Georg Baum wrote: >> - rename the top level menu "Special Characters" to "Special Characters & >> Strings" > > > This is what a programmer would call it, but I think this is just too > long fo

Re: LyX's master is now uncompilable

Guillaume Munch wrote: > Is that all the information that the compiler gives you? Does it not > give you the name of the file? This is the kind of error messages you often get from templates. The compiler gives the name of the file where the error occurs, but it is a system header and not in our

Re: Many tex2lyx failing now on master

Scott Kostyshak wrote: > Many tex2lyx tests have started to fail (before it was just 4 and we > knew why and I think Günter's recent commit might have fixed them?). Now > 14 are failing. If you look at the differences between the test references and the actual results you see only changed format

Re: [patches] the last ones before 2.2

Guillaume Munch wrote: > I hope I did not put you on a wrong track with my reference to the gcc-5 > bug, which was more of a joke (because the the conditions to trigger it > were *the contrary*). No problem. It made me think a bit, but I did not waist any time. > It displays more resemblance wit

Re: macron below vs. minus sign below (was tex2lyx tests failing on master)

Guenter Milde wrote: > I committed the patches for bug #9764, so now the macron below vs. minus > sign below problem should be fixed. > http://www.lyx.org/trac/changeset/7e716a26a5e/lyxgit > > tex2lyx test pass again here. Here as well. The new errors are due to ce933b1e14f. > Please give it a

Re: [LyX/master] tcolorbox.module: uniform whitespace

Scott Kostyshak wrote: > On Mon, Oct 19, 2015 at 07:15:21AM +0200, Uwe Stöhr wrote: >> commit 8da453fd30a1df085782ae5a3772a07cea38b77b >> Author: Uwe Stöhr >> Date: Mon Oct 19 07:15:18 2015 +0200 >> >> tcolorbox.module: uniform whitespace > > Uwe can you please catch up on reading the ema

Re: Regression in lyx2lyx box alignment

Jean-Marc Lasgouttes wrote: > Le 18/10/15 17:01, Georg Baum a écrit : >> What is wrong with the new alignment handling? It is IMHO confusing and >> not needed, we have paragraph alignment. Look at the attached example: I >> set the box alignment to centered, and the paragra

Re: [patches] the last ones before 2.2

Guillaume Munch wrote: > Le 17/10/2015 21:19, Guillaume Munch a écrit : >> >> I thought about that, but I do not want to introduce a divergence in the >> behaviour of release mode compared to devel mode in a fundamental >> aspect. This can open the door to a lot of problems: unreproducibility >> o

Re: [patches] the last ones before 2.2

Guillaume Munch wrote: > The choice is simple, because just adding a new variable member to math > insets as per the attached (trivial) .diff leads to new segfaults with > math macros. The .diff must be applied to current master (before or > after my upcoming TexRow patches). Compiler is g++ 4.9.2

Re: [LyX/master] Refine lang nesting fix

Scott Kostyshak wrote: > Do you mean with the patch in this email? Or do you mean on current > master, after commit 86325e50? with the patch, as you found out. > Yes we will have to discuss this. One issue is that you need a lot of > dependencies to run all the tests. Another issue is that a cou

Re: [LyX/master] Refine lang nesting fix

Scott Kostyshak wrote: > Much better. The following tests still fail (compared to not using your > patch and reverting the commit in question, where these tests pass) > > ctest -R > "(export/doc/de/Additional_pdf4_systemF| export/doc/fr/Additional_pdf4_systemF|export/doc/he/Tutorial_pdf4_systemF|

bug 9626: new handling of "LyX" is unintuitive

Bug 9626 complains about the removed automatic translation of LyX, LaTeX etc to logos. Since this was done intentionally, we will not revert it. However, the questions whether we can do something to help people who work on our docs (these are the only ones who need the logos very often). This is

Re: macron below vs. minus sign below (was tex2lyx tests failing on master)

Guenter Milde wrote: > Unfortunately, there is also no agreement on the way out, as the proper > fix requires changing unicodesymbols, tex2lyx, and test-files (bugs in > the expected test outcome). I thought we agreed on a solution? You explained how the inconsistency in unicodesymbols needs to

Re: Regression in lyx2lyx box alignment

Richard Heck wrote: > On 10/16/2015 05:15 PM, Scott Kostyshak wrote: >> On Fri, Oct 16, 2015 at 11:04:32PM +0200, Georg Baum wrote: >> >>>> In my opinion this is a serious regression. Many users have boxes. >>> We should not release the alpha version with thi

Re: [LyX/master] Refine lang nesting fix

Jürgen Spitzmüller wrote: > Am Freitag 16 Oktober 2015, 23:50:38 schrieb Georg Baum: > >> Under the assumption that the old babel output was correct the fix is >> indeed trivial. > > I am not sure. When a babel language environment is used > (\begin{otherlanguage}.

Re: lyx.org down for me

Jean-Marc Lasgouttes wrote: > I just sent a message to netad...@stw-bonn.de Seems to have worked ;-) Georg

Re: [patches] the last ones before 2.2

Guillaume Munch wrote: > Le 16/10/2015 21:52, Georg Baum a écrit : >> Guillaume Munch wrote: >> >>> I did not realise that there were supposed to be so many InsetMaths live >>> at the same time. Although the increased memory use is quite small for >>>

Re: [LyX/master] Fix cursor movement for large logos (#9628)

Scott Kostyshak wrote: > I think this commit caused a regression in context menus. From what I > understand, the old behavior was that when there was a right-click over > an inset LyX would move the cursor just in front of the inset which is > how LyX would know which context menu to show. With th

Re: [LyX/master] Refine lang nesting fix

Scott Kostyshak wrote: > On Fri, Oct 16, 2015 at 10:55:25PM +0200, Georg Baum wrote: >> >> I looked into the changes, and I believe we can fix this easily. The two >> nesting fixs did also change the behaviour if babel is used. Was that >> intended? If yes, what w

Re: macron below vs. minus sign below (was tex2lyx tests failing on master)

Guenter Milde wrote: > On 2015-10-14, Georg Baum wrote: >> Scott Kostyshak wrote: > >>> On Tue, Oct 13, 2015 at 06:31:04PM +, Guenter Milde wrote: > >>>> Therefore, I don'tg want to waste time in trying to find out how I can >>>> subscrib

Re: Regression in lyx2lyx box alignment

Scott Kostyshak wrote: > Hi Uwe, > > I am now convinced this is a regression. If in 2.1.x you just create a > simple frameless box and then you open the file in master, the box is > now centered. I discussed the same issue with Uwe when the tex2lyx tests failed because of these changes. He conv

Re: [LyX/master] Refine lang nesting fix

Scott Kostyshak wrote: > On Fri, Jun 19, 2015 at 07:03:14PM +0200, Juergen Spitzmueller wrote: >> commit 46aed6d2b90cafed93a6ee996ec72c09a6325f92 >> Author: Juergen Spitzmueller >> Date: Fri Jun 19 19:02:35 2015 +0200 >> >> Refine lang nesting fix >> > > After this commit I believe that

Re: [patches] the last ones before 2.2

Guillaume Munch wrote: > Le 14/10/2015 21:35, Georg Baum a écrit : >> >> Please measure memory consumption. I am a bit afraid that this increases >> memory usage a lot, since math insets contain very tiny bits of >> information, and you may need _lots_ of them even for

Re: IBus compatibility

Guillaume Munch wrote: > Beware of any confusion, the deadlock bug is with qt4 and is solved in > qt5 (any version I could test). Another bug makes qt < 5.6 impractical > for (all) Linux users. So the situation is more complex than what you > wrote. Oh, sorry, then I misunderstood the situation c

Re: [patches] the last ones before 2.2

Jean-Marc Lasgouttes wrote: >> Why do you need a new member variable at all? Why can't you just use the >> memory address? This would not consume memory and still be a unique id. > > I guess that the answer is the same as for paragraph ids: they can get > copied at unexpected times. If my unders

Re: [LyX/master] Fix missing xhtml output found by cppcheck

Scott Kostyshak wrote: > Many export ctests are failing after this commit. One example is if you > open up the Additional.lyx manual and export to XHTML. I get a "LyX has > caught an exception" message. Or if you do it on the command line I get: > > $ lyx -e xhtml Additional.lyx > Error 2

Re: [patches] the last ones before 2.2

Guillaume Munch wrote: > I submit it on the list to get your agreement on several fundamental > changes which I kept, as you will see, as little intrusive as possible. Wow, these are lots of changes. I am running out of time and will only comment on some. > The sensitive changes (i.e. where I h

Re: Compiling LyX on Windows with more recent Visual Studio versions

David Hyde wrote: > I'm interested in looking into this at least a bit (may become deterred > if some dependency nightmare occurs!). I've looked at the current MSVC > dependencies that are in the archive on sourceforge. Which of these > are things that should actually be downloaded and compiled

Re: macron below vs. minus sign below (was tex2lyx tests failing on master)

Scott Kostyshak wrote: > On Tue, Oct 13, 2015 at 06:31:04PM +, Guenter Milde wrote: >> On 2015-10-12, Jean-Marc Lasgouttes wrote: >> >> > We can live with a few missing messages on lyx-cvs, as long as this >> > gets sorted out eventually. >> >> > I propose that you commit your patches yourse

Re: [LyX/master] Comply with rule-of-three

Vincent van Ravesteijn wrote: > Op 12-10-2015 om 4:17 schreef Scott Kostyshak: >> On Sun, Oct 11, 2015 at 11:20:15AM +0200, Georg Baum wrote: >>> commit cea2d71e641e6a4023128a367d1cd5a593ed1706 >>> Author: Georg Baum >>> Date: Sun Oct 11 11:16:09 2015 +0

Re: When to court Qt 5.6?

Scott Kostyshak wrote: > On Tue, Oct 13, 2015 at 09:20:49AM +0900, Cyrille Artho wrote: >> >> In that case it's a good opportunity to test Qt 5.6 with the next alpha >> release. > > Sounds good. Do note though that it would be Qt 5.6 *beta*. I still > think it makes sense to test our alpha with t

Re: IBus compatibility

Jean-Marc Lasgouttes wrote: > Le 11/10/2015 12:43, Guillaume Munch a écrit : >>> Qt 5.6.0 will probably be released before LyX 2.2.0. Therefore the most >>> simple solution would be to disable IBus if an older qt is detected (at >>> runtime) and mention in the release notes that korean users need

Re: [LyX/master] Fix cursor movement for large logos (#9628)

Guillaume Munch wrote: > Thanks. Can this be easily adapted for > ? I don't think so. Cursor movement in math is a quite separate implementation. Georg

Re: Form is function (was: Removing 2.2.0 milestone (as opposed to changing to 2.3.0))

Liviu Andronic wrote: > ALL other bugs fall into two categories: somewhat important if a devel > is interested in the bug, not important if no one will be bothered to > address it. This is why I find Guillaume's proposal unworkable, if I > understood it correctly, in the sense that: How do we defi

Re: Form is function (was: Removing 2.2.0 milestone (as opposed to changing to 2.3.0))

Liviu Andronic wrote: > While I understand when people want to remove milestones since "if no > one is working on them they're meaningless", I also agree with > Guillaume's arguments here: a milestone usually contains some > information about the bug, its intended scope and its importance. The > m

Re: IBus compatibility

Guillaume Munch wrote: > Decision has to be taken about the keyboard issues and deadlock in > under Linux with IBus. > > The issue is going to be solved by Qt5, but unfortunately due to > (related to event compression as

Re: Moving towards a 2.2 release

Scott Kostyshak wrote: > 1. Do you agree that the master branch is stable and that we should move > soon towards releasing an alpha? I saw a couple of reports of crashes > that could not be reproduced (Guillaume, I think you had one recently? > [1]), but these seem to be the normal amount to me, s

Re: Update on the patches

Guillaume Munch wrote: > Le 01/10/2015 00:43, Pavel Sanda a écrit : > >> This is interesting, I thought default tab is 8 and always >> edited our sources this way. Kind of surprising that we didn't >> conflicted yet about the visual appearance of indented blocks, >> like in void ViewSourceWidget::

Re: UTF-8 in string literals and translation strings in particular

Guillaume Munch wrote: > So, is the plan is to change char_type from wchar_t to uchar32_t in 2.3 > and use the syntax U"..." to directly define docstring literals? Do you > see any issues with this change? Then we do not need any conversion > method, we can just use docstring for all purposes when

Re: UTF-8 in string literals and translation strings in particular

Jean-Marc Lasgouttes wrote: > The problem with the patch is that it does not have a clear goal. The > discussion would have been much easier if you had splitted it in 3 from > the start: > > 1/ easy use of utf8 in docstring > 2/ allow utf8 in translattable strings > 3/ use … instead of ... in UI

Re: LyX on high resolution displays

Guillaume Munch wrote: > Hi, > > > Note that under Linux+Qt5, there's this bug: > > http://www.lyx.org/trac/ticket/9731 > > presumably fixed in Qt5.6: > > https://codereview.qt-project.org/#/c/126136/ > > 1) Is your testing environment still Linux? > 2) Does the slowness disappear if you scr

Re: LyX on high resolution displays

PhilipPirrip wrote: > Is 2.2 going to be a Qt5 app by default (or is it up to packagers)? 2.2 will support both qt4 and qt5, where qt4 support is probably most important for older linux distros. The windows and Mac binaries are likely to be compiled with qt5. Georg

Re: Compiling LyX on Windows with more recent Visual Studio versions

David Hyde wrote: > Hi there, > > > I'm interested in compiling LyX on Windows. I've read through the > INSTALL.Win32 file and was able to get LyX to compile from source using > Visual C++ Express 2010, following the instructions in that file. Great! > I'm > wondering though, is it possible (

Re: Release manager for LyX 2.2

Pavel Sanda wrote: > Hi all, > > it is very clear that we need to move forward with the release process. > > After the discussion with the former and current managers we agreed that > Scott Kostyshak has our trust for the role of release manager of 2.2. He > has good understanding of the code an

Re: LyX2.2 build fails on OS X

Jürgen Spitzmüller wrote: > Am Sonntag 20 September 2015, 18:43:33 schrieb Guillaume Munch: >> I understand that there are two separate issues: >> >> - There are errors looking like Uwe's if one uses --disable-cxx11, >> probably due to my latest patches. > > I rather have the impression that c++

Re: Bug with nested braces in mathed

Andrew Parsloe wrote: > LyX doesn't handle nested braces correctly. In a maths inset write { > {1234 } } so that the outer pair of braces contains a single argument. > Now save and close the document, then reopen it and the maths inset will > contain { 1234 } i.e. 4 tokens rather than the single a

Re: How to compile LyX in Win64?

Kornel Benko wrote: > Am Montag, 14. September 2015 um 10:17:02, schrieb Pål Næverlid Sævik > >> Salutations! >> >> I have been using LyX since writing my master's thesis. Now I've used it >> for academic papers, coursework, my phd thesis and more. A big thank you >> to the development team, the

Re: textcommands in math mode

Enrico Forestieri wrote: > I think that all is needed is the attached patch. I like it very much. I did not test it, but if the autocompletion problem does still exist after applying it, then we should implement a general mechanism to restrict autocompletion in mathed to the currently active mo

Re: Problem with InsetMathSideset::dyb

Jean-Marc Lasgouttes wrote: > Coverity points out that in the code below, des is overwritten without > being used. The same happens in dyt(). Georg, any comment? This was the first attempt of calculating descend and ascent, which I abandoned by introducing dybt(). I forgot to remove the old code

Re: Update on the patches

Guillaume Munch wrote: > * Where should I commit po files? I vaguely remember reading somewhere > that these should be against stable, do I remember correctly and in that > case is it better to commit to master at the same time? Note that you do not need to change po files if you don't want to (e

Re: macron below vs. minus sign below (was tex2lyx tests failing on master)

Guenter Milde wrote: > I propose a different approach: > > Motivation: > > Commit 268bd00 introduced an ambiguity because the "before" state had a > wrong mapping for the "MINUS BELOW". > The patch from #9764 removes the ambiguity (\b as representation of two > Unicode points). > > Both, commit

Re: Crash on Fedora 23 on copying or cutting text

Jean-Marc Lasgouttes wrote: > Le 12/09/15 13:58, Georg Baum a écrit : >> Jean-Marc Lasgouttes wrote: >> >>> I suspect a compiler bug. >> >> After further thinking about it I agree and reported it: >> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67557

Re: Crash on Fedora 23 on copying or cutting text

Jean-Marc Lasgouttes wrote: > I suspect a compiler bug. After further thinking about it I agree and reported it: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67557 >> The attached patch fixes the crash. Shall I apply it? > > Sure, it makes the code cleaner anyway. Did you try to run valgrind w

Re: Crash on Fedora 23 on copying or cutting text

Jean-Marc Lasgouttes wrote: > The line of Paragraph.cpp which causes the crash reads: > tagsToOpen.push_back(html::FontTag(html::FT_ROMAN)); > > I do not see how this could go wrong... Is it a problem to push_back a > temp object in a container? Georg, any idea? Actually it has something to do w

Re: Crash on Fedora 23 on copying or cutting text

Jean-Marc Lasgouttes wrote: > The line of Paragraph.cpp which causes the crash reads: > tagsToOpen.push_back(html::FontTag(html::FT_ROMAN)); > > I do not see how this could go wrong... Is it a problem to push_back a > temp object in a container? Georg, any idea? No, the temp object should not be

Re: macron below vs. minus sign below (was tex2lyx tests failing on master)

Guenter Milde wrote: > I see. > Interestingly, despite the "tests passed" message, git reports changed > files: > > diff --git a/src/tex2lyx/test/test-insets-basic.lyx.lyx > b/src/tex2lyx/test/test-insets-basic.lyx.lyx index 34c2ddc..3679ac5 100644 > --- a/src/tex2lyx/test/test-insets-basic.lyx.l

Re: cvs list forwarding

Guenter Milde wrote: > After all, it is the Git repo that sends the mails, not me, so there > should be a way to whitelist. I bet there is a technical solution. However, it looks like the list admin currently does not have the resources to look into that, so there are basically not many alterna

Re: macron below vs. minus sign below (was tex2lyx tests failing on master)

Guenter Milde wrote: > I added the mapping for the "macron below" after research into combining > diacritical characters in connection with the comma below fix. > >> Looking further at change 268bd00, I see that both 0x0320 and 0x0331 do >> now map to \b in lib/unicodesymbols. Which one is correc

Re: cvs list forwarding

Scott Kostyshak wrote: > On Sat, Sep 05, 2015 at 08:42:07AM +, Guenter Milde wrote: >> I hope there is a solution that works without me getting all the >> auto-generated lyx-cvs posts: To my kowledge this is not possible. You need to subscribe with your lyx.org account. > Would it be simple

Re: How do I run tex2lyx tests?

Jean-Marc Lasgouttes wrote: > Now I have done it and I know it is "make alltests". > > I feel wiser, except that the tests fail with my patch. I guess you do not talk about the failures caused by change 268bd00? Are you sure that the new output of the changed tests is wrong? In some cases a ch

Re: tex2lyx tests failing on master

Kornel Benko wrote: > Am Donnerstag, 3. September 2015 um 17:20:30, schrieb Scott Kostyshak > >> These tests are failing on master: >> >> 16:tex2lyx/roundtrip/test-insets-basic.tex >> 17:tex2lyx/cmplyx/test-insets-basic.tex >> 18:tex2lyx/roundtrip/test-insets.tex >> 19:tex2lyx/cmplyx/test-insets

Re: \input@path - two slashes, quotation marks

PhilipPirrip wrote: > I suspect the other slash was added as a bug fix for those OS's that do > not have it at the end of the path, can't see any other reason. > So I suppose this should be tested on OSX and Windows as well. It is not an OS issue. LyX has an OS abstraction layer for this kind of

Re: -std=c++11 and [PATCH] Improve the display of the source (bugs #6501,#7359)

Jean-Marc Lasgouttes wrote: > Le 27/08/2015 22:00, Georg Baum a écrit : >> We can at least turn c++11 on automatically for "non-weird" compilers >> (and I think we should do it). > > The following patch (on top of the previous one) does this. OK? Yes, this looks good. Georg

Re: [PATCH] Re: -std=c++11 and [PATCH] Improve the display of the source (bugs #6501,#7359)

Jean-Marc Lasgouttes wrote: > Le 27/08/2015 22:00, Georg Baum a écrit : >>>> One problem that we have is that the compiler has to be in c++11 mode >>>> _and_ the configure script has to be aware of it. Currently weird >>>> compilers are not handled at a

Re: -std=c++11 and [PATCH] Improve the display of the source (bugs #6501,#7359)

Guillaume Munch wrote: > More specific answers follow. > > Le 26/08/2015 13:18, Jean-Marc Lasgouttes a écrit : >> Le 24/08/2015 21:19, Georg Baum a écrit : > > Thanks. By the way, Georg, is there any plan to backport 125a2977 and > 27f067dd? IMHO we should not backpo

Re: \input@path - two slashes, quotation marks

PhilipPirrip wrote: > Why does \input@path end with two slashes, as in > /home/user/directory// IIRC this means that also sub directories are searched, but this should be documented in some TeX or LaTeX docs. > > Not sure how it all works for (La)TeX, I'm assuming this is all ha

Re: \input@path - two slashes, quotation marks

PhilipPirrip wrote: > On 08/19/2015 04:44 PM, Georg Baum wrote: >> PhilipPirrip wrote: >> >>> Why does \input@path end with two slashes, as in >>> /home/user/directory// >> >> IIRC this means that also sub directories are searched, but this should &

Re: -std=c++11 and [PATCH] Improve the display of the source (bugs #6501,#7359)

Guillaume Munch wrote: > Then, I must translate for people who do not read French. Essentially, > if the plan is to use c++11 features starting from 2.3, and 2.2 requires > c++98 compatibility, then backporting new code is going to involve > unusual efforts, or discourage using the features as lon

Re: [PATCH] minor improvements to mathed

Richard Heck wrote: > On 08/19/2015 06:35 PM, Guillaume Munch wrote: >> >> These patch are also up to date and both can be applied to stable as >> well. > > OK. Whoever applies them to master please also apply to stable. I can do that, but I could not find a license statement from Guillaume yet.

Re: \input@path - two slashes, quotation marks

PhilipPirrip wrote: > Why does \input@path end with two slashes, as in > /home/user/directory// IIRC this means that also sub directories are searched, but this should be documented in some TeX or LaTeX docs. > and why is its output > "/home/user/dir ectory/"/ > (note quotation marks, and two s

Re: [PATCH] minor improvements to mathed

Richard Heck wrote: > On 08/01/2015 06:34 AM, Guillaume Munch wrote: >> Here are again two very small patches if you agree. >> >> 1. Add \ensuremath to the list of math completions. > > This is certainly fine. > >> 2. math-mode inserts \text instead of \mbox when already in math mode. >> >> For

Re: [PATCH] \{ and \% now correctly use the selection as their argument instead of erasing it (bug #6466)

Guillaume Munch wrote: > Le 31/07/2015 23:08, Scott Kostyshak a écrit : >> On Fri, Jul 31, 2015 at 12:05 PM, Guillaume Munch wrote: >>> \{ and \% now correctly use the selection as their argument instead of >>> erasing it. Solves . Please >>> criticise. >>> >>

Re: [PATCH] \{ and \% now correctly use the selection as their argument instead of erasing it (bug #6466)

Richard Heck wrote: > On 08/03/2015 09:32 AM, Guillaume Munch wrote: >> Le 31/07/2015 17:05, Guillaume Munch a écrit : >>> \{ and \% now correctly use the selection as their argument instead of >>> erasing it. Solves . Please >>> criticise. >>> >> >> >> If ther

Re: Guillaume's pending patches

Scott Kostyshak wrote: > Guillaume has various patches for bug fixes in several places that > have been waiting around a bit. I do not know enough about the code > that the patches touch in order to review them. However, I can test > the patches and confirm that they fix the corresponding bugs. Is

Re: About the rowpainter2 branch (testers, have a look!)

Richard Heck wrote: > On 07/21/2015 09:36 AM, Scott Kostyshak wrote: >> On Tue, Jul 21, 2015 at 8:10 AM, Jean-Marc Lasgouttes >> wrote: >> >>> Basically, I'd appreciate if some people could test it so that we can >>> see what's right and what's wrong. Since leave on thursday for vacation, >>> the

Re: Windows debug messages for graphics conversion (can't find call to my .bat file)

Cris Fuhrman wrote: > Hello, > > I'm using LyX on Windows with custom PlantUML graphics files per > http://tex.stackexchange.com/a/154806/17868 -- I have this working great > on one of my PC's that runs Windows 7. > > I have a Windows 8.1 machine at the office and I'm struggling with the SVG > c

Re: Remove InsetGraphics noUnzip

Jean-Marc Lasgouttes wrote: > Le 17/07/2015 18:57, Pavel Sanda a écrit : >> Scott Kostyshak wrote: >>> On Fri, Jul 17, 2015 at 12:35 PM, Pavel Sanda wrote: Jean-Marc Lasgouttes wrote: > I think you should remove it. Are people really still using EPS files > anyway? Major fo

Re: Remove InsetGraphics noUnzip

Jean-Marc Lasgouttes wrote: > I think you should remove it. Are people really still using EPS files > anyway? I do occasionally (but these are really special cases, they are hand programmed). Fortunately after the removal of noUnzip EPS is just one of many supported formats, we do not need to c

Remove InsetGraphics noUnzip

Hi, InsetGraphics has a parameter noUnzip. If this is set, and the included image is a compressed eps, then LyX does not unzip it when producing a DVI. Instead, the LaTeX compiler gets the bounding box information, and the .eps file stays compresssed. Only when the DVi is viewed, the viewer unc

Re: Build questions for OS X

Jean-Marc Lasgouttes wrote: > On 09/07/2015 17:13, Jean-Marc Lasgouttes wrote: >> From what I understand, the problem is only with libc++ (the clang >> Standard library) and on this one setting std=c++98 does not change >> anything. I just tried that with clang 3.6 and compilation fails. >> >> We

<    2   3   4   5   6   7   8   9   10   11   >