On Wednesday, January 13, 2021 8:27:28 PM WET Pavel Sanda wrote:
> The question really is why it should be wrong to give new major version
> +0.1.
>
> Anyway, I do not see that this subthread is moving in a constructive
> direction, so it's perhaps best to agree that we disagree
I agree, I tried
On Wednesday, January 13, 2021 2:37:54 PM WET Pavel Sanda wrote:
> Fortunately I do not have to rely only on my memory
>
> Wiki: Sat Nov 15 18:59:02 2008 : LyX 2_0: Wiki pages creation
> SVN:Sun Dec 7 18:09:18 2008 : [Cvslog] r27798 Makefile.am: PSpell and
> ISpell was removed for LyX 2.0
On Wednesday, January 13, 2021 9:48:58 AM WET Jean-Marc Lasgouttes wrote:
> I do not really like this. I find it very useful to add weird character
> in a version string to indicate that the version is not a regular one.
>
> JMarc
This is what I call the "Paris Syndrome", a mild form of the
On Wednesday, January 13, 2021 11:51:53 AM WET Pavel Sanda wrote:
> I hope my memory serves me well, but the major reason we did not go the
> predictable route of 1.6, 1.7, 1.8, 1.9, 2.0, 2.1 etc was your own push for
> 2.0 at the Berlin meeting. I can even remember at which corner of the room
>
On Wednesday, January 13, 2021 2:37:54 PM WET Pavel Sanda wrote:
> I guess that's the point where we break. I agree that moving from 2 to 3
> signals major change. At the same time once some project moves to double
> digits versions my experience is that I am no more keeping track which
> version
On Monday, January 4, 2021 2:02:30 PM WET Jean-Marc Lasgouttes wrote:
> Strangely enough, the test is present. Assuming your configure script is
> updated, could you send the output of
>g++ -dumpversion
> and
>g++ -dumpfullversion
> ?
>
> JMarc
[root@centos7 ~]# g++ -dumpversion
4.8.5
On Sunday, January 3, 2021 7:19:11 PM WET Jean-Marc Lasgouttes wrote:
> > Remove elipses after 'Open'
>
> Why is that?
>
> JMarc
I agree with Jean-Marc.
Open always launches a pop up and so it always has ellipses in every program I
tried. :-)
--
José Abílio--
lyx-devel mailing list
On Monday, January 4, 2021 2:02:30 PM WET Jean-Marc Lasgouttes wrote:
>
> Strangely enough, the test is present. Assuming your configure script is
> updated,
I will answer this in two parts. :-)
I would assume that the configure script is updated as I am compiling from the
tar balls created by
On Monday, January 4, 2021 5:02:24 PM WET Jean-Marc Lasgouttes wrote:
> It should be fixed now at 69eb262721b445, a wildcard was missing.
>
> Please test when you have the occasion.
>
> JMarc
Actually I went the other way, I brought the big brother to the fight. :-)
I am now using gcc9 to
On Monday, January 11, 2021 10:58:48 PM WET Joel Kulesza wrote:
> Regarding semantic versioning: I feel like LyX already (arguably) uses that.
> The argument I imagine: it's not clear what prompted moving from version
> 1->2,
What is the rationale of the number change?
I have been bugging the
Hi,
we have met virtually on Monday, 2021-01-11.
A short summary of the major points discussed can be found here:
https://wiki.lyx.org/Devel/Meeting2021-01-11
For those who were not able to attend feel free to ask question if the summary
is too terse.
Personally I think that the meeting
On Friday, December 11, 2020 8:14:59 PM WET Richard Kimberly Heck wrote:
> I'm not really competent, either. But if there were going to be
> problems, I think we would see them fairly quickly. Maybe it would be a
> good time, after this were committed, to do another alpha-ish release.
>
> Riki
On Monday, February 1, 2021 2:42:43 AM WET Thibaut Cuvelier wrote:
> More generally, what about the other patches? Are formatting changes
> considered risky? What about Joel's suggestions?
My issue is not about the formatting changes, I can live with them even if in
some cases I think that it is
On Sunday, January 31, 2021 12:12:41 PM WET Enrico Forestieri wrote:
> Does the attached patch work for you?
Yes. Without the patch "make check" fails, with the patch it works.
Thank you. :-)
--
José Abílio--
lyx-devel mailing list
lyx-devel@lists.lyx.org
On Friday, January 29, 2021 3:51:12 AM WET Thibaut Cuvelier wrote:
> Dear list,
>
> While working on the ePub output, I ran through many Python scripts. I
> corrected a few bgs and a lot of formatting, plus one feature (find Java in
> the Windows registry in configure.py), here are the patches.
On Friday, January 29, 2021 5:05:19 AM WET Richard Kimberly Heck wrote:
> José, can you look at these please?
>
> Riki
I think that Thibaut wants to impose black[1] on us. :-D
Most of the changes are cosmetic, e.g. one import per line, or to use the same
indentation for documentation.
The
On Friday, January 29, 2021 11:48:40 AM WET Kornel Benko wrote:
> Right, the last one should be escaped.
> Given the line
> # \DeclareLaTeXClass[revtex,revtex.sty]{REVTeX (Obsolete Version)}
> and the original regex
>
>
On Sunday, January 31, 2021 6:56:31 AM WET Liviu Andronic wrote:
> Any idea what's wrong? I'm not sure if maybe there are some new
> dependencies for 2.4 I should take into account or if maybe a specific
> compiler flag is needed.
>
>
> Thank you,
> Liviu
I am looking into it.
Note that I am
On Sunday, January 31, 2021 6:56:31 AM WET Liviu Andronic wrote:
> I've tried building Alpha 1 on Bionic but compilation ends up with this
> error:
>
> g++ -fPIC -O2 -std=c++17 -std=c++17 -g -O2
> -fdebug-prefix-map=/<>=. -fstack-protector-strong
> -Wformat -Werror=format-security -Wl,-z,defs
On Sunday, January 31, 2021 10:04:13 AM WET José Abílio Matos wrote:
> So the summary is that the compile only fails on the "make check" stage. The
> package built fine.
After this clue I searched on the logs of all architectures and the error is
also present there.
Comp
On Monday, May 24, 2021 8:18:31 PM WEST Richard Kimberly Heck wrote:
> Hi, all,
>
> I have put tarballs for beta 1 here:
>
> https://drive.google.com/drive/folders/1Zl_20mzi9ndDDQdzeFyvR07O4lLDtcW3?usp
> =sharing
>
> I need to get my IP updated with our FTP people before I can upload
> again to
On Thursday, June 3, 2021 12:58:23 AM WEST Scott Kostyshak wrote:
> commit 8c5b58a3f83457913579423cc313698a3559a7b4
> Author: Scott Kostyshak
> Date: Wed Jun 2 20:03:48 2021 -0400
>
> Noweb.lyx: fix a few mistakes from old lyx2lyx
>
> In fb034884 I made some manual changes to
On Wednesday, February 10, 2021 12:48:17 PM WET Thibaut Cuvelier wrote:
> @José : reconfiguring LyX does not solve the problem. It really looks like
> it cannot find Python.
We did not change the python detection code since alpha-1... :-(
--
José Abílio
--
lyx-devel mailing list
On Tuesday, February 9, 2021 10:09:27 AM WET Andrew Parsloe wrote:
> I've attached the output from the messages pane (with All debug messages
> set) resulting from when I click on the new document icon. (If this is
> not sufficient, then Yes, I can run LyX from the command line. What
> arguments
On Friday, February 5, 2021 10:24:23 PM WET Richard Kimberly Heck wrote:
> Hi, all,
>
> I've put tarballs for Alpha 2, built from f4003593, here:
>
> http://ftp.lyx.org/ftp/pub/lyx/devel/lyx-2.4/
>
> This includes the latest epub export stuff.
>
> Please prepare such binaries as it makes sense
On Thursday, February 11, 2021 4:02:19 PM WET Yu Jin wrote:
> Will be pointless imo, it's not the script's fault that python is not found.
> The fault is to be searched in the part of code which adds the prefix path
> to the environment, which part would that be? After all when installing,
> the
On Thursday, April 1, 2021 7:56:16 PM WEST Pavel Sanda wrote:
> When we disable multithreading, the crashes are gone.
> The downside is that comparison can not be canceled while running.
>
> Attached the final patch. If no objections are raised I'll commit.
>
> Pavel
Please do, this is one area
On Friday, March 12, 2021 3:03:03 PM WET José Abílio Matos wrote:
> On Friday, March 12, 2021 1:55:22 PM WET Jürgen Spitzmüller wrote:
> > Can you tell me what Qt theme this is?
> >
> > Jürgen
>
> Breeze Dark
BTW this how it looks like after increasing or decreasing
On Friday, March 12, 2021 3:31:45 PM WET Jürgen Spitzmüller wrote:
> Thanks. Fixed.
>
> Jürgen
Thank you after the patch the problem is gone. :-)
--
José Abílio
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
On Friday, March 12, 2021 1:55:22 PM WET Jürgen Spitzmüller wrote:
> Can you tell me what Qt theme this is?
>
> Jürgen
Breeze Dark
--
José Abílio
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
On Monday, March 15, 2021 2:39:47 PM WET Pavel Sanda wrote:
> I had the same thought, this issue happens for me regularly.
>
> Pavel
It happens to me as well. :-)
--
José Abílio
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
I am not sure if this is already reported.
When LyX launches the zoom factor "100%" is not seen initially as it can be
seen in the attached figure.
After changing it and having it redrawn every looks normal and crispy. :-)
So the issue is on start. After interacting with it the percentage
On Friday, March 12, 2021 11:24:55 AM WET José Abílio Matos wrote:
> So the issue is on start. After interacting with it the percentage shows as
> it should.
In this context interacting means changing the zoom factor, that is "zoom in"
and then "zoom out", after that
On Wednesday, February 17, 2021 11:34:23 AM WET Pavel Sanda wrote:
> Hi,
>
> when pref conversion routines fail you are greeted on terminal with
>
> LyXRC.cpp (260): Conversion failed for /home/lyx/.lyx/preferences
> Warning: Could not read configuration file
>
On Saturday, March 6, 2021 5:52:53 PM WET Jean-Marc Lasgouttes wrote:
> Don't tempt me. Or a flutter frontend?
>
> JMarc
I suggest instead a probably less known toolkit: xforms. It is a small code
base but the mailing list is still active, the last messages are from last
December. :-D
--
On Monday, February 15, 2021 3:25:45 PM WET Scott Kostyshak wrote:
> +1
>
> Thanks for taking a look, José.
>
> Scott
OK. I have lots of issues on hand but at least this is funny. :-)
One option would be to use some kind of string formatting. Actually since
curly braces are usually not used
On Monday, February 22, 2021 10:13:33 AM WET Pavel Sanda wrote:
> Anyone around with 2.70 installed to check whether the reported issues
> affect us? (Not a big deal, no sane distribution will deliver 2.70 with
> those issues as a default).
>
> Pavel
Just as you said. In Fedora we will jump from
On Tuesday, April 13, 2021 5:17:24 PM WEST Scott Kostyshak wrote:
> I get the following terminal messages followed by a SIGSEGV when opening and
> viewing MergedManuals.lyx in the GUI:
>
> QSocketNotifier: Invalid socket 16 and type 'Read', disabling...
>
> Does anyone else see this on master?
On Friday, February 12, 2021 3:01:19 PM WET Thibaut Cuvelier wrote:
> Actually, it looks like \e is a GCC-only extension that is not
> well-understood by MSVC. The attached patch solves the problem for me by
> replacing \e by another nonprintable character.
You are right \e is a gcc extension:
On Friday, February 12, 2021 3:01:19 PM WET Thibaut Cuvelier wrote:
> Actually, it looks like \e is a GCC-only extension that is not
> well-understood by MSVC. The attached patch solves the problem for me by
> replacing \e by another nonprintable character.
@Enrico what do you think about this
On Sunday, February 14, 2021 7:45:37 PM WET Richard Kimberly Heck wrote:
> With the Windows problem fixed, we need another alpha. So it's here:
>
> http://ftp.lyx.org/ftp/pub/lyx/devel/lyx-2.4/
>
> Please prepare binaries.
I have built packages for EPEL 7 and 8 and for Fedora 32-34 and rawhide
On Sunday, February 14, 2021 6:33:03 PM WET Jean-Marc Lasgouttes wrote:
> Am I right that it
> is the same to write:
> BufferView const * bv_ {};
> BufferView const * bv_ = {};
> BufferView const * bv_ = {nullptr};
> BufferView const * bv_ = nullptr;
>
> Why do we need to have all these
On Monday, February 15, 2021 4:27:40 AM WET Richard Kimberly Heck wrote:
> We have a Python detection routine, find_python_binary(), so it could be
> modified to check for those commands explicitly. I'm reluctant to touch
> that code myself though.
The detection code in LyX is working correctly,
On Thursday, February 11, 2021 7:53:36 PM WET Thibaut Cuvelier wrote:
> I would guess it is os::find_python_binary. But it has not been touched in a
> long time.
>
> It's highly likely that it does. On Windows, the first thing this function
> checks is `py -3`, but I haven't seen any py binary in
On Sunday, 11 July 2021 17.11.28 WEST Pavel Sanda wrote:
> Hi,
>
> this is what I see after make install:
>
> DeprecationWarning: the imp module is deprecated in favour of importlib;
> see the module's documentation for alternative uses
>
> Perhaps some pythonst should check...
>
> Pavel
>
>
On Monday, 18 October 2021 12.29.49 WEST Jean-Pierre Chrétien wrote:
> Le 18/10/2021 à 13:22, Jean-Pierre Chrétien a écrit :
> > Dear developers
> >
> > I get this :
> >
> > $ sudo make install-strip >>make.log
> > -c:2: DeprecationWarning: the imp module is deprecated in favour of
> >
On Sunday, 19 December 2021 17.15.19 WET Jürgen Spitzmüller wrote:
> The first thing to check, since this is a 2.3.x file, is how much time
> is taken by lyx2lyx.
If this proves to be a problem we can speed lyx2lyx code (using profiling to
identify the bottlenecks).
--
José Abílio--
On Saturday, 25 December 2021 18.32.21 WET Scott Kostyshak wrote:
> On Sun, Oct 31, 2021 at 12:58:19PM -0400, Scott Kostyshak wrote:
Hi Scott,
I find you choice of dates very convenient. :-)
https://journeys.dartmouth.edu/folklorearchive/2016/11/12/halloween-and-christmas/
“Why do programmers
On Tuesday, 28 December 2021 12.33.57 WET Stephan Witt wrote:
> The LyX tasks here are IMO:
> 1. Assure the detected python3 is used consequently. This is not the case
> ATM.
> 2. Document the meaning of the prompts the LyX user is seeing on
> Monterey.
> 3. Provide a working python3 or give
Hi all,
while searching in order to solve the python issues, I searched for all the
occurrences of "$$o" in src/
$ grep -r '$$o' src/*
The only case where I was surprised were the case of frontends GuiPrefs.cpp:
$ grep '$$o' src/frontends/qt/GuiPrefs.cpp
dviCB->addItem("xdvi
On Sunday, 2 January 2022 21.36.22 WET Richard Kimberly Heck wrote:
> On 1/2/22 16:15, Pavel Sanda wrote:
> > On Mon, Dec 27, 2021 at 11:29:08AM -0500, Richard Kimberly Heck wrote:
> >> Where do people think things are now?
> >
> > If Jose is close to finish ${python} patch it would be good to
On Wednesday, 29 December 2021 14.52.29 WET Pavel Sanda wrote:
> Jose,
>
> are the proposed changes sensible?
> I remember there were flowing similar patches to python codebase before.
The changes are reasonable for python 3.
I am not so sure about python 2 (because we support it) although it
On Sunday, 2 January 2022 23.52.37 WET José Abílio Matos wrote:
> Another option would be instead of doing this in LyXRC.cpp to do it in
> Converter.cpp and Mover.cpp where supposedly the commands are used. Then we
> could expose this to users.
This is the counterpart to the previ
On Monday, 3 January 2022 14.55.53 WET Pavel Sanda wrote:
> If I get that right the part of the "..." -> b"..." should be committed to
> 2.4?
>
> Pavel
Good point. Yes, it should (I thought that it already was) specially in order
to be consistent with all the other code that already does that.
On Tuesday, 4 January 2022 08.53.46 WET Enrico Forestieri wrote:
> I disagree. It should return the first usable version found first in
> PATH. The user has to be in control of what version has to be run, not
> the software.
I understand what you say, and I agree, but that is precisely what we
On Tuesday, 4 January 2022 10.56.51 WET Kornel Benko wrote:
> There is one:
> File 'preferences' is not updated, so I had to manually change occurrences
> of 'python', 'python3' and 'python -tt' to '$${python}'.
>
> The changed lines in preferences here:
> $ egrep python preferences
>
>
On Tuesday, 28 December 2021 13.07.19 WET José Abílio Matos wrote:
> Does any one knows why we are injecting these calls manually there?
Actually the title is wrong we are adding viewers and not converters, but the
same question applies since they are already present in configure...
--
J
On Monday, 3 January 2022 16.02.51 WET Pavel Sanda wrote:
> On Mon, Jan 03, 2022 at 03:16:47PM +0000, José Abílio Matos wrote:
> > If you want I can take care of that, in 2.4, and see if there are cases
> > where the conversion is missing.
>
> Please do, I suffer from oph
On Sunday, 2 January 2022 21.36.22 WET Richard Kimberly Heck wrote:
> OK, let me cc José on that.
>
> Riki
I have a patch that it is mostly complete but I have one doubt.
In src/support/ForkedCalls.cpp there is a comment that says:
// Make sure that a V2 python is run, if available
Does anyone
On Wednesday, 29 December 2021 10.38.38 WET Stephan Witt wrote:
> In any case we should ensure the detected usable python is used
> consequently.
>
> Stephan
This should be done now.
All the heuristics regarding Python detection is now placed in src/support/
os.cpp. In particular we can try use
On Monday, 3 January 2022 18.32.14 WET José Abílio Matos wrote:
> In any case I found other cases where the code is wrong (like the BOM
> removal that does not work) and that it does not give an error although it
> is wrong.
For future reference this is an issue that happens
On Monday, 3 January 2022 22.40.05 WET Enrico Forestieri wrote:
> If i remember correctly, if the command starts with "python -tt" then we
> could be sure it was a command defined by us and we replaced that with
> os::python(). The last was for sure invoking a Python 2, while the bare
> python
On Friday, 31 December 2021 13.03.57 WET Stephan Witt wrote:
> I’m curious how difficult it would be to ignore python2 and present a
> message box for users to tell them how to get a python3 interpreter.
>
> BR, Stephan
For now we always search for Python 3 before Python 2. We know what is the
On Tuesday, 4 January 2022 07.16.52 WET Stephan Witt wrote:
> Interestingly on my system the python3 is detected only if I install the
> Python package from python.org. The python3 in /usr/bin is not tried?
> Sorry, I didn’t read the code yet.
It should according to the code in support/os.cpp.
On Monday, 8 November 2021 20.57.37 WET Pavel Sanda wrote:
> This is actually not correct way how to solve this under bullseye.
> "python" is gone for good and scripts should use either python2
> or python3 binary.
> If you insist on using "python" you should install specific package (IIRC
>
On Monday, 25 October 2021 17.14.36 WEST Scott Kostyshak wrote:
> Update layouts (run layout2layout.py)
>
> There is nothing in the diff besides the format number changing from
> 93 to 95. From what I understand, this is as expected since 93 -> 94
> and 94 -> 95 just add new
On Monday, 25 October 2021 18.48.18 WEST José Abílio Matos wrote:
> FWIW maybe it could help if this was part of the standard process of layout
> format updates.
>
> If problems occur that is the reason why we have git for.
>
> Not only that but the person that commits the
On Sunday, 5 December 2021 17.43.30 WET Richard Kimberly Heck wrote:
> > 3. LyX's configure should not assume 'python' command exists.
> > (https://www.mail-archive.com/search?l=mid=20210215004347.vha7nygqpd6g5h
> > 5q%40tallinn)
> I've asked Pavel to create a wiki to-do list. Or you can do it.
On Thursday, 15 July 2021 16.37.19 WEST Scott Kostyshak wrote:
> Bump. I know most people are lacking time, and I also have not been giving
> feedback on others' patches (sorry, racoon!). But I prefer not to push this
> change without at least a few more opinions. That said, I'm happy to wait
>
On Sunday, 13 February 2022 03.30.57 WET Enrico Forestieri wrote:
> commit 777ccce5617aea9b15f27902b9133146eff4e87b
> Author: Enrico Forestieri
> Date: Sun Feb 13 04:57:27 2022 +0100
>
> Fix bug #12466
>
> Amend 109ea2be by reintroducing the command prefix that was
> inadvertently
On Friday, 11 February 2022 13.04.06 WET Jean-Marc Lasgouttes wrote:
> Dear Jürgen,
>
> I had a quick look and it looks good. Of course, only time will tell of
> the approach was good enough
>
> JMarc
Just like Jean-Marc I agree that this seems to fit the declared purpose.
In particular it
On Monday, 7 March 2022 12.57.59 WET Scott Kostyshak wrote:
> Let's just leave things as is for now. Perhaps it would make sense for
> me to eventually start a separate Beamer example file so that we can
> keep the introduction simple.
>
> Scott
That "smells" (I am thinking about cinnamon, do
On Tuesday, 8 March 2022 01.53.10 WET Scott Kostyshak wrote:
> Thanks, Joel! I've been complaining several years that we should switch,
> but I don't do anything about it :). And I still have no plans to
> volunteer.
>
> Scott
There are several examples of transitions like that:
On Tuesday, 8 March 2022 18.21.25 WET Scott Kostyshak wrote:
> Has anyone tried Mold when linking LyX? I've been curious about it for a
> while. I just checked Ubuntu 22.04 daily and it has it packaged, which
> makes it more interesting to try when I find the time.
>
> Some references if curious:
On Wednesday, 23 March 2022 20.12.23 WET Thibaut Cuvelier wrote:
> XHTML 1 dates back from 2001... LyX generates XHTML 5, but the doctype is
kept
> from XHTML 1 for compatibility issues (some browsers completely change their
> behaviour based on the doctype). The issue has been discussed on the
On Thursday, 27 January 2022 13.04.12 WET José Abílio Matos wrote:
> Hi,
>
> we are at the time of year again. :-)
>
>
> The gcc project will release version 12 and in Fedora we are rebuilding all
> packages with it.
The changes were minimal and already referred here.
I
On Monday, 3 January 2022 19.30.58 WET José Matos wrote:
> commit 940d3ceeb9e6d8ce216afedf18c898ec075cc27d
> Author: José Matos
> Date: Mon Jan 3 19:59:42 2022 +
>
> Make layout2layout compatible with Python 2 and 3
> ---
> lib/scripts/layout2layout.py | 14 +++---
> 1
On Thursday, 27 January 2022 13.09.09 WET Scott Kostyshak wrote:
> Except for that issue does it build with -Werror ?
>
> Scott
For completeness sake, since this was answered before, it follows here an
example of the output that you can expect when building lyx with gcc-12. In
this case I am
On Wednesday, 2 February 2022 21.45.40 WET Pavel Sanda wrote:
> Jose, could I ask for pythonic help?
> We would need a routine in configure.py which check whether to remove eps->png
> conversion in case IM bans those conversions. That could be done this way by
> checking return status of the
On Thursday, 27 January 2022 15.44.56 WET José Abílio Matos wrote:
> The previous patch was all that it was required to compile lyx-2.4 with
> gcc-12. :-)
But then it does not run:
$ src/lyx
src/lyx: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.30' not found (required
by s
On Thursday, 27 January 2022 15.48.33 WET Kornel Benko wrote:
> This one may be needed for 2.4.0 version of lyxfind.cpp too.
You are right but for some reason I got away without this fix, only the
cstring of the other thread. (BTW I am puzzled) The reason could be some
change in the code
Hi,
we are at the time of year again. :-)
The gcc project will release version 12 and in Fedora we are rebuilding all
packages with it.
There is a failure to build 2.3.x (e.g. on x86-54):
https://kojipkgs.fedoraproject.org//work/tasks/4412/81984412/build.log
73 | class MatchString :
On Sunday, 2 January 2022 21.19.14 WET Pavel Sanda wrote:
> Most likely my doing.
> These are just suggestions in drop-down menu you can use or edit in
> your settings. I do not see much merit in moving it to configure
> (they are not automagically used).
>
> Pavel
That makes sense. Thank you.
On Tuesday, 1 February 2022 14.33.49 WET Jean-Marc Lasgouttes wrote:
> Note that shift-tab for depth does not always have a local scope either,
> since it may change the depth of nested sub elements.
Yes, I know and it was a sloppy language. :-)
A better expression would be a waterfall model and
On Tuesday, 1 February 2022 10.23.41 WET Jean-Marc Lasgouttes wrote:
> Hello,
>
> I am looking for feedback about
> https://www.lyx.org/trac/ticket/12417
>
> Basically, now Tab and the depth icons invoke outline in/out when on a
> sectioning layout.
>
> Do you find that this is confusing? The
On Wednesday, 9 February 2022 01.06.17 WET Thibaut Cuvelier wrote:
> Dear list,
>
> A friend of mine noticed that LyX 2.3 has problems displaying the attached
> EPS file. All other EPS images can be previewed within LyX without any
> problem.
> All EPS files are displayed correctly in the PDF
On Wednesday, 9 February 2022 13.17.29 WET Daniel wrote:
> eps is a vector image, png is a bitmap. so, this might not be a
> desirable solution depending on what is to be achieved.
A small nitpick, eps allows vector images but it does not require it.
It is perfectly possible to have an eps that
On Thursday, 27 January 2022 13.52.56 WET Jean-Marc Lasgouttes wrote:
> José, what can you tell me about these messages?
> annobin: Timeout.cpp: Warning: -D_GLIBCXX_ASSERTIONS not defined
>
> We use _GLIBCXX_DEBUG currently. Should we switch to
> _GLIBCXX_ASSERTIONS? I have not found the gcc docs
On Thursday, 27 January 2022 13.52.56 WET Jean-Marc Lasgouttes wrote:
> This one is a warning, but you cut part of it out.
For complete sake the complete diagnose (warnings and errors) is here:
make[4]: Entering directory '/builddir/build/BUILD/lyx-2.3.6.1/src'
g++ -DHAVE_CONFIG_H -I. -I..
On Thursday, 27 January 2022 13.09.09 WET Scott Kostyshak wrote:
> Except for that issue does it build with -Werror ?
>
> Scott
As Jean-Marc said the compilation has lots of warnings. Some of them are not
our fault, so I am not sure if it is possible to filter system warnings from -
Werror. :-)
On Thursday, 27 January 2022 15.06.43 WET José Matos wrote:
> commit b73ab0256d113571174fed4b2a3405fe8c44d297
> Author: José Matos
> Date: Thu Jan 27 15:37:45 2022 +
>
> Fix compilation with gcc-12
> ---
> src/insets/InsetListings.cpp |1 +
> 1 files changed, 1 insertions(+), 0
On Saturday, 22 January 2022 19.49.26 WET Pavel Sanda wrote:
> Hi Jose,
>
> this what I see in curent master:
> 1. start lyx
> 2. load file
> 3. this is what I see in terminal window:
> env: '$${python}': No such file or directory
>
> Most likely related to image preview conversions, this what
On Sunday, 23 January 2022 15.01.33 WET Pavel Sanda wrote:
> On Sat, Jan 22, 2022 at 09:54:39PM +0000, José Abílio Matos wrote:
> > The problem here is that the placeholder is not replaced before being
used.
> > In order to see what python is being used you can see:
> >
Hi,
just for fun, I have been compiling lyx with gcc-latest (gcc 13 in
development). This is the error I get:
/home/jamatos/lyx/lyx.anon/src/tex2lyx/Parser.cpp: In member function ‘void
lyx::Parser::tokenize_one()’:
/home/jamatos/lyx/lyx.anon/src/tex2lyx/Parser.cpp:857:60: error: ‘uint32_t’
On Wednesday, 8 June 2022 22.47.16 WEST Jean-Marc Lasgouttes wrote:
> Note that, contrary to .tex, the .lyx file format does not consider a
> line break as a space. This is probably a mistake, but it should be
> taken into account.
>
> JMarc
That is certainly a mistake, that Joel pointed last
On Wednesday, 4 May 2022 16.52.32 WEST Richard Kimberly Heck wrote:
> FWIW, I've been using the master branch for daily work for some time and
have
> not run into any new major issues. A few small things with line breaking,
but
> they're hard to reproduce. I think one invovled a quotation mark
On Wednesday, 4 May 2022 12.48.10 WEST Pavel Sanda wrote:
> >
> > ping :)
>
> ping :)
>
> > p
Riki is not the only person busy. :-D
After the next week things will calm down a bit and I will look into that.
--
José Abílio--
lyx-devel mailing list
lyx-devel@lists.lyx.org
401 - 497 of 497 matches
Mail list logo
