On Tuesday, 28 August 2018 07.07.19 WEST Cor Blom wrote:
> LyX 2.3.1 builds fine on openSUSE.
>
> Maybe you are interested in warnings and errors that the buildsystem
> used by openSUSE report:
I also a couple of them from building in Fedora. :-)
> [ 1130s] RPMLINT report:
> [ 1130s] ==
On Wednesday, 29 August 2018 12.27.44 WEST Pavel Sanda wrote:
> I think it would unnecessarily break build scripts for distro maintainers
> and does not provide some new functionality, just defaults...
> Pavel
Using my (blue) hat as a distro maintainer we already use qt5 by default for
2.3.x.
Ho
On Monday, 27 August 2018 19.41.26 WEST Richard Kimberly Heck wrote:
> Are available for testing at http://ftp.lyx.org/pub/lyx/devel/lyx-2.3/.
> I suppose we should wait to prepare binaries until we have some feedback.
>
> Riki
Compiled successfully on Fedora 27 to 30 (rawhide), as well as EL7, f
While working on https://www.lyx.org/trac/ticket/11200
Riki has improved the lyx2lyx code in terms of performance.
Today I compared the time necessary to convert the big and slow lyx file, used
in the trac report, using both python 2 and python 3. The difference in this
case is a ~ 41% improvem
On Friday, 10 August 2018 16.55.38 WEST Jürgen Spitzmüller wrote:
> Try this.
>
> Jürgen
It works, thank you. :-)
--
José Abílio
On Friday, 10 August 2018 13.58.43 WEST José Abílio Matos wrote:
> latex has no problem with it.
FWIW I am aware that I am getting into weird corners. :-)
To put things into perspective I am parsing a directory with .m files (octave/
matlab) to get the documentation and to generate automatica
On Wednesday, 8 August 2018 11.38.50 WEST Jürgen Spitzmüller wrote:
> \begin{lstlistings}
> [foo]
>
> reads [foo] as content, whereas
>
> \begin{lstlistings}%
> [foo]
>
> or
>
> \begin{lstlistings}[foo,
> bar]
>
> reads [foo...] as argument.
>
> Patch attached. Please test.
>
> It's possible
Consider the following tex file:
\documentclass{scrbook}
\usepackage{listings}
\lstset{language=Octave}
\begin{document}
\begin{lstlisting}
[x,y] = nice_fun(a,b);
\end{lstlisting}
\end{document}
The problem is that when importing tex2lyx reads the [x,y] as an additional
arguments to
On Sunday, 5 August 2018 09.05.07 WEST Juergen Spitzmueller wrote:
> The lyx2lyx reversion routine has lots of room for improvement and
> attractive tasks for pythons (file timestamp, switch of localization).
> Please feel invited!
Is this invitation still worth it?
Regards, :-)
PS: I th
On Sunday, 17 June 2018 21.04.00 WEST Kornel Benko wrote:
> The settings in .lyx/math.bind are set to
> \bind "M-m ~S-H" "math-insert \widehat
> \bind "M-m h" "math-insert \hat
>
> It doesn't make difference if using 'H' or 'h'.
That is precisely what the ~S means (i.e. regardl
On Saturday, 16 June 2018 07.15.33 WEST Scott Kostyshak wrote:
> To create \hat, we have a keybinding alt+m, h. I propose the following
> bindings (patch attached):
>
> - alt + m, H -> \widehat
> - alt + m, t -> \tilde
This seems to be taken by
M-m t ? -> math-mutate
No?
I am not sure this
On Monday, 14 May 2018 18.18.58 WEST Richard Kimberly Heck wrote:
> It seems to me that, in some ways, this is tied up with different
> understandings people have of the master-child relationship, and what it
> means to view "only the child".
I had some cases where I would like to have both option
On Tuesday, 15 May 2018 11.03.01 WEST Jean-Marc Lasgouttes
wrote:
> This has been fixed by Enrico at 6253cc4c51e4e3, right?
>
> JMarc
After running again autogen.sh the problem went away. So I
suspect that the answer is yes to your question. :-)
--
José Abílio
On Saturday, 12 May 2018 09.50.56 WEST Kornel Benko
wrote:
> I seem to be unable to send mails containing a signature.
>
> Kornel
We did _not_ receive this email. ;-)
--
José Abílio
On Saturday, 12 May 2018 04.13.02 WEST Richard Kimberly Heck wrote:
> I understand that you think Windows users would be confused by a simple
> dialog asking their permission to update MikTeX. I have spoken to
> several Windows users over the last few days who think otherwise. For a
> public exampl
On Thursday, 10 May 2018 12.30.25 WEST Jean-Marc Lasgouttes
wrote:
> What is strange is that __repalcement_assert seems to be related to
> __gnu_parallel. Could this be a compiler/library bug?
>
> JMarc
Could it be that search and replace code uses another thread? That
would explain the __gnu_p
On Thursday, 10 May 2018 18.32.00 WEST Scott Kostyshak wrote:
> Should I still do the above? I'm not sure if it would still be useful
> after reading the messages that came after this.
>
> Thanks for helping debug,
>
> Scott
There is no need to.
The problem seems to be in the calling code. This
On Wednesday, 9 May 2018 14.30.49 WEST Kornel Benko wrote:
> OK, but what can be done here? Even if I define a converter
> \converter "svgz" "bmp" "convert $$i $$o" ""
> I still see the error messages.
>
> (Manually, the "convert"-command works)
>
> Kornel
Honestly the debugging
On Wednesday, 9 May 2018 12.09.18 WEST Kornel Benko wrote:
> No it was not there.
> But with the other file it is.
> I removed the last part following the first Traceback
>
> Kornel
The culprit is:
Format.cpp (507): will guess format from file extension: svgz -> svgz
graphics/Graphi
On Wednesday, 9 May 2018 12.10.35 WEST Kornel Benko
wrote:
> I too. But the versions may differ. 5.6.1-2
I use 5.10.1
--
José Abílio
On Wednesday, 9 May 2018 10.59.34 WEST Kornel Benko wrote:
> What is your setting
> Tools->Preferences->File Handling->Converters->Converter File
> Cache->Enabled?
>
> Here it is checked. Max age = 180.
>
> Kornel
BTW I am using qt5, if that matters. :-)
--
José Abílio
On Wednesday, 9 May 2018 11.08.06 WEST Kornel Benko wrote:
> I get them too, but only if the cache is not enabled.
>
> Kornel
I have the cache enabled but it seems that I am using qt to do the
conversion/drawing
and not the default converter.
In any case the problem seems to be the sam
On Wednesday, 9 May 2018 10.59.34 WEST Kornel Benko wrote:
> What is your setting
> Tools->Preferences->File Handling->Converters->Converter File
> Cache->Enabled?
>
> Here it is checked. Max age = 180.
>
> Kornel
Yes, I have it like that in all instances.
I think that this is th
On Wednesday, 9 May 2018 10.42.31 WEST Kornel Benko wrote:
> Open eu_UserGuide.lyx
> Select TOC with graphics
> Select the last image
>
> I get _plenty_ of messages.
> Apparently zillions of converts run parallel, but they are seemingly
> sequentially handled, because I don't see big processing lo
On Wednesday, 9 May 2018 09.09.06 WEST Kornel Benko wrote:
> I found how to reproduce. Emptying cache is the winner
> # rm -rf ~/.lyx2.3/cache
> # mkdir ~/.lyx2.3/cache
>
> Kornel
Even after emptying the cache I still do not see it. :-)
--
José Abílio
On Monday, 7 May 2018 16.18.08 WEST William Adams wrote:
> It's answered here --- apparently it's an in-built feature:
>
> https://stackoverflow.com/questions/32564415/how-to-convert-jupyter-ipython->
> notebooks-to-latex
> >You have to do this from the command line rather than the web interface
On Tuesday, 8 May 2018 17.50.58 WEST Scott Kostyshak wrote:
> Thanks for trying. I'm not surprised, since my two computers have very
> simliar setups so if I can reproduce on one and not on the other, this
> is probably a tricky issue.
>
> Scott
Hi Scott,
since you can reproduce this issu
On Tuesday, 8 May 2018 15.55.33 WEST Scott Kostyshak wrote:
> To try to reproduce, open the tutorial manual and search for
"Footnotes
> and Margin Notes".
>
> Scott
I tried (not hard enough, it seems :-) ) with both 2.3 and 2.4 and I was
not able to reproduce it. :-(
--
José Abílio
On Tuesday, 8 May 2018 12.48.50 WEST Kornel Benko wrote:
> Would be nice to see the arguments. Could we test first, if enough
arguments
> are provided?
>
> Kornel
Sure. :-)
The funny part is that this was not ever needed because convertDefault.py is
called by lyx, so something else is
$ ~/lyx/lyx/configure --enable-qt5
...
Configuration
Host type: x86_64-unknown-linux-gnu
Special build flags: build=development warnings assertions stdlib-debug
C++ Compiler:g++ (8)
C++ Compiler flags: -Wall -Wextra -Wfloat-conversion -fPIC -g -O
C++ C
On Tuesday, 8 May 2018 12.08.20 WEST Kornel Benko wrote:
> I got 10 messages of the form:
> Traceback (most recent call last):
> File "/usr/local/share/lyx2.3/scripts/convertDefault.py", line 73, in
> if (im or gm) and os.system(r'%s %s "%s" "%s"' % (command, opts,
> sys.argv[2], sys.argv[3] + '
Using my Fedora hat,
we got a bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1575097
In this case the user (me again :-) ) has used the search and replace.
At the end of document I got the standard dialog:
"End of file reached while searching forward.
Continue searching from the
On Thursday, 3 May 2018 00.51.04 WEST Richard Kimberly
Heck wrote:
> Added to ANNOUNCE.
>
> Riki
Thank you. :-)
--
José Abílio
On Monday, 30 April 2018 03.06.01 WEST Richard Kimberly Heck
wrote:
> José made some changes to some older routines, so that might
explain it.
>
> Riki
It is possible but unlikely. :-)
I am aware of the famous last words analogy. ;-)
--
José Abílio
On Tuesday, 24 April 2018 16.37.34 WEST Jean-Marc
Lasgouttes wrote:
> Especially since xemacs seems to be dead these days.
Nope I do not use xemacs since ~ 2001. I always use emacs
(and (g)vi(m) and kate and whatever works). :-)
--
José Abílio
On Tuesday, 24 April 2018 15.21.08 WEST Kornel Benko
wrote:
> Understood. Anyone else using emacs.bind besides me?
FWIW I use the xemacs.bind (and I have used ever since I
remember).
Do not ask me why xemacs and not emacs, I would not know
what to answer. :-)
--
José Abílio
On Thursday, 19 April 2018 03.55.27 WEST Richard Kimberly Heck wrote:
> This can easily enough be installed, but it does not seem to be
> installed by default on Fedora 27. Do we want to do something about
> that? The User Guide would not compile for me due to not having it.
>
> Riki
Regarding Fe
After looking into all the python scripts I have fixed most of the issues.
The only possible issues are files that are not in utf-8 encoding, I think that
in all those cases we are on the safe side but I could be wrong.
The patch as it is should be compatible with both python 2 and python 3, so
On Wednesday, 4 April 2018 14.28.44 WEST José Abílio Matos wrote:
> Hi,
> while trying to solve #Bug 11101 I faced the doubt
> of what is the encoding of an eps file.
>
> Is it ascii or can it use another encoding?
>
> Regards,
Replying myself: it can be another
Hi,
while trying to solve #Bug 11101 I faced the doubt
of what is the encoding of an eps file.
Is it ascii or can it use another encoding?
Regards,
--
José Abílio
On Tuesday, 3 April 2018 12.55.20 WEST Helge Hafting wrote:
> Existing documents with xfig figures cannot be opened, because LyX then
> invokes /usr/share/lyx/scripts/fig_copy.py which python3 does not
> understand. In other words, backward compatibility seems broken.
>
> On arch linux, "python" i
On Tuesday, 3 April 2018 13.28.55 WEST José Abílio Matos
wrote:
> Could you test the attached patch?
There was a typo in the last patch...
--
José Abílio
diff --git a/lib/scripts/fig_copy.py b/lib/scripts/fig_copy.py
index d5e0421668..c6235195c2 100644
--- a/lib/scripts/fig_copy.py
+++ b/
On Tuesday, 3 April 2018 12.55.20 WEST Helge Hafting wrote:
> Existing documents with xfig figures cannot be opened, because LyX then
> invokes /usr/share/lyx/scripts/fig_copy.py which python3 does not
> understand. In other words, backward compatibility seems broken.
>
> On arch linux, "python" i
On Friday, 30 March 2018 20.21.53 WEST Kornel Benko wrote:
> And we should distinguish usage of python at configure and build time, from
> the use at lyx-run-time.
>
> Kornel
That is where I respectfully disagree. :-)
What you are suggesting is equivalent to release a lyx version with th
On Friday, 30 March 2018 19.59.13 WEST Kornel Benko wrote:
> No, I think you are wrong.
> CmakeLists.txt:760
> starts with
> find_package(PythonInterp 3.3 QUIET)
> If python3 is found, it is used as ${LYX_PYTHON_EXECUTABLE} from then on.
I was referring to src/support/os.cpp function pytho
On Tuesday, 27 March 2018 10.29.31 WEST Kornel Benko wrote:
> On cmake build the default is already python3.
True but then, if I read the code correctly, lyx will pick the language called
python that only on Arch (linux) is python 3, for all other cases (in linux
and other OSs) python refers to
On Tuesday, 27 March 2018 10.45.10 WEST Jean-Marc Lasgouttes wrote:
> I am OK with that. Even Ubuntu 14.04 has python 3.4.
>
> JMarc
FWIW the reasons are the following:
* we require version 3.3 because we use the u"" prefix in several places, that
was not
supported in previous versions of pyt
On Thursday, 29 March 2018 16.29.44 WEST Richard Kimberly Heck wrote:
> There's actually quite a lot of the latter, so I might think about a
> relatively quick release of 2.3.1 even still, by which I mean something
> like mid-May.
>
> Riki
+1
2.3.x seems to be a quite stable release (famous last
On Wednesday, 28 March 2018 20.26.52 WEST racoon wrote:
> I'd like to get your take on an enhancement request for changing the
> label for footnotes from "foot x" too "fn x". I think the latter is a
> much more common abbreviation than the former.
I agree but for me fn remembers FuNction. :-)
> h
On Thursday, 29 March 2018 15.19.07 WEST Joel Kulesza wrote:
> I ask because, in my experience, inserting a comment should *never*
have an
> effect on the result of the application processing it. My thanks for the
> fix with "fragile" below, and it's true I don't need overlays in my
> application
On Wednesday, 28 March 2018 23.26.08 WEST Pavel Sanda wrote:
> Given that no catastrophic bugs were reported during past weeks isn't
> the time ripe to merge 2.3.2-staging into 2.3.x to get testing for
> this branch?
> Pavel
I agree with Pavel :-) in the sense that we could at least set some date
Hi,
I intend to apply a patch that makes python3 the default for lyx 2.4.
The core of the change is to move all calls to python to use the python3 name.
That should work everywhere.
Eventually we should even ignore python 2 and go python 3, only, for 2.4. In
the
time frame of 2.4 python
On Tuesday, 20 March 2018 02.01.57 WET Uwe Stöhr wrote:
> The fileformat and also the format of the preferences of major LyX
> versions differ. Therefore every major LyX version has its own
> preferences. You can try out to copy your preferences from LyX 2.2 but
> we cannot guarantee that they will
On Monday, 19 March 2018 08.57.24 WET Juergen Spitzmueller wrote:
> commit 1ae537c5437d0f1abbf877e40a09ad59385f621b
> Author: Juergen Spitzmueller
> Date: Mon Mar 19 09:56:53 2018 +0100
>
> Change lookup order for enchant-2 vs. enchant (prefer the former)
FWIW I tested this on 2.4 and it w
On Friday, 2 March 2018 19.14.52 WET Uwe Stöhr wrote:
> -tfp = cmdOutput(interpreter + " -tt " + '"'
> +tfp = cmdOutput('"' + interpreter + '"' + " -tt " + '"'
> + os.path.join(srcdir, 'scripts', 'TeXFiles.py') + '"')
This is mater of style, but personally I think th
On Monday, 26 February 2018 14.22.15 WET Uwe Stöhr wrote:
> - the default in CMake for LYX_USE_QT is still Qt4, it should be Qt5
Note that this is also the default with the autotools (autoconf & co). So
that is a global choice and it is not specific to cmake.
For 2.4 I think that the time has co
On Sunday, 25 February 2018 16.58.36 WET Stephan Witt wrote:
> Today I saw a warning with lyx-2.3.0 as follows:
> configure: WARNING: unrecognized options: --enable-cxx11
Hi Stephan,
isn't C++ 11 our basic requirement?
Or said the other way around there is code that does not work
On Friday, 23 February 2018 18.15.34 WET Scott Kostyshak wrote:
> To get you back, I made you waste time with thinking about my above
> proposal :)
>
> Scott
It is always a good sign when at the end of a development cycle the
release manager is smiling. ;-)
Good job.
--
José Abílio
On Friday, 23 February 2018 03.34.52 WET Joel Kulesza wrote:
> Minor wording question here and on the website: is "down" potentially
> confusing for a non-native English speaker? Would "unavailable" be more
> clear?
In the case of (European) Portuguese the equivalent of down is the word that we
On Wednesday, 21 February 2018 09.35.44 WET Jean-Marc Lasgouttes wrote:
> OK, let's a propose a few things:
> - always use a period as separator, like we do for export (be
> consistent). Or, if we think that the period was a bad idea, use
> something else (minus or underscore) consistently.
That I
On Tuesday, 20 February 2018 10.43.17 WET José Abílio Matos wrote:
> Something like what follows attached?
>
> I have tested it with several cases and it works.
Id this patch is deemed appropriate there is still one small issue.
should it be as it is:
A) document.lyx -> document-l
On Monday, 19 February 2018 11.42.57 WET Jean-Marc Lasgouttes wrote:
> Le 17/02/2018 à 14:02, José Abílio Matos a écrit :
> > How about the following patch?
>
> What happens if the format is not from a released version? In this case,
> we would like to keep the old naming IMO.
On Monday, 19 February 2018 15.40.42 WET Jürgen Spitzmüller wrote:
> xcellent. Here is my analysis.
>
> Since this is a very old document, it has "\layout Standard" in insets.
> Now as of format 315 (for LyX 1.6), we switched to "\begin_layout
> PlainLayout" and shortly afterwards "\begin_layout P
On Monday, 19 February 2018 11.42.57 WET Jean-Marc Lasgouttes wrote:
> Le 17/02/2018 à 14:02, José Abílio Matos a écrit :
> > How about the following patch?
>
> What happens if the format is not from a released version? In this case,
> we would like to keep the old naming IMO.
On Saturday, 17 February 2018 15.27.48 WET Scott Kostyshak wrote:
> On Sat, Feb 17, 2018 at 01:53:55PM +0000, José Abílio Matos wrote:
> > What are the cases where a bigger warning is expected?
>
> I don't have anything specific in mind. There are seven instances of
> "
On Thursday, 1 February 2018 19.09.47 WET Scott Kostyshak wrote:
> Thanks to Jean-Pierre's hawk eyes, we found a potential issue in
> configure.py [1]. I did not see this because I don't manually check the
> configure log (although this would be a good thing to do from time to
> time).
>
> I'm won
On Wednesday, 31 January 2018 15.53.41 WET Jean-Marc Lasgouttes wrote:
> Le 31/01/2018 à 16:29, José Abílio Matos a écrit :
> > My idea, in the last message, was for lyx2lyx to add the -lyxXX suffix
> > to the file name by default when called with the --backup optio
On Saturday, 10 February 2018 18.51.44 WET Scott Kostyshak wrote:
> What is your feeling on how stable our 2.3.x branch currently is? I have
> the feeling that it is quite stable and that we should now make plans
> for the next step in the release process. I propose to make the final
> 2.3.0 releas
On Wednesday, 31 January 2018 21.43.11 WET Jean-Marc
Lasgouttes wrote:
> PS: and José will answer that he agrees 1000% and
intended to do that
> for the start %-]
Nah... last time I used gogol, now I will use gogolplex
(10^(10^100)) and my share of smiles is over for the day. :-)
--
José Abíli
On Wednesday, 31 January 2018 11.16.26 WET Jean-Marc Lasgouttes wrote:
> Yes, it is nice to have a --backup option, but if lyx itself can avoid
> to figure out the suffix from the cryptic lyxformat value, it is even
> better.
FWIW I agree with you. :-)
My idea, in the last message, was for lyx2lyx
On Wednesday, 31 January 2018 10.35.08 WET Jean-Marc Lasgouttes wrote:
> Le 31/01/2018 à 11:11, José Abílio Matos a écrit :
> > I am suggesting that
> >
> > format 508 -> .22.lyx
> >
> > format 509 -> .23.lyx
>
> What is the current situation? Is i
On Wednesday, 31 January 2018 09.48.50 WET Jean-Marc Lasgouttes wrote:
> It would be nice if we were able to translate lyxformat values that
> correspond to stable release to a nicer name. For example, -22x.lyx~
> instead of -lyxformat-508.lyx~, or even .22.lyx~, a bit like what export
> as 2.2.x d
On Tuesday, 30 January 2018 15.41.28 WET Jean-Marc
Lasgouttes wrote:
> You mean _custom_ file dialogs, right?
>
> JMarc
Sure. My mistake. :-)
--
José Abílio
On Tuesday, 30 January 2018 14.53.45 WET Pavel Sanda wrote:
> I use them sometimes, but can't say whether it's because of real usage or
> devel activities... P
Me too. :-)
I think that the question regarding the usefulness of the those dialogs could
get a
better feedback on the users list. If n
On Thursday, 18 January 2018 06.00.41 WET Joel Kulesza wrote:
> b.
> I will use such Notebooks more and more in the future, and it would be
> extremely useful if I could import then in an easy way into LyX.
>
>
> Here I've used the pdfpages package to include PDFs from Jupyter (or other
> tools)
On Wednesday, 3 January 2018 13.02.18 WET Pavel Sanda wrote:
> Speaking of Portuguese, could you check whether the current translations for
> "List of Listings"
> "Nomenclature[[output]]
> "see equation[[nomencl]]"
> "page[[nomencl]]"
>
> is correct in lib/layouttranslations?
> Pavel
It is. :-)
On Wednesday, 3 January 2018 12.04.42 WET Jürgen Spitzmüller wrote:
> You mean it should display green (in the given example)?
>
> Jürgen
Yes, or else, to be coherent, "no color" should mean invisible. :-)
I understand that the color property is dealt in the WYSIWYM such that the mean
part. And
On Tuesday, 2 January 2018 17.28.49 WET Jürgen Spitzmüller wrote:
>
> http://www.lyx.org/trac/ticket/5870
>
> Fix attached.
>
> Jürgen
Thank you Jürgen,
that solves the immediate (and most important) problem, the latex
export. :-)
There is another minor problem that is the visual feed
Hi,
in the last couple of months I had been busy working with beamer. A
co-worker had
a problem with the "Example Block" in beamer. The easiest recipe to replicate
is:
1) In a beamer document select the "Example Block". Write some text and then
select some
text and change its color to
On Saturday, 30 December 2017 10.40.19 WET Jürgen Spitzmüller wrote:
> Right. I am talking about the layout format here, though.
>
> Jürgen
Oops. :-)
You are right.
IIRC we have been a little bit more permissive in this case. :-)
Happy new year. :-)
--
José Abílio
On Saturday, 30 December 2017 10.14.53 WET Jürgen Spitzmüller wrote:
> Note, further, that this entails a layout format change. I am not sure
> what our current policy is wrt introducing this within a stable series.
> If we don't do that, no for 2.3.0 would mean no for 2.3.x.
>
> Jürgen
The invar
On Sunday, 24 December 2017 02.50.07 WET Scott Kostyshak wrote:
> I changed <> to <> at b798347, otherwise I get a
> "SyntaxError: invalid syntax" from Python.
>
> Can someone please confirm that's the correct fix? (I am not experienced
> in Python).
>
> Scott
Your change is only half correct. :
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
> #
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 (
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
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
On Wednesday, 24 May 2017 03.51.55 WEST Scott Kostyshak wrote:
> Any objection from anyone else?
>
> Scott
Honestly the use of the plus sign as a special character seems unnatural to
me. :-)
My suggestion would be to pass an option that specify just that, say -d. The
advantage of this approach
On Saturday, 13 May 2017 19.39.55 WEST Uwe Stöhr wrote:
> commit 0dd3311dd42996f9aede7d8c58b27937ebb48b54
> Author: Uwe Stöhr
> Date: Sat May 13 20:39:45 2017 +0200
>
> rename buffer parameter math_number_before to math_numbering_side
>
> this is a fileformat change
>
> also try
On Monday, 15 May 2017 12.50.06 WEST Guillaume MM wrote:
> It looks like this warning shows up every time.
Yes. And it is clearly out of place. The function in question is supposed to
work on the header, and all the calls are like that (I have some reservations
regarding the last part but they a
On Saturday, 13 May 2017 09.23.44 WEST Scott Kostyshak wrote:
> José, thanks for remembering about this issue. The script still does not
> work for me.
>
> $ python --version
> Python 2.7.12
>
> Scott
The command line parser was missing the argv argument (minus the program
name). I test
On Saturday, 13 May 2017 10.50.10 WEST Stephan Witt wrote:
> Yes, I put in in. (And you luckily hit a Friday to place your smiley )
That has never stopped me before. :-D
My daughter and son follow the same footsteps, some of the other parents said
that never saw them not smiling in the morning.
On Friday, 12 May 2017 18.16.28 WEST Kornel Benko wrote:
> Have you tried math-preview with standard output format PDF(lualatex)?
> I know, this has nothing to do with python2 vs. python3, but since you are
> looking into the relevant files, it may interest you.
>
> Kornel
I tried and I h
With the several patches committed this week I am able to open all the
documents in the LyX's documentation with no crash in the lyxpreview scripts
when running python 3.
I suspect that there could be other places needing to be fixed but for now it
is working.
Regards,
--
José Abílio
On Monday, 24 April 2017 06.46.21 WEST Scott Kostyshak wrote:
> I use
>
> development/tools/updatelayouts.py
>
> to easily update the format of our layout files. The script no longer
> works for me. I wonder if the script needs to be updated after 77511ea1
> (I think the call to layout2layout i
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 :
> > I will look into this problem if we have a bug report for it and a simple
> > example file.
>
> http://www.lyx.org/trac/ticket/10660
>
> Jürgen
>
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: in
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? lead
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 I h
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 prefs2prefs
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
301 - 400 of 499 matches
Mail list logo
