Re: Virtual meetings

On Sun, Jan 3, 2021 at 9:39 PM Pavel Sanda wrote: > I would suggest we meet Mon 11 Jan, 5pm CET (4pm UTC, 11am EST) unless > there is a better proposal. > > I could send zoom invitiation if you all are ok with that. Otherwise > suggest > your tool and manage the managment side of the meeting. >

Re: Windows Installer: Future Issues

On Wed, Mar 14, 2018 at 12:23 PM, Pavel Sanda <sa...@lyx.org> wrote: > Abdelrazak Younes wrote: > > Thanks, I sometime read the devel list just for fun :-) > > That's a bizarre form of masochism :) > Where do you live now, there were some rumors we might try to organi

Re: Windows Installer: Future Issues

On Wed, Mar 14, 2018 at 11:14 AM, Pavel Sanda <sa...@lyx.org> wrote: > Jean-Marc Lasgouttes wrote: > > Le 14/03/2018 ?? 11:10, Abdelrazak Younes a écrit : > >> By the way, you should definitely release now in order to get into next > >> Ubuntu LTS release... >

Re: Windows Installer: Future Issues

By the way, you should definitely release now in order to get into next Ubuntu LTS release... On Wed, Mar 14, 2018 at 11:05 AM, Abdelrazak Younes <you...@lyx.org> wrote: > Hi Guys, > > In the old days we had the Friday rule for fight... you should restore the > tradition :-) &

Re: Windows Installer: Future Issues

Hi Guys, In the old days we had the Friday rule for fight... you should restore the tradition :-) Cheers, Abdel On Wed, Mar 14, 2018 at 7:23 AM, Jürgen Spitzmüller wrote: > Dear all, > > I have kept calm in this debate until now, but since this is getting more > and more

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

On 06/08/2016 21:58, Guillaume Munch wrote: But I agree that new move functionality in C++11 is really nice and I know that I have to unlearn the good practice I learned so many years ago in order to use them efficiently. The issue with c++11 move semantics is that it is an addition of a big

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

On 06/08/2016 17:04, Guillaume Munch wrote: Le 06/08/2016 à 10:16, Abdelrazak Younes a écrit : (1) Do not commit any part of the patch because it is so minor. This is my preference because it doesn't bring anything and it can create confusion for the beginner when compared with const

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

On 06/08/2016 14:41, Vincent van Ravesteijn wrote: But, I guess the coding standard says that functions shouldn't be longer than something like half a screen. Exactly! Cheers, Abdel.

Re: Pandora's box

Hi Guillaume, Just my 2 cents about those recent commits: 1) Switching to C++11 thread is a good thing 2) All these #if (gcc 4.6) are uglyfying the code considerably, you should enter C++11 with 2 steps or just leave it. Thanks, Abdel On 31/07/2016 19:38, Guillaume Munch wrote: Hi list,

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

Hi Scott, Too late already but my 2 cents below :-) On 27/07/2016 02:54, Scott Kostyshak wrote: The attached patch constifies a function parameter. My question is whether this patch causes more pain to other developers than it does good to the code. The patch modifies a header that is

Re: One official build system?

On 04/06/2016 10:18, Georg Baum wrote: Abdelrazak Younes wrote: Hi Guys, Funny to discover that the same discussion is coming back every couple of years :-) I am not surprised at all, maintaining two build systems with such a small amount of developers is simply stupid. I agree. The main

Re: One official build system?

Hi Guys, Funny to discover that the same discussion is coming back every couple of years :-) On 03/06/2016 22:22, Jean-Marc Lasgouttes wrote: Le 03/06/16 à 18:42, Richard Heck a écrit : Same here. I am used to autotools, so I use it. I have reservations about cmake, but I would have some

Re: [ANNOUNCE] LyX 2.2.0 Released

Congratulations guys!!! It feels really good to know that LyX is still in development after so many years :-) I look forward to trying the new version... Abdel On 28/05/2016 01:55, Scott Kostyshak wrote: Public release of LyX version 2.2.0 We are

Re: [patch] improve error output

