Le 21/06/2016 01:07, Richard Heck a écrit :
I would agree with this change, which should be properly documented.
PS Do you think this is all right for stable, even though it is a change of
behavior? We won't do anything with layout2layout
I tend to think so, but you should rather ask Geor
On 06/20/2016 11:03 PM, Jean-Marc Lasgouttes wrote:
Le 20/06/2016 17:34, Richard Heck a écrit :
At the moment, it is possible to effect a layout change inside almost
all of our character styles. So far as I can see, this is almost always
a bug. One does not want, e.g., to be able to switch to a
On 06/20/2016 11:03 PM, Jean-Marc Lasgouttes wrote:
Le 20/06/2016 17:34, Richard Heck a écrit :
At the moment, it is possible to effect a layout change inside almost
all of our character styles. So far as I can see, this is almost always
a bug. One does not want, e.g., to be able to switch to a
On 06/20/2016 11:04 PM, Jean-Marc Lasgouttes wrote:
Le 20/06/2016 18:37, Richard Heck a écrit :
I propose that bugs meeting that description (such as #4398) simply be
marked as having status "Fixed". The "Fixed in Master" status seems
misleading: They are not going to get fixed in stable. If we
Am Montag, 20. Juni 2016 um 16:04:03, schrieb Joel Kulesza
> On Mon, Jun 20, 2016 at 3:39 PM, Kornel Benko wrote:
>
> >
> > Your QT4 is installed under /opt/anaconda1anaconda2anaconda3.
> > Look for include files in /opt/anaconda1anaconda2anaconda3/include
> >
>
> Something is definitely weir
Le 20/06/2016 18:37, Richard Heck a écrit :
I propose that bugs meeting that description (such as #4398) simply be
marked as having status "Fixed". The "Fixed in Master" status seems
misleading: They are not going to get fixed in stable. If we mark them
Fixed, it can mean: We are done with them.
On Mon, Jun 20, 2016 at 3:39 PM, Kornel Benko wrote:
>
> Your QT4 is installed under /opt/anaconda1anaconda2anaconda3.
> Look for include files in /opt/anaconda1anaconda2anaconda3/include
>
Something is definitely weird with respect to the install:
1127 jkulesza@machine[~/tmp/test]> which qma
Le 20/06/2016 17:34, Richard Heck a écrit :
At the moment, it is possible to effect a layout change inside almost
all of our character styles. So far as I can see, this is almost always
a bug. One does not want, e.g., to be able to switch to an enumeration
inside the Code character style. So I p
Am Montag, 20. Juni 2016 um 15:25:02, schrieb Joel Kulesza
> On Mon, Jun 20, 2016 at 1:07 PM, Kornel Benko wrote:
>
> >
> > Please give us the full command line used fir the cmake call.
> >
>
> cmake ../. --- which points to the CMakeLists in the base directory.
> Perhaps I should point it to
On Mon, Jun 20, 2016 at 1:07 PM, Kornel Benko wrote:
>
> Please give us the full command line used fir the cmake call.
>
cmake ../. --- which points to the CMakeLists in the base directory.
Perhaps I should point it to another directory or pass additional options?
> Where is your QT installed
On Mon, Jun 20, 2016 at 12:59 PM, Georg Baum wrote:
>
> -std=c++11 wil likely not work with the old qt. The other flags look OK. I
> would be interested to see what happens if you call configure with --
> disable-cxx11. If that does not help then I am out of ideas and would
> suggest to stop the
Am Montag, 20. Juni 2016 um 09:03:35, schrieb Joel Kulesza
> > On Sun, Jun 19, 2016 at 9:53 AM, Georg Baum <
> > georg.b...@post.rwth-aachen.de> wrote:
> >
...
>
> I did try compiling with CMake and see the error(s) below:
Please give us the full command line used fir the cmake call.
> 1026 j
racoon wrote:
> On 20.06.2016 10:14, racoon wrote:
>> On 19.06.2016 20:02, Georg Baum wrote:
>>>
>>> Yes. Does cmake still not recognize the compiler if you call it from
>>> that command window? In that case please send the CMakeError.log and
>>> CMakeOutput.log files created by cmake, this would
Joel Kulesza wrote:
> All the gore and carnage for the failing source file from the configure
> with "--disable-silent-rules" below my signature.
>
> I did try compiling with CMake and see the error(s) below:
>
> 1026 jkulesza@machine[~/SRC/lyx220/build_cmake]> cmake ../.
> -- TOP_SRC_DIR = /hom
I propose that bugs meeting that description (such as #4398) simply be
marked as having status "Fixed". The "Fixed in Master" status seems
misleading: They are not going to get fixed in stable. If we mark them
Fixed, it can mean: We are done with them.
Note that this is different from having the
On 06/20/2016 11:34 AM, Richard Heck wrote:
> At the moment, it is possible to effect a layout change inside almost
> all of our character styles. So far as I can see, this is almost always
> a bug. One does not want, e.g., to be able to switch to an enumeration
> inside the Code character style. S
At the moment, it is possible to effect a layout change inside almost
all of our character styles. So far as I can see, this is almost always
a bug. One does not want, e.g., to be able to switch to an enumeration
inside the Code character style. So I propose the following simple patch:
diff --git
On Sun, Jun 19, 2016 at 3:30 PM, Joel Kulesza wrote:
> On Sun, Jun 19, 2016 at 9:53 AM, Georg Baum <
> georg.b...@post.rwth-aachen.de> wrote:
>
>
>> You get this if you call configure with --disable-silent-rules (from the
>> log file I assume that you use autotools and not cmake to compile).
>
>
Some time back, there was a discussion on the list about the labels of
collapsed branches. As it is now, we display a bit of text from the
branch. The general view was that this is not very useful, and it makes
documents with lots of branches look terrible. The proposal was to label
collapsed bran
On 06/19/2016 11:06 AM, Georg Baum wrote:
> commit 5ab19af7820fba58876ac86efd8cc4aa1e75b44f
> Author: Georg Baum
> Date: Sun Jun 19 17:05:13 2016 +0200
>
> Skip paragraph parameters for dash conversion
>
> Some of them are directly passed to LaTeX, but for all of them a token
>
On 20.06.2016 10:14, racoon wrote:
On 19.06.2016 20:02, Georg Baum wrote:
racoon wrote:
In a common command window cl is not found.
This is actually good. It means your PATH is not poisoned by specific
MSVC
tools.
But if I start
1) Open Developer Command Prompt for VS2015
2) call 'cl -v'
On 19.06.2016 20:12, Kornel Benko wrote:
Am Sonntag, 19. Juni 2016 um 19:52:25, schrieb racoon
On 19.06.2016 19:36, Kornel Benko wrote:
Am Sonntag, 19. Juni 2016 um 19:23:14, schrieb racoon
On 19.06.2016 18:20, Georg Baum wrote:
racoon wrote:
...
The most important question now is why
On 19.06.2016 20:02, Georg Baum wrote:
racoon wrote:
In a common command window cl is not found.
This is actually good. It means your PATH is not poisoned by specific MSVC
tools.
But if I start
1) Open Developer Command Prompt for VS2015
2) call 'cl -v'
I get
Microsoft (R) C/C++ Optimizi
23 matches
Mail list logo