Re: One official build system?

On Friday, June 3, 2016 1:16:04 AM WEST Scott Kostyshak wrote: > From what I understand, most developers on Linux use autotools. I can't > tell if this is because that is what most developers have experience > with or if it is because autotools has other advantages. > > Scott In my case I use

Re: Tarballs for LyX 2.2.0 are on FTP

On Friday, June 3, 2016 2:02:15 PM WEST Jean-Marc Lasgouttes wrote: > I prefer the fixed schedule. We never know exactly when starting a > release cycle what features will happen or not. But we can enforce when > the release will happen. +1 -- José Abílio

Re: [LyX/master] Make lyx2lyx infrastructure python3 ready

On Sunday, June 12, 2016 9:24:44 PM WEST Georg Baum wrote: > commit 166420d02ccb073dc32ab5cd0bc466de54aa36bb > Author: Georg Baum > Date: Sun Jun 12 21:21:15 2016 +0200 > > Make lyx2lyx infrastructure python3 ready > > The LyX class works now with python 3. Certain file

Re: lyx and dark color schemes

On Tuesday, June 14, 2016 9:21:38 PM WEST Guillaume Munch wrote: > latexhighlighter.diff Could this go to lyx-2.2 as well. I have the same problem with the font colours but not the panel icons. Regards, -- José Abílio

Re: Tarballs for LyX 2.2.0 are on FTP

On Wednesday, May 25, 2016 7:11:14 PM WEST Jürgen Spitzmüller wrote: > Congratulations. And thanks for the excellent management job, Scott. > > Jürgen I agree. :-) Well done. -- José Abílio

Re: Handling of \SpecialChar

On Wednesday, May 25, 2016 1:39:56 PM WEST Scott Kostyshak wrote: > I'm still curious someone has thoughts on the above idea. The main > question I have is do we usually know when we are not producing > equivalent documents (and thus it is easy to issue a warning)? I assumed > so but I don't have

Re: Layout Changes Inside CharStyles?

On Tuesday, June 21, 2016 4:07:25 PM WEST Helge Hafting wrote: > Why do we generally not want to change paragraph style just because some > char style is in effect? The purpose of the char styles is to be used for inline elements, that is elements that are placed inside a paragraph. Currently

Re: [LyX/master] Style.

On Friday, June 24, 2016 10:02:30 PM WEST Richard Heck wrote: > commit 92fae708aebf8d2f3bc393b29c54a4cebeafe730 > Author: Richard Heck > Date: Fri Jun 24 15:03:59 2016 -0400 > > Style. > --- > lib/lyx2lyx/LyX.py |2 +- > 1 files changed, 1 insertions(+), 1 deletions(-)

Re: [LyX/master] Document new inverted branch insets in User Guide. Also add note to RELEASE_NOTES.

On Tuesday, July 12, 2016 10:57:05 AM WEST Richard Heck wrote: > There was some discussion of this last cycle, too, and I think everyone > generally thinks it is a good idea. Exactly how to do it is less clear. > I had thought about having, for each format change, test files that > could be used

Re: [LyX/master] Document new inverted branch insets in User Guide. Also add note to RELEASE_NOTES.

On Tuesday, July 12, 2016 6:20:38 AM WEST Richard Heck wrote: > commit e57889ff2f38ed8e804a7e3c7e62114e31bf7715 > Author: Richard Heck > Date: Tue Jul 12 00:20:27 2016 -0400 > > Document new inverted branch insets in User Guide. Also add note to > RELEASE_NOTES. Since

Re: [LyX/master] We do not need to enter the format numbers for 2.3 at this time. The code just below fills thiss automatically.

On Tuesday, July 12, 2016 4:49:21 AM WEST Richard Heck wrote: > commit ed87044d91e39daf2c079ba4582603add299d667 > Author: Richard Heck > Date: Mon Jul 11 22:48:04 2016 -0400 > > We do not need to enter the format numbers for 2.3 at this time. > The code just below fills

Re: [patch] Specify the target format for local layout conversion

On Sunday, July 24, 2016 1:18:32 AM WEST Guillaume Munch wrote: > Dear list > > > Here are two patches that I would like to include in master. > > * The first one adds a flag [-t FORMAT] to lib/scripts/layout2layout.py > to specify a target format for conversion. I took some code from > lyx2lyx

Re: [LyX/2.2.x] Fix bug #10273