Hi Georg, Few nitpicks inline. On 29/11/2015 18:53, Georg Baum wrote: The investigation of bug 9139 showed that the error message we give when a file operation fails is not too clever. The attached patch improves this. It is still not optimal (since qt has a very limited set of error causes

Re: Unit testing

On 03/11/2015 14:28, Jean-Marc Lasgouttes wrote: Le 02/11/2015 21:36, Vincent van Ravesteijn a écrit : Dear all, I have prepared a unit test framework based on google-test (gtest). You can see the commits at http://git.lyx.org/?p=developers/vfr/lyx.git;a=shortlog;h=refs/heads/tests. It

Re: Unit testing

On 04/11/2015 14:30, Vincent van Ravesteijn wrote: However, I would also count as advantage, if there is someone familiar with the framework and willing to do the setup and lend a helping hand to others. (Maybe, the toolkit with the most developers willing to work on should win.) We have

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

On 08/10/2015 16:14, Stephan Witt wrote: Am 08.10.2015 um 16:02 schrieb Jean-Marc Lasgouttes : I have to admit that I did not understand Abdel's idea %-| I understood it that way: to present the ellipsis character in the UI there is no need to put that character with

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

On 08/10/2015 11:58, Guillaume Munch wrote: I think that my solution is vastly superior to these proposed alternatives that misrepresent the problem, and that I have lifted the technical objections and the burden for translators. I think I mostly agree with you at this point. That being said

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

On 07/10/2015 10:54, Jean-Marc Lasgouttes wrote: Le 06/10/2015 22:17, Guillaume Munch a écrit : I think you might be mixing issues. One thing is allowing to have UTF-8 string literals especially in translations, another one is deciding that we now use … instead of ... in the interface to be

Re: Release manager for LyX 2.2

On 07/10/2015 21:35, Stephan Witt wrote: Am 07.10.2015 um 17:19 schrieb Richard Heck : On 10/07/2015 05:08 AM, Jean-Marc Lasgouttes wrote: Le 07/10/2015 11:04, Pavel Sanda a écrit : Hi all, it is very clear that we need to move forward with the release process. After the

Re: Understanding the painting process (André, Abdel, Lars, please read)

On 03/10/2015 23:46, Jean-Marc Lasgouttes wrote: Le 03/10/2015 11:50, Abdelrazak Younes a écrit : I propose to get rid of pm::insetDimension. pm is bv dependent; so it should nicely adapt to it containing bv. I would think that bv::cordCache is bv dependent too... Sure. I do

Re: Understanding the painting process (André, Abdel, Lars, please read)

On 02/10/2015 15:38, Jean-Marc Lasgouttes wrote: Hello, After a gentle push by Guillaume and a boring meeting, I decided to actually read the code that handles metrics computing and contents drawing. The result is the document below, which is available in development/PAINTING_ANALISYS. It

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

On 23/07/2015 16:45, Jean-Marc Lasgouttes wrote: Le 23/07/2015 16:29, Richard Heck a écrit : I wonder how bad this will be. In practice, people do not actually use that many different words when writing. Probably no more than a few hundred, and a couple thousand, at most. It is not a problem

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

On 23/07/2015 16:45, Jean-Marc Lasgouttes wrote: Le 23/07/2015 16:29, Richard Heck a écrit : I wonder how bad this will be. In practice, people do not actually use that many different words when writing. Probably no more than a few hundred, and a couple thousand, at most. It is not a problem

Re: [LyX/master] Fix build with GNU libstdc++ C++11 ABI

On 08/05/2015 22:03, Jean-Marc Lasgouttes wrote: Le 08/05/2015 21:19, Georg Baum a écrit : commit 51cc8aa9f6b784f806b1d9cc97fe0749ffac29af Author: Georg Baum b...@lyx.org Date: Fri May 8 21:12:42 2015 +0200 Fix build with GNU libstdc++ C++11 ABI The GNU libstdc++ that ships witch

Re: C++ question about auto_ptr

On 09/05/2015 11:37, Jean-Marc Lasgouttes wrote: Le 09/05/2015 09:18, Abdelrazak Younes a écrit : On 08/05/2015 22:13, Jean-Marc Lasgouttes wrote: With C++11, auto_ptr is deprecated and we get warnings. I am trying to see how we can get rid of it. unique_ptr is new to C++11, so I'd rather

Re: C++ question about auto_ptr

On 08/05/2015 22:13, Jean-Marc Lasgouttes wrote: With C++11, auto_ptr is deprecated and we get warnings. I am trying to see how we can get rid of it. unique_ptr is new to C++11, so I'd rather avoid that. Why that? unique_ptr is supported since gcc 4.4 released in 2009:

Re: Failure to compile lyx with gcc 5.1 with the new ABI

On 08/05/2015 21:24, Georg Baum wrote: José Matos wrote: While testing what packages failed with the new ABI one of the cases is LyX (2.1.3), the first builder to fail was the x86_64 one and this is why this message refers to it:

Re: Failure to compile lyx with gcc 5.1 with the new ABI

On 09/05/2015 11:39, Jean-Marc Lasgouttes wrote: Le 09/05/2015 09:30, Abdelrazak Younes a écrit : Now with modern compilers and STL, string is much cheaper... Do you have a reference for that? My own experience + just some article that I read about gcc's and clang's STL minimizing

Re: C++ question about auto_ptr

On 08/05/2015 22:13, Jean-Marc Lasgouttes wrote: With C++11, auto_ptr is deprecated and we get warnings. I am trying to see how we can get rid of it. unique_ptr is new to C++11, so I'd rather avoid that. Why that? unique_ptr is supported since gcc 4.4 released in 2009:

Re: Failure to compile lyx with gcc 5.1 with the new ABI

On 08/05/2015 21:24, Georg Baum wrote: José Matos wrote: While testing what packages failed with the new ABI one of the cases is LyX (2.1.3), the first builder to fail was the x86_64 one and this is why this message refers to it:

Re: [LyX/master] Fix build with GNU libstdc++ C++11 ABI

On 08/05/2015 22:03, Jean-Marc Lasgouttes wrote: Le 08/05/2015 21:19, Georg Baum a écrit : commit 51cc8aa9f6b784f806b1d9cc97fe0749ffac29af Author: Georg Baum Date: Fri May 8 21:12:42 2015 +0200 Fix build with GNU libstdc++ C++11 ABI The GNU libstdc++ that ships

Re: C++ question about auto_ptr

On 09/05/2015 11:37, Jean-Marc Lasgouttes wrote: Le 09/05/2015 09:18, Abdelrazak Younes a écrit : On 08/05/2015 22:13, Jean-Marc Lasgouttes wrote: With C++11, auto_ptr is deprecated and we get warnings. I am trying to see how we can get rid of it. unique_ptr is new to C++11, so I'd rather

Re: Failure to compile lyx with gcc 5.1 with the new ABI

On 09/05/2015 11:39, Jean-Marc Lasgouttes wrote: Le 09/05/2015 09:30, Abdelrazak Younes a écrit : Now with modern compilers and STL, is much cheaper... Do you have a reference for that? My own experience + just some article that I read about gcc's and clang's STL minimizing

Re: new compiler warnings in master

On 18/03/2015 11:39, Jean-Marc Lasgouttes wrote: Le 18/03/2015 08:30, Uwe Stöhr a écrit : Within the last 2 weeks a commit lead to these new compiler warnings: (The same that I constantly report here. I am wondering why the appear so often with recent commits.) The warnings should be gone

Re: [LyX/master] Grr...

On 16/03/2015 14:29, Juergen Spitzmueller wrote: commit 066d6a9cfb3936c61b514d085df01dd6835c784a Author: Juergen Spitzmueller sp...@lyx.org Date: Mon Mar 16 14:30:02 2015 +0100 Grr... By the way, we use at works clang-format for coding style formatting. I am confident that all LyX

Re: new compiler warnings in master

On 18/03/2015 11:39, Jean-Marc Lasgouttes wrote: Le 18/03/2015 08:30, Uwe Stöhr a écrit : Within the last 2 weeks a commit lead to these new compiler warnings: (The same that I constantly report here. I am wondering why the appear so often with recent commits.) The warnings should be gone

Re: [LyX/master] Grr...

On 16/03/2015 14:29, Juergen Spitzmueller wrote: commit 066d6a9cfb3936c61b514d085df01dd6835c784a Author: Juergen Spitzmueller Date: Mon Mar 16 14:30:02 2015 +0100 Grr... By the way, we use at works clang-format for coding style formatting. I am confident that all LyX

Re: [patch] LyX logo logoification

On 13/03/2015 15:21, Jean-Marc Lasgouttes wrote: Le 13/03/2015 12:10, Jean-Marc Lasgouttes a écrit : In this patch, I change our new LyX logo inset to look like the real thing. Georg, is there a reason why your chose not to follow this route (or only lack of time/motivation). Also, I am not

Re: [patch] Prefer svg icons

Hi Enrico, On 16/02/2015 15:21, Enrico Forestieri wrote: The attached patch let LyX use svg icons (if they exist) in preference to png ones. The svg icons automatically scale to the wanted dimension and the patch introduces 2 more resolutions (huge and giant icons) that should be useful to

Re: [patch] LyX logo logoification

On 15/03/2015 18:29, Jean-Marc Lasgouttes wrote: Le 15/03/15 08:44, Abdelrazak Younes a écrit : Comments? You use lots of hardcoded constants nobody except you will understand 1 month from now, and not even you 1 year from now :-P What is the LaTeX source code good for? I didn't know

Re: [patch] LyX logo logoification

On 13/03/2015 15:21, Jean-Marc Lasgouttes wrote: Le 13/03/2015 12:10, Jean-Marc Lasgouttes a écrit : In this patch, I change our new LyX logo inset to look like the real thing. Georg, is there a reason why your chose not to follow this route (or only lack of time/motivation). Also, I am not

Re: [patch] Prefer svg icons

Hi Enrico, On 16/02/2015 15:21, Enrico Forestieri wrote: The attached patch let LyX use svg icons (if they exist) in preference to png ones. The svg icons automatically scale to the wanted dimension and the patch introduces 2 more resolutions (huge and giant icons) that should be useful to

Re: [patch] LyX logo logoification

On 15/03/2015 18:29, Jean-Marc Lasgouttes wrote: Le 15/03/15 08:44, Abdelrazak Younes a écrit : Comments? You use lots of hardcoded constants nobody except you will understand 1 month from now, and not even you 1 year from now :-P What is the LaTeX source code good for? I didn't know

Re: Thread problems with std::basic_string and GNU libstdc++

On 22/11/2014 23:01, Richard Heck wrote: On 11/22/2014 03:19 AM, Abdelrazak Younes wrote: On 20/11/2014 21:04, Georg Baum wrote: I don't think so in this case. The crash happens because internal std::basic_string members are corrupt, and it is almost always a string created from Language

Re: Thread problems with std::basic_string and GNU libstdc++

On 23/11/2014 22:21, Richard Heck wrote: On 11/23/2014 02:38 PM, Jean-Marc Lasgouttes wrote: Le 23/11/2014 18:34, Abdelrazak Younes a écrit : This string might be modified by some class in main thread while being read at the same time by a buffer clone in the export thread. If the memory

Re: Thread problems with std::basic_string and GNU libstdc++

On 22/11/2014 23:01, Richard Heck wrote: On 11/22/2014 03:19 AM, Abdelrazak Younes wrote: On 20/11/2014 21:04, Georg Baum wrote: I don't think so in this case. The crash happens because internal std::basic_string members are corrupt, and it is almost always a string created from Language

Re: Thread problems with std::basic_string and GNU libstdc++

On 23/11/2014 22:21, Richard Heck wrote: On 11/23/2014 02:38 PM, Jean-Marc Lasgouttes wrote: Le 23/11/2014 18:34, Abdelrazak Younes a écrit : This string might be modified by some class in main thread while being read at the same time by a buffer clone in the export thread. If the memory

Re: Thread problems with std::basic_string and GNU libstdc++

On 20/11/2014 21:04, Georg Baum wrote: I don't think so in this case. The crash happens because internal std::basic_string members are corrupt, and it is almost always a string created from Language::babel_. Furthermore, I was not able to reproduce the crash after changing std::string const

Re: Thread problems with std::basic_string and GNU libstdc++

On 20/11/2014 21:04, Georg Baum wrote: I don't think so in this case. The crash happens because internal std::basic_string members are corrupt, and it is almost always a string created from Language::babel_. Furthermore, I was not able to reproduce the crash after changing std::string const &

Re: Thread problems with std::basic_string and GNU libstdc++

Hi Georg, Warning: I haven't read LyX source code for a long long time :-) On 19/11/2014 22:43, Georg Baum wrote: Hi, while investigating http://www.lyx.org/trac/ticket/9336 I found out a fundamental problem with our multithreaded export: The GNU libstdc++ gives only a relatively weak

Re: Thread problems with std::basic_string and GNU libstdc++

Hi Georg, Warning: I haven't read LyX source code for a long long time :-) On 19/11/2014 22:43, Georg Baum wrote: Hi, while investigating http://www.lyx.org/trac/ticket/9336 I found out a fundamental problem with our multithreaded export: The GNU libstdc++ gives only a relatively weak

Re: [LyX/master] Prevent accidental usage of wrong copy constructor

On 14/11/2014 18:48, Georg Baum wrote: Jean-Marc Lasgouttes wrote: Le 11/11/2014 20:58, Georg Baum a écrit : commit 8f93600d3fa8182ba43973075cf37e7ecb2be8d3 Author: Georg Baum b...@lyx.org Date: Tue Nov 11 07:22:14 2014 +0100 Prevent accidental usage of wrong copy constructor Is

Re: [LyX/master] Prevent accidental usage of wrong copy constructor

On 14/11/2014 18:48, Georg Baum wrote: Jean-Marc Lasgouttes wrote: Le 11/11/2014 20:58, Georg Baum a écrit : commit 8f93600d3fa8182ba43973075cf37e7ecb2be8d3 Author: Georg Baum Date: Tue Nov 11 07:22:14 2014 +0100 Prevent accidental usage of wrong copy constructor Is

Re: cmake warnings

On Sun, May 11, 2014 at 12:22 AM, Kornel Benko kor...@lyx.org wrote: Am Samstag, 10. Mai 2014 um 22:26:24, schrieb Abdelrazak Younes you...@lyx.org On Sat, May 10, 2014 at 9:50 PM, Kornel Benko kor...@lyx.org wrote: Am Samstag, 10. Mai 2014 um 18:32:13, schrieb Abdelrazak Younes you

Re: Where is my menubar?

On Sun, May 11, 2014 at 7:03 AM, Scott Kostyshak skost...@lyx.org wrote: On Sun, May 11, 2014 at 12:54 AM, Scott Kostyshak skost...@lyx.org wrote: For me, toggling fullscreen on and off fixes the problem: lyx -x command-sequence ui-toggle fullscreen; ui-toggle fullscreen Or more simply:

Re: cmake warnings

On Sun, May 11, 2014 at 11:09 AM, Kornel Benko kor...@lyx.org wrote: You do miss some. LYX_CPACK, LYX_ASPELL, LYX_ENCHANT, LYX_HUNSPELL. (If you don't use CPACK then at least use LYX_INSTALL option) Hunspell is installed on my system, why don't we pick that automatically?

Re: Call for testers: the features/str-metrics branch

On Thu, May 8, 2014 at 7:01 PM, Jean-Marc Lasgouttes lasgout...@lyx.orgwrote: Le 08/05/14 18:45, Abdelrazak Younes a écrit : I don't read Arabic but my wife does. I'll see if I can find time over the week-end to compile your branch. Thanks, you're a sweetheart. I already know that cursor

Re: cmake warnings

On Sun, May 11, 2014 at 11:23 AM, Scott Kostyshak skost...@lyx.org wrote: On Sun, May 11, 2014 at 5:16 AM, Abdelrazak Younes you...@lyx.org wrote: On Sun, May 11, 2014 at 11:09 AM, Kornel Benko kor...@lyx.org wrote: Hunspell is installed on my system, why don't we pick

Re: cmake warnings

On Sun, May 11, 2014 at 12:22 AM, Kornel Benko <kor...@lyx.org> wrote: > Am Samstag, 10. Mai 2014 um 22:26:24, schrieb Abdelrazak Younes < > you...@lyx.org> > > On Sat, May 10, 2014 at 9:50 PM, Kornel Benko <kor...@lyx.org> wrote: > > > > > Am Samstag,

Re: Where is my menubar?

On Sun, May 11, 2014 at 7:03 AM, Scott Kostyshak wrote: > On Sun, May 11, 2014 at 12:54 AM, Scott Kostyshak > wrote: > > > For me, toggling fullscreen on and off fixes the problem: > > lyx -x "command-sequence ui-toggle fullscreen; ui-toggle fullscreen" > >

Re: cmake warnings

On Sun, May 11, 2014 at 11:09 AM, Kornel Benko wrote: > > > You do miss some. > > > LYX_CPACK, LYX_ASPELL, LYX_ENCHANT, LYX_HUNSPELL. > > > > > > (If you don't use CPACK then at least use LYX_INSTALL option) > > > > > > > Hunspell is installed on my system, why don't we pick

Re: Call for testers: the features/str-metrics branch

On Thu, May 8, 2014 at 7:01 PM, Jean-Marc Lasgouttes <lasgout...@lyx.org>wrote: > Le 08/05/14 18:45, Abdelrazak Younes a écrit : > > I don't read Arabic but my wife does. I'll see if I can find time over >> the week-end to compile your branch. >> > > Thanks, yo

Re: cmake warnings

On Sun, May 11, 2014 at 11:23 AM, Scott Kostyshak <skost...@lyx.org> wrote: > On Sun, May 11, 2014 at 5:16 AM, Abdelrazak Younes <you...@lyx.org> wrote: > > On Sun, May 11, 2014 at 11:09 AM, Kornel Benko <kor...@lyx.org> wrote: > >> > >> > Hunsp

Re: Converters: Skip Qt's loadable svg function

On 07/05/2014 09:08, Pavel Sanda wrote: Vincent van Ravesteijn wrote: Now I remember why I didn't do that. We might want the Qt-automatic-way as a fallback when no custom converter is defined. Exactly. If user wants to have svg he has to install something to get pdf output, so the fallback

cmake warnings

Hi guys, Just checked out feature/str-metrics and I got some warning when running cmake: CMake Warning (dev) at src/CMakeLists.txt:106 (add_executable): Policy CMP0028 is not set: Double colon in target name means ALIAS or IMPORTED target. Run cmake --help-policy CMP0028 for policy

Where is my menubar?

Hi, Just compiled a fresh str-metrics under kubuntu 14.04 (Qt4.8) and there is no menubar. This is actually the same for Firefox but there I can press Alt key to show it. Under Lyx, nothing... Alt+F just print 'f'... Abdel.

Re: Where is my menubar?

On Sat, May 10, 2014 at 6:42 PM, Abdelrazak Younes you...@lyx.org wrote: Hi, Just compiled a fresh str-metrics under kubuntu 14.04 (Qt4.8) and there is no menubar. This is actually the same for Firefox but there I can press Alt key to show it. Under Lyx, nothing... Alt+F just print 'f

Re: Where is my menubar?

On Sat, May 10, 2014 at 7:10 PM, Pavel Sanda sa...@lyx.org wrote: Abdelrazak Younes wrote: Just for completeness. Ubuntu package 2.0.7 does not have this issue. I guess you use the unity crap, right? ;) https://bugs.launchpad.net/ubuntu/+source/libdbusmenu/+bug/619811 No, plain KDE. But I

Re: Where is my menubar?

On Sat, May 10, 2014 at 9:36 PM, Abdelrazak Younes you...@lyx.org wrote: On Sat, May 10, 2014 at 7:10 PM, Pavel Sanda sa...@lyx.org wrote: Abdelrazak Younes wrote: Just for completeness. Ubuntu package 2.0.7 does not have this issue. I guess you use the unity crap, right? ;) https

Re: cmake warnings

On Sat, May 10, 2014 at 9:50 PM, Kornel Benko kor...@lyx.org wrote: Am Samstag, 10. Mai 2014 um 18:32:13, schrieb Abdelrazak Younes you...@lyx.org Hi guys, Just checked out feature/str-metrics and I got some warning when running cmake: CMake Warning (dev) at src/CMakeLists.txt:106

Re: Converters: Skip Qt's loadable svg function

On 07/05/2014 09:08, Pavel Sanda wrote: Vincent van Ravesteijn wrote: Now I remember why I didn't do that. We might want the Qt-automatic-way as a fallback when no custom converter is defined. Exactly. If user wants to have svg he has to install something to get pdf output, so the fallback

cmake warnings

Hi guys, Just checked out feature/str-metrics and I got some warning when running cmake: CMake Warning (dev) at src/CMakeLists.txt:106 (add_executable): Policy CMP0028 is not set: Double colon in target name means ALIAS or IMPORTED target. Run "cmake --help-policy CMP0028" for policy

Where is my menubar?

Hi, Just compiled a fresh str-metrics under kubuntu 14.04 (Qt4.8) and there is no menubar. This is actually the same for Firefox but there I can press Alt key to show it. Under Lyx, nothing... Alt+F just print 'f'... Abdel.

Re: Where is my menubar?

On Sat, May 10, 2014 at 6:42 PM, Abdelrazak Younes <you...@lyx.org> wrote: > Hi, > > Just compiled a fresh str-metrics under kubuntu 14.04 (Qt4.8) and there is > no menubar. This is actually the same for Firefox but there I can press Alt > key to show it. Under Lyx, nothing..

Re: Where is my menubar?

On Sat, May 10, 2014 at 7:10 PM, Pavel Sanda <sa...@lyx.org> wrote: > Abdelrazak Younes wrote: > > Just for completeness. Ubuntu package 2.0.7 does not have this issue. > > I guess you use the unity crap, right? ;) > https://bugs.launchpad.net/ubuntu/+source/libdbusmenu/