On Monday, August 1, 2016 1:25:56 PM WEST Jean-Marc Lasgouttes wrote: > What is this -V1.4 for clyx and friends? > > Jmarc > > Le 1 août 2016 12:09:07 GMT+02:00, "José Matos " a écrit : > >+\converter lyxclyx "python -tt $$s/lyx2lyx/lyx2lyx -V > >1.4 -o $$o -c

Re: Exporting compressed files

On Friday, July 8, 2016 2:10:07 PM WEST Richard Heck wrote: > Good, and thanks for fixing this. > > rh Thank you. :-) The change is in for 2.2.2 together with a change status and the bug close. Regards, -- José Abílio

Re: [LyX/master] Include all [scr]article styles in beamer article layouts.

On Thursday, August 4, 2016 11:44:37 AM WEST Juergen Spitzmueller wrote: > commit 90f6eb01a4ac09d56591e0ed8a342ad6f6163796 > Author: Juergen Spitzmueller > Date: Thu Aug 4 11:42:06 2016 +0200 > > Include all [scr]article styles in beamer article layouts. > > File format

Re: Should the author of a file format change update the file format of docs in master?

On Thursday, August 11, 2016 3:33:10 PM WEST Scott Kostyshak wrote: > Good idea. I think it makes sense and does get rid of the problem. > Please feel free to update Development.lyx with these instructions. Or > if you want me to, I will do it eventually. > > Scott Please do. I will be busy for

Re: Should the author of a file format change update the file format of docs in master?

On Sunday, August 7, 2016 8:00:53 PM WEST Scott Kostyshak wrote: > I wrote that after what I recall being a discussion in a sub-thread. I > wonder now if I should have made a separate discussion on the list, so > I'm doing that now. Do others agree with the above paragraph? I have not > actually

Re: [LyX/master] implement lyx2lyx roundtrip for \use_microtype

Hi, I have been looking into making lyx2lyx more robust and better integrated with lyx. I have identified some issues in the code that I intend to fix later. On Friday, June 17, 2016 9:12:20 PM WEST Georg Baum wrote: > commit ff93b83953ea3276f9be8a4243a7e6f603f3fe38 > Author:

Re: Exporting compressed files

On Saturday, May 28, 2016 3:00:09 PM WEST Andrew Parsloe wrote: > I inadvertently tried exporting a compressed 2.2 file to 2.1.4. It was > not recognised by 2.1.4. When I try exporting an empty 2.2 compressed > file, it too isn't recognized by 2.1.4, so clearly this is not an > allowed mode of

Re: Exporting compressed files

On Tuesday, July 5, 2016 10:36:51 PM WEST Andrew Parsloe wrote: > The problem is just with compressed files. Uncompressed they export > fine, and can be read in 2.1.5. With the compressed file when I try to > open it in 2.1.5 I get the message: ".21.lyx is not a > readable LyX document."

Re: Exporting compressed files

On Thursday, July 7, 2016 4:05:15 PM WEST Richard Heck wrote: > Patch seems reasonable to me. > > Please commit to 2.2.x after 2.2.1 is released. > > Richard Thank you Richard. :-) Commited to master and I will do the same to 2.2.x after 2.2.1 is out. Regards, -- José Abílio

Re: Exporting compressed files

On Thursday, July 7, 2016 10:09:44 AM WEST Andrew Parsloe wrote: > > Yes, changing > to -o results in an exported compressed file that 2.1.5 > can read. Thanks for the help. > > Andrew Thank you Andrew. I still blame windows for this but in any case to use the option -o is the right thing to

Re: toolbars Lock menu

On Saturday, July 9, 2016 2:42:11 PM WEST racoon wrote: > By the way, since I have never worked on a project like LyX, if anyone > has tips on how to work effectively, I am pleased to know. I guess using > git is one. The first step is to read: http://www.lyx.org/Development where there are

Re: Weird KDE Bug in LyX

On Friday, July 1, 2016 9:51:08 AM WEST Richard Heck wrote: > Add > > [Development] > AutoCheckAccelerators=false > CopyWidgetText=false > > to $HOME/.config/kdeglobals > > Richard Thank you Richard, when that happens it can be really annoying. Trying to change a paragraph layout with Alt+P

Re: Exporting compressed files

On Wednesday, July 6, 2016 10:31:45 AM WEST Andrew Parsloe wrote: > LyX 2.1.5 has no trouble saving and reading its own compressed files. That is good, I was being thoroughly in order to not to discart any possibility. > If I save a compressed file in 2.2.0, LyX 2.1.5 can read it. If I export

Re: middle-click to open child documents?

On Friday, August 5, 2016 10:56:31 PM WEST Scott Kostyshak wrote: > Dear LyX devs, > > The following behavior is shared by Firefox and Chromium: > > ctrl+left-click opens a tab but does not switch to it > middle-click is the same as ctrl+left click > shift+middle-click opens the tab and switches

Re: C++ "good practices" regarding constifying a function parameter?

On Saturday, August 6, 2016 4:17:01 PM WEST Abdelrazak Younes wrote: > Exactly! > > Cheers, > Abdel. Can I use a 4K screen as the standard? ;-) FWIW I agree with the rational of having short/not too long functions, I am just saying that half a screen is an ambiguous measure. :-) -- José

tex2lyx fails with \subfloat without optional arguments

Hi, recently I had a colleague that asked to convert some tex document to lyx because it was failing for him. After some work, involving bissections :-) , I dound out that the culprit was a subfloat. Basically a call like \subfloat{somegraphics} fails to produce a legal lyx

Re: epub output in version 2.2?

On Saturday, July 23, 2016 6:30:45 PM WEST Guenter Milde wrote: > On 2016-07-09, Richard Heck wrote: > > On 07/09/2016 07:36 AM, Guillaume Munch wrote: > >> Le 07/07/2016 19:25, Steve Litt a écrit : > >>> If they just made LyX into valid and well formed XML, creating our > >>> own converter, with

Re: ancient history, v 0.10.7 beta

On Thursday, June 30, 2016 10:51:09 AM WEST Jean-Marc Lasgouttes wrote: > We have a lot of these old thing on our ftp actually: > http://www.lyx.org/misc/archaeology/lyx-time.html > > This web page is not up to date, unfortunately... I did that initally and then Angus has improved it a lot but

Re: Weird KDE Bug in LyX

On Thursday, June 30, 2016 4:26:40 PM WEST Richard Heck wrote: > For anyone running LyX 2.2.0 under KDE (or using a KDE-based window > manager, or anything of that sort): > > There is an annoying new feature, KDE's "accelerator manager", that > automatically adds shortcuts. This causes conflicts

Re: Why does LyX not accept empty list items?

On Monday, July 4, 2016 12:45:05 PM WEST racoon wrote: > In LyX one has to enter and ERT with {} or a note or so in order to keep > the item. This seems cumbersome. And it is needed in order to, for > example, start an "indented environment" directly after the first, e.g. > to get No need to

Re: Regular expression search

On Tuesday, September 27, 2016 1:12:49 PM WET Kornel Benko wrote: > What are the differences between gcc5.3, 6.1 and 4.8? > gcc4.8 Compiler does not support std_regex, flag = "--std=c++11" > gcc5.3 Compiler supports std_regex, flag = "--std=c++14" > gcc6.1 Compiler supports std_regex, flag =

Re: middle-click to open child documents?

On Friday, August 19, 2016 11:06:15 PM WEST Scott Kostyshak wrote: > I see, but José seems against it. So it would be nice to see what others > think. > > Scott FWIW, in case it was not clear, I have/had a minor/minimal objection. :-) -- José Abílio

Re: master/child assertion

On Saturday, September 3, 2016 10:50:49 AM WEST Scott Kostyshak wrote: > > Can anyone else reproduce? > > Scott Using 2.2.1 in Fedora I get lassert.cpp (51): ASSERTION d->clone_list_->empty() VIOLATED IN Buffer.cpp:505 ( 1) lyx: lyx(+0x7c50eb) [0x55ebc487c0eb] ( 2) lyx: lyx(+0x197894)

Re: tex2lyx fails with \subfloat without optional arguments

On Monday, August 29, 2016 3:00:53 PM WEST Jean-Marc Lasgouttes wrote: > Le 06/08/2016 à 16:31, José Abílio Matos a écrit : > > Basically a call like > > > > \subfloat{somegraphics} > > > > fails to produce a legal lyx file. LyX complains that it gets a c

Re: [PATCH] A fix for the zombie -lyxformat- files invasion ?