Re: Where is my menubar?

On Sat, May 10, 2014 at 9:36 PM, Abdelrazak Younes <you...@lyx.org> wrote: > On Sat, May 10, 2014 at 7:10 PM, Pavel Sanda <sa...@lyx.org> wrote: > >> Abdelrazak Younes wrote: >> > Just for completeness. Ubuntu package 2.0.7 does not have this issue. >> &

Re: cmake warnings

On Sat, May 10, 2014 at 9:50 PM, Kornel Benko <kor...@lyx.org> wrote: > Am Samstag, 10. Mai 2014 um 18:32:13, schrieb Abdelrazak Younes < > you...@lyx.org> > > Hi guys, > > > > Just checked out feature/str-metrics and I got some warning when running > >

Re: Call for testers: the features/str-metrics branch

On 06/05/2014 11:06, Jean-Marc Lasgouttes wrote: 04/05/2014 22:14, Vincent van Ravesteijn: When selecting the first character, I see two things: 1) the connection between characters is lost (in master this is not the case) 2) the first character actually moves to the right on selection (while

Re: Call for testers: the features/str-metrics branch

On 06/05/2014 11:06, Jean-Marc Lasgouttes wrote: 04/05/2014 22:14, Vincent van Ravesteijn: When selecting the first character, I see two things: 1) the connection between characters is lost (in master this is not the case) 2) the first character actually moves to the right on selection (while

Re: Copying and pasting to other apps

On 27/04/2014 23:11, Tommaso Cucinotta wrote: On 27/04/14 16:58, Georg Baum wrote: If you copy something, it is put onto the clipboard in three formats: plain text, HTML (using the HTML export) and LyX since version 2.1. The pasting application is then supposed to select the most appropriate

Re: Feature request

On 29/04/2014 18:20, Richard Heck wrote: On 04/28/2014 06:10 PM, stefano franchi wrote: On Mon, Apr 28, 2014 at 4:14 PM, Tommaso Cucinotta tomm...@lyx.org mailto:tomm...@lyx.org wrote: On 28/04/14 19:37, Patrick O'Keeffe wrote: I don't personally see any advantage to composing

Re: Copying and pasting to other apps

On 27/04/2014 23:11, Tommaso Cucinotta wrote: On 27/04/14 16:58, Georg Baum wrote: If you copy something, it is put onto the clipboard in three formats: plain text, HTML (using the HTML export) and LyX since version 2.1. The pasting application is then supposed to select the most appropriate

Re: Feature request

On 29/04/2014 18:20, Richard Heck wrote: On 04/28/2014 06:10 PM, stefano franchi wrote: On Mon, Apr 28, 2014 at 4:14 PM, Tommaso Cucinotta > wrote: On 28/04/14 19:37, Patrick O'Keeffe wrote: I don't personally see any advantage to

Re: Feature request

On 24/04/2014 17:02, Kornel Benko wrote: Am Donnerstag, 24. April 2014 um 17:00:16, schrieb Kornel Benko kor...@lyx.org Am Donnerstag, 24. April 2014 um 07:49:02, schrieb Pavel Sanda sa...@lyx.org Kornel Benko wrote: Html is inappropriate for email

Re: Feature request

On 24/04/2014 15:08, Jean-Marc Lasgouttes wrote: 24/04/2014 15:02, Kornel Benko: What is so beautiful about the typography of the .html files we export, though? C'mon, its not so bad. For a mail it should be OK. Do you see an added value wrt whatever html one can produce with

Re: Feature request

On 24/04/2014 17:02, Kornel Benko wrote: Am Donnerstag, 24. April 2014 um 17:00:16, schrieb Kornel Benko Am Donnerstag, 24. April 2014 um 07:49:02, schrieb Pavel Sanda Kornel Benko wrote: Html is inappropriate for email

Re: Feature request

On 24/04/2014 15:08, Jean-Marc Lasgouttes wrote: 24/04/2014 15:02, Kornel Benko: > What is so beautiful about the typography of the .html files we export, > though? C'mon, its not so bad. For a mail it should be OK. Do you see an added value wrt whatever html one can produce with

Re: Dialog-Related Bug 8144

On 19/04/2014 17:51, Richard Heck wrote: Can someone who knows a bit about dialogs have a look at the patch attached to: http://www.lyx.org/trac/ticket/8144 please? Hi Richard, I added a comment there that you should use a vector of pair of strings instead. The patch is not really about

Re: #7437: Assertion isDirectory() violated after importing '/a/' as plain text

On 23/03/2014 13:33, LyX Ticket Tracker wrote: #7437: Assertion isDirectory() violated after importing '/a/' as plain text ---+--- Reporter: gmatht@… | Owner: younes Type: defect | Status: new

Re: #7437: Assertion isDirectory() violated after importing '/a/' as plain text

On 19/04/2014 19:15, Richard Heck wrote: On 04/19/2014 01:07 PM, Abdelrazak Younes wrote: On 23/03/2014 13:33, LyX Ticket Tracker wrote: #7437: Assertion isDirectory() violated after importing '/a/' as plain text ---+--- Reporter: gmatht

Re: #7437: Assertion isDirectory() violated after importing '/a/' as plain text

On 19/04/2014 19:25, Richard Heck wrote: On 04/19/2014 01:17 PM, Abdelrazak Younes wrote: If you want to remove yourself as owner of the other bugs, that is fairly easy to do via Batch Modify. Just select all the bugs you want to change and switch Owner to nobody. Hum, what is Batch

Re: Anybody Wanna Own Some Bugs?

On 19/04/2014 19:22, Richard Heck wrote: Abdel has asked to be removed as default owner for the dialog and frontend-qt4 bugs, and I've also removed him as default owner of the file and menu bugs. Would anyone like to replace him? The only thing this really means is that you get an email when

Re: Dialog-Related Bug 8144

On 19/04/2014 17:51, Richard Heck wrote: Can someone who knows a bit about dialogs have a look at the patch attached to: http://www.lyx.org/trac/ticket/8144 please? Hi Richard, I added a comment there that you should use a vector of pair of strings instead. The patch is not really about

Re: #7437: Assertion isDirectory() violated after importing '/a/' as plain text

On 23/03/2014 13:33, LyX Ticket Tracker wrote: #7437: Assertion isDirectory() violated after importing '/a/' as plain text ---+--- Reporter: gmatht@… | Owner: younes Type: defect | Status: new

Re: #7437: Assertion isDirectory() violated after importing '/a/' as plain text

On 19/04/2014 19:15, Richard Heck wrote: On 04/19/2014 01:07 PM, Abdelrazak Younes wrote: On 23/03/2014 13:33, LyX Ticket Tracker wrote: #7437: Assertion isDirectory() violated after importing '/a/' as plain text ---+--- Reporter: gmatht

Re: #7437: Assertion isDirectory() violated after importing '/a/' as plain text

On 19/04/2014 19:25, Richard Heck wrote: On 04/19/2014 01:17 PM, Abdelrazak Younes wrote: If you want to remove yourself as owner of the other bugs, that is fairly easy to do via Batch Modify. Just select all the bugs you want to change and switch "Owner" to nobody. Hum, what

Re: Anybody Wanna Own Some Bugs?

On 19/04/2014 19:22, Richard Heck wrote: Abdel has asked to be removed as default owner for the dialog and frontend-qt4 bugs, and I've also removed him as default owner of the file and menu bugs. Would anyone like to replace him? The only thing this really means is that you get an email when

Re: About using git as file format for lyx ...

On 07/03/2014 03:09, Tommaso Cucinotta wrote: ... instead of XML, as discussed so often ... https://plus.google.com/+LinusTorvalds/posts/X2XVf9Q7MfV Bad idea for a document, LyX is used to create structured document, not database, we are not going to create a new directory for each new

Re: About using git as file format for lyx ...

On 08/03/2014 17:20, Richard Heck wrote: On 03/08/2014 10:31 AM, Liviu Andronic wrote: On Sat, Mar 8, 2014 at 10:51 AM, Liviu Andronic landronim...@gmail.com wrote: On Sat, Mar 8, 2014 at 8:54 AM, Abdelrazak Younes you...@lyx.org wrote: On 07/03/2014 03:09, Tommaso Cucinotta wrote

  1   2   3   4   5   6   7   8   9   10   >