On Friday, September 9, 2016 10:45:44 AM WEST Jean-Marc Lasgouttes wrote: > Hello, > > Here is a trivial idea to limit the proliferation of > myfile-lyxformat-322.lyx files that are more annoying than helpful to > many people (or helpful in a Clippy sense). Can we at least use .lyx~ as >

Re: fix math toolbars

On Friday, September 9, 2016 10:45:08 AM WEST Enrico Forestieri wrote: > Sorry, I didn't even read your logorrheic answer. I think this a > strategy for exhausting the opponent. This type of arguments does not help and is detrimental in the long term for the community. It is OK to disagree and

Re: tex2lyx fails with \subfloat without optional arguments

On Tuesday, September 13, 2016 10:19:09 PM WEST Scott Kostyshak wrote: > Do we have a ticket for this issue so it doesn't get forgotten? Now we do. :-) http://www.lyx.org/trac/ticket/10385 Thank you for reminder. :-) > Scott -- José Abílio

Re: lyx2lyx problem converting math

On Wednesday, September 28, 2016 11:11:39 AM WET Kornel Benko wrote: > Using math in lyx2.3 as e.g. > \begin_inset Formula $\vec{{\underline{{v$. > Exported to 2.2.x we get > \begin_inset Formula $\vec{{\underline{}{v}}}$ > > Kornel Hi Kornel, I am again at the

Re: lyx2lyx problem converting math

On Saturday, November 5, 2016 11:08:37 AM WET Kornel Benko wrote: > I already forgot about this. But retesting now, it seems the problem is > gone. Instead now we have a BIG problem displaying previewed math. > 1.) The previewed expression is too small compared to used font size. > 2.) The

Re: mathmacros/testcases_speed.lyx: Handling unknown body token

On Wednesday, November 30, 2016 10:44:21 AM WET Kornel Benko wrote: > I was/am reluctant. Preferring correction of lyx2lyx. > But since the expert is Günter, maybe I am wrong. > > Kornel I agree with Kornel. The patch should be quite easy, since as far as I understand the purpose is to

Re: [LyX features/biblatex2] Fix isDefaultBiblio() test

On Saturday, December 31, 2016 4:01:31 PM WET Juergen Spitzmueller wrote: > + vector::const_iterator it = default_biblios_.begin(); > + vector::const_iterator end = default_biblios_.end(); > + for (; it != end; ++it) { > + string const s = *it; > + if

Support for python 2 and 3 in lyx2lyx for 2.3

First the good news: after Georg's work we are almost there (99.999%). :-) And now the fine details. I have fixed #9006 that results in lyx2lyx working with python 3 for systems where the system default encoding is not UTF-8. Using the 0.12.0 User Guide as the starting point the only

Re: LyX master still not ready for Python 3

On Wednesday, 29 March 2017 23.09.23 WEST Uwe Stöhr wrote: > And indeed by using i n line 208 > > os.write(fd, b'\relax') > instead of > os.write(fd, r'\relax') > > I get with > inpname = shortPath(str(tmpfname)).replace('\\', '/') > no error. But then it will of course fail with Python 2. > >

Re: Support for python 2 and 3 in lyx2lyx for 2.3

On Wednesday, 29 March 2017 15.25.12 WEST Kornel Benko wrote: > > > There is one task remaining. Creation of lyxrc.defaults uses string > > > 'python' as executable even if lyx is configured for use with python3. > > > I agree that this could change. Actually here I meant to say not just that it

Re: LyX master still not ready for Python 3

On Wednesday, 29 March 2017 01.12.06 WEST Uwe Stöhr wrote: > As requested by José, I installed Python 3.6.1 and tested today's master > with it. As result LyX cannot be started because the reconfiguration fails: > > 02:05:53.187: Checking whether TeX allows spaces in file names... yes >

Re: Support for python 2 and 3 in lyx2lyx for 2.3

On Wednesday, 29 March 2017 13.19.23 WEST Kornel Benko wrote: > So, should we make python3 be the default for lyx2.3? We want it to work as well as it works python 2. If it is the default or not I have no strong opinion. > There is one task remaining. Creation of lyxrc.defaults uses string

Re: Support for python 2 and 3 in lyx2lyx for 2.3

On Tuesday, 28 March 2017 15.07.17 WEST Jean-Marc Lasgouttes wrote: > It looks like something that can be handled by a bisect, either a real > one or a hand-made one where a dichotomy is done on the intermediate > commits. Nah... I prefer to follow Ken Thompson's advice: "When in doubt, use brute

Re: Support for python 2 and 3 in lyx2lyx for 2.3

On Tuesday, 28 March 2017 23.57.39 WEST José Abílio Matos wrote: > FWIW the culprit seems to be normalize_font_whitespace in lyx_1_5.py, that > is used for formats 259 and 274. I found the reason. In that function the is a variable called changes that is a dictionary. We access to th

Re: LyX master still not ready for Python 3

On Wednesday, 29 March 2017 18.24.26 WEST Enrico Forestieri wrote: > On Wed, Mar 29, 2017 at 02:41:23PM +0100, José Abílio Matos wrote: > > OK, I committed a change that should fix this problem. > > I hope so ;) When dealing with windows I always hope, after all hope is

Re: Support for python 2 and 3 in lyx2lyx for 2.3

On Wednesday, 29 March 2017 12.14.29 WEST Kornel Benko wrote: > Export tests to previous lyx-versions using python3 are failing. It should be working now. Using iteritems() returns an iterator while items() returns a list in python 2. For python 3 items() returns and iterator and iteritems()

Re: LyX master still not ready for Python 3

On Wednesday, 29 March 2017 01.12.06 WEST Uwe Stöhr wrote: > As requested by José, I installed Python 3.6.1 and tested today's master > with it. As result LyX cannot be started because the reconfiguration fails: > > 02:05:53.187: Checking whether TeX allows spaces in file names... yes >

Re: Is this a valid .lyx file (created by 2.0.8.1)?

On Wednesday, 15 March 2017 19.06.07 WET Scott Kostyshak wrote: > Attached is a minimal example from here: > > http://tex.stackexchange.com/questions/358326/my-font-shows-up-in-the-font-l > ist-but-the-document-wont-compile > > It was created with 2.0.8.1. > > When I open it in 2.1.0 or 2.2.x I

Re: [LyX/master] Fix output of en- and em-dashes with TeX fonts

On Sunday, 19 March 2017 19.58.08 WET Enrico Forestieri wrote: > commit 72a488d7e6b56432263c80dd92cd6acc565e03a7 > Author: Enrico Forestieri > Date: Sun Mar 19 20:50:34 2017 +0100 > > Fix output of en- and em-dashes with TeX fonts > > This commit fixes the regression

Re: [LyX/master] Fix output of en- and em-dashes with TeX fonts

On Tuesday, 21 March 2017 09.26.39 WET Jürgen Spitzmüller wrote: > > I am not sure I understand. The default setting of \dynamic_quotes is > "false", which is equal to the case when the param is missing. > > Jürgen That was the subject of my rambling on Sunday and something that I have been

Re: LyX 2.2 cannot read a document from LyX 2.1?

On Tuesday, 7 March 2017 12.39.19 WET Enrico Forestieri wrote: > > Is this a valid process that we should support? > > Given that lyx2lyx processes text files, taking into account that they > may have a BOM is safer. OK. So I will try to solve this problem. > > If so the following patch fixes

Re: [LyX/master] Fix output of en- and em-dashes with TeX fonts

On Monday, 20 March 2017 10.52.26 WET Enrico Forestieri wrote: > > For this changes I would expect for \use_dash_ligatures to be referred in > > the FORMATS since this is a new header that does not exists before. > > I think you mean development/FORMAT. I will add the reference. Note that > also

Re: [LyX/master] Fix output of en- and em-dashes with TeX fonts

On Monday, 20 March 2017 13.28.36 WET Enrico Forestieri wrote: > I think that info was already in document.start You are right and initially I started to search for it but for some reason got sidetracked. I intend to commit a change to remove document.start and to change all references to

Re: [patch] Re: LyX master still not ready for Python 3

On Sunday, 2 April 2017 13.40.05 WEST Uwe Stöhr wrote: > - the file was opened without the correct encoding. Since nothing was > give, utf8 was used. That failed because on Windows it is in cp1252. In > my patch I use io.open which works with Python 2.6 and 2.7. I think we > don't need to support

Re: [patch] Re: LyX master still not ready for Python 3

On Tuesday, 4 April 2017 21.43.58 WEST Uwe Stöhr wrote: > Hi José, > > many thanks for having a look. > > Why CMake 2.6? That was released 9 years (sic!) ago. Using it is a > potential security issue. i am wondering if people still use this. > > In my opinion we should rely on CMake 2.8,

Re: LyX docs: cleaning up math options

On Tuesday, 11 April 2017 16.11.06 WEST Jean-Pierre Chrétien wrote: > I still get errors with Literate, knitr, listerrors, noweb2lyx, sweave, > DocBook and Rjournal. Not that DocBook is not related with latex. So you can remove it from your list of failures. :-) -- José Abílio

Re: prefs2prefs.py not compatible with python3 [PATCH]

On Saturday, 1 April 2017 06.16.55 WEST Scott Kostyshak wrote: > José, any thoughts? The changes are reasonable and in line with what has been done in other places. So if it works for both python 2 and 3 it should go in. :-) -- José Abílio

Re: Remove "Bummer" in "Save failed! Bummer. Document is lost."

On Saturday, 1 April 2017 05.39.45 WEST Scott Kostyshak wrote: > Regarding the message > > "Save failed! Bummer. Document is lost." > > the word "Bummer" to me means "eh, too bad" (imagine someone saying this > with a nonchalant voice). I don't think it is a professional choice of > words when

Re: [LyX/master] support to indent formulas

On Wednesday, 12 April 2017 00.16.01 WEST Uwe Stöhr wrote: > Well, this is a matter of taste. For me math is everything, inline and > formulas. Since the indentation is only something for formulas I chose > "formula". Personally, I find LyX's term "displayed equations" > meaningless. What is

Re: [LyX/master] Add support to cross out characters

On Tuesday, 11 April 2017 09.04.59 WEST Jean-Marc Lasgouttes wrote: > I do not see any reason to keep == true in C++ either. > > JMarc I agree that the " == true" is a non-idiomatic expression both for c++ and for python. PS: I am aware that the literal is True in python but the idea is

Re: Python error

On Wednesday, 12 April 2017 15.42.42 WEST Enrico Forestieri wrote: > On Wed, Apr 12, 2017 at 03:36:10PM +0200, Jürgen Spitzmüller wrote: > > I understand that there is no perfect method. However, if we can catch > > a significant set of cases without too much effort, we should probably > > do

Re: Python error

On Wednesday, 12 April 2017 16.49.54 WEST Enrico Forestieri wrote: > And how would you perform regex matches when dealing with bytes-like > objects in python3? Don't you get a TypeError? http://stackoverflow.com/questions/5618988/regular-expression-parsing-a-binary-file tldr; defining the regex

Re: [patch] Re: LyX master still not ready for Python 3

On Wednesday, 5 April 2017 21.08.09 WEST Enrico Forestieri wrote: > Most probably you have some non-ascii characters in a \DeclareLaTeXClass > line in some of your layout files. Now those files are explicitly read as > utf-8 encoded. If this is so, the attached patch should help. It should be

Re: [patch] Re: LyX master still not ready for Python 3

On Wednesday, 5 April 2017 09.38.24 WEST Kornel Benko wrote: > ATM cmake(lyx) checks for python >= 2.7. I stand corrected then. :-) Thank you Kornel. -- José Abílio

Re: [patch] Re: LyX master still not ready for Python 3

On Wednesday, 5 April 2017 21.48.21 WEST Uwe Stöhr wrote: > El 05.04.2017 a las 22:08, Enrico Forestieri escribió: > > Most probably you have some non-ascii characters in a \DeclareLaTeXClass > > line in some of your layout files. Now those files are explicitly read as > > utf-8 encoded. If this

Re: [LyX/master] Add support to cross out characters

On Thursday, 6 April 2017 02.56.51 WEST Scott Kostyshak wrote: > I see it's used in other places in lyx2lyx (grep for '== True'), so > perhaps this is convention in Python? Nope. The convention is the former: if changed: ... -- José Abílio

Re: Tentative schedule for 2.3.0 release

On Monday, 10 April 2017 08.46.45 WEST Jean-Marc Lasgouttes wrote: > It was proably discussed last time, but I do not remember: what is the > rationale for having an alpha before feature freeze? Shouldn't it be the > opposite? I think that this is the usual procedure. Take Fedora as an example,

Re: Tentative schedule for 2.3.0 release

On Monday, 10 April 2017 10.58.51 WEST Jean-Marc Lasgouttes wrote: > No, because doing everything by opposition to others is like doing doing > it like them: it is following their whim :-) > Seriously, I am not sure about the alpha release. It is serious work, > and I am not sure what we will

Re: [patch] Re: LyX master still not ready for Python 3

On Monday, 10 April 2017 11.02.21 WEST Jean-Marc Lasgouttes wrote: > As I wrote, it fixes my problem. Do you want me to apply it, or are > there reasons to hold it? > > JMarc Since this fixes a bug I think that it should be committed. For the final version I intend to uniform all the changes

Re: How far is 2.3.0?

On Monday, 10 April 2017 08.50.32 WEST Jean-Marc Lasgouttes wrote: > Version numbers are just version numbers, I do not think that they make > as much of a difference than getting versions out fast. In the case of > firefox and gcc, the important part of the new release scheme was speed. > The

Re: Python error

On Wednesday, 12 April 2017 19.25.29 WEST Enrico Forestieri wrote: > Maybe I beat him Yes, you did. :-) > Please, try the attached. It works for me with both python 2 and 3. I like this code more than the previous since the previous section that was windows specific could fail if we had a

Re: Python error

On Wednesday, 12 April 2017 19.40.32 WEST Enrico Forestieri wrote: > I have some difficulty understanding how backslashes are treated > in bytes-like objects, though. Do you have an examples? I am not aware of any differences regarding backslashes in strings or bytes. -- José Abílio

Re: Python error

On Thursday, 13 April 2017 10.46.18 WEST Enrico Forestieri wrote: > The rule I infer from the above is that in b'' objects the backslash > is not special unless followed by another backslash, in which case > is quotes the backslash. This seems nonsense to me. FWIW a couple of weeks ago I was

Re: Python error

On Thursday, 13 April 2017 15.52.57 WEST Enrico Forestieri wrote: > Thanks for the pointer. I also see there: > > Changed in version 3.6: Unrecognized escape sequences produce a > DeprecationWarning. In some future version of Python they will > be a SyntaxError. > > which is what I

Re: [LyX/master] buffer-export without argument exports the default format

On Friday, 10 March 2017 07.31.43 WET Scott Kostyshak wrote: > agree that * is an established wildcard, but doesn't it mean "all" or > "everything"? For example, inset-forall uses '*' for "all insets". > Wouldn't the analogy here be for it to mean "all formats", which is not > what we want? I

Re: How far is 2.3.0?

On Friday, 24 February 2017 17.45.28 WET Jean-Marc Lasgouttes wrote: > Hi there, > > A good subject before the week-end: what do we need to do before > declaring feature freeze for 2.3? Personally I have finished a cycle or > breaking/fixing the math editor and would like to refrain from doing

Re: How far is 2.3.0?

On Saturday, 11 March 2017 20.48.02 WET Richard Heck wrote: > And I'll second that. You did an excellent job last time, which is why > we all want you to do it again. +1 -- José Abílio

Re: How far is 2.3.0?

On Wednesday, 8 March 2017 00.17.33 WET Scott Kostyshak wrote: > Makes sense. I guess in the end this is the decision of the branch > maintainer. > > Scott Agreed. :-) -- José Abílio

Re: How far is 2.3.0?

On Wednesday, 8 March 2017 01.33.03 WET Pavel Sanda wrote: > My take on this is that release manager responsibility is to set and publish > deadlines and push people who are responsible for their area of expertise > to fix or stabilize that in reasonable time. So it's more of understanding > whom

Re: LyX 2.2 cannot read a document from LyX 2.1?

On Monday, 6 March 2017 12.35.47 WET Kornel Benko wrote: > Am Montag, 6. März 2017 um 13:13:58, schrieb Matěj Cepl > > > Yes, this is not a minimal example, but I am hesitant to touch this > > document from LyX 2.1 so that I wouldn’t accidentally fixed it. When > > trying to open

Re: LyX 2.2 cannot read a document from LyX 2.1?

On Monday, 6 March 2017 22.27.25 WET Enrico Forestieri wrote: > The problem is that the file starts with a U+FEFF BOM mark, and most > probably lyx2lyx doesn't expect to deal with BOM marks. Actually, the > conversion succeeds, but the BOM mark is left in place (it now appears > on the second

Re: How far is 2.3.0?

On Tuesday, 7 March 2017 00.06.24 WET Scott Kostyshak wrote: [...] Thank you Scott for all distilling your experience as release manager, as this is important to improve the development process. :-) I will left the other issues that you have raised for others. > In case someone is craving

Fwd: Installation issues, log file available?

We got this on the users mailing list: -- Forwarded Message -- Subject: Installation issues, log file available? Date: Saturday, 8 April 2017, 12.33.15 WEST From: Ward Romp To: lyx-us...@lists.lyx.org Dear all, I try to install LyX on windows 7 on top of

Re: Do we need AM_PYTHON_CHECK_VERSION ?

On Monday, 24 April 2017 17.00.05 WEST Jean-Marc Lasgouttes wrote: > Hi there, > > We have this in lyxinclude.m4. Do we still need it? I cannot find a > trace of this code in configure. > > JMarc > > # AM_PYTHON_CHECK_VERSION(PROG, VERSION, [ACTION-IF-TRUE], > [ACTION-IF-FALSE]) > # >

Re: ext_copy.py

On Saturday, 1 July 2017 04.54.15 WEST Scott Kostyshak wrote: > Pinging José. > > Scott I am sorry for the huge latency time but I have been busy with exams & Co. That period is now over. Is it OK then to apply the patch? Regards, -- José Abílio

Re: ext_copy.py

On Monday, 7 August 2017 02.52.12 WEST Scott Kostyshak wrote: > On Tue, Jul 04, 2017 at 06:03:22PM -0400, Scott Kostyshak wrote: > > On Tue, Jul 04, 2017 at 11:33:02AM +0100, José Abílio Matos wrote: > > > On Saturday, 1 July 2017 04.54.15 WEST Scott Kostyshak wrote: &g

Re: ext_copy.py

On Thursday, 25 May 2017 01.31.05 WEST Andrew Parsloe wrote: > (Deep breath.) I think ext_copy.py is only half of a pair of scripts. > The other half is a "dummy exporter", something like > > ## dummy_export.py > ## a minimal script used to 'export' the > ## current document and excite the LyX >

Re: ext_copy.py

On Tuesday, 4 July 2017 23.03.22 WEST Scott Kostyshak wrote: > No problem at all. I hope you don't mind my nagging emails (if you do, > please say so). Not only I do not mind them but I appreciate them. :-) I apologize for taking so long, after reading ~1100 pages (tikz manual) and ~550 pages

Re: Migration of preferences

On Thursday, 11 May 2017 14.26.37 WEST Jürgen Spitzmüller wrote: > 2017-05-11 12:51 GMT+02:00 José Abílio Matos <jama...@lyx.org>: > > I will look into this problem if we have a bug report for it and a simple > > example file. > > http://www.lyx.org/tr

Re: [LyX/master] make python string compliant with python 2 and 3

On Thursday, 11 May 2017 15.06.42 WEST Jean-Marc Lasgouttes wrote: > I still get: > > File > "/home/local/lasgoutt/lyx/master/lib/scripts/lyxpreview2bitmap.py", line 166 > def_re = > re.compile(rb"(newcommandx|globallongdef)([a-zA-Z]+)") > > ^ > SyntaxError:

Re: Fwd: 2.3.0alpha1-1

On Tuesday, 9 May 2017 12.20.13 WEST Scott Kostyshak wrote: > On Tue, May 09, 2017 at 10:10:12AM +0100, José Abílio Matos wrote: > > In order to test the python3 support I created the fedora packages that > > force the usage of python 3. > > Attached follows the patch that

Re: Migration of preferences

On Tuesday, 9 May 2017 12.08.31 WEST Jürgen Spitzmüller wrote: > We (José and Enrico) fixed a similar problem with encodings in layouts in > lyx2lyx, so I suppose prefs2prefs can be fixed as well. > > Jürgen I agree with your point of view. :-) OTOH the difference between lyx2lyx and

Re: 2.3.0alpha1-1

On Tuesday, 9 May 2017 17.33.24 WEST Richard Heck wrote: > It feels (and it just is a feeling) as if there's some kind of conflict > that happens when we call > the system python. Maybe because of something in the path? Could that > lead python itself to > look for packages in the wrong place?

Re: [LyX/master] python3: fix the preview framework to work with both python 2 and 3

On Tuesday, 9 May 2017 16.06.54 WEST Jean-Marc Lasgouttes wrote: > I just got the following. Is it related? Yes. I committed the obvious fix. Thank you. :-) -- José Abílio

  1   2   3   4   5   >