Dear Pavel,
On 2020-11-24, Pavel Sanda wrote:
> On Tue, Nov 24, 2020 at 09:32:53PM -, Guenter Milde wrote:
>> * How can I change the security policy and why does it prevent EPS
>> generation by default?
> Well known problem with imagemagick configuration. Bunch of distros
> fear potential
On 2020-11-24, Guenter Milde wrote:
> On 2020-11-24, Kornel Benko wrote:
>> Am Tue, 24 Nov 2020 10:39:00 +0100 schrieb Kornel Benko :
>>> Am Tue, 24 Nov 2020 09:31:39 - (UTC) schrieb Guenter Milde
>>> :
> ...
>>> > export of lib/Intro.lyx (and other lib/*/Intro.lyx) document to DVI or PS
>>>
Le 25/11/2020 à 01:14, Yuriy Skalko a écrit :
commit fe0ea7bff7d89a4edaec83a272769281d39695d2
Author: Yuriy Skalko
Date: Tue Nov 24 20:46:49 2020 +0200
Add default TransformID enum value
Now I get this warning (with gcc 5.4, if it matters):
../../master/src/insets/ExternalSupport.cpp:
Am Wed, 25 Nov 2020 03:05:43 +0200
schrieb Yuriy Skalko :
> > Yes, that is a problem with non-ascii. These characters takes more than one
> > byte,
> > but tour search-engine uses UTF8 instead of wchar.
> > So, for instance you cannot use structs like [е-р] (Cyrillic chars).
> > Would be a good p
On Wed, Nov 25, 2020 at 09:18:04AM -, Guenter Milde wrote:
> Dear Pavel,
>
> This did the trick.
After reading about the same problem again again on our list I filed
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975678
I suggest to file similar bug report for whatever distro you are
using
I see a couple of changes in behavior in advanced find that can be
reproduced with the Welcome.lyx file (I attached it for convenience).
1. In advanced find, put "a" in the find area and "c" in the replace
area and do "Replace all". It takes about 10 seconds with 2.3.0, and
about 25 seconds
While experimenting with undo/redo after a "replace all" with Advanced
find, I received an assertion. I think the cursor was in the "Find" work
area. Unfortunately, I cannot reproduce. The assertion and terminal (not
GDB) backtrace is attached.
Scott
support/lassert.cpp (52): ASSERTION false VIOLA
On 11/25/20 6:41 AM, Juergen Spitzmueller wrote:
commit 17ebec693ad1fce6961867a5514217707a8f8051
Author: Juergen Spitzmueller
Date: Wed Nov 25 13:10:04 2020 +0100
Fix tex4ht odt converter
Private message by Michal Hoftich (tex4ht head developer):
oolatex is not reco
Now I get this warning (with gcc 5.4, if it matters):
../../master/src/insets/ExternalSupport.cpp: In function ‘const string
lyx::external::{anonymous}::substituteIt(const string&, lyx::external::TransformID, const
string&, const lyx::external::Template::Format&, const lyx::InsetExternalParams
Le 25/11/2020 à 19:30, Yuriy Skalko a écrit :
Fixed this and several other issues. Patches attached.
1/ I do not know cmake, but it is strange that you still have code after
a FATAL_ERROR
2/ fine
3/ thanks for spotting it
4/ fine.
JMarc
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
ht
1/ I do not know cmake, but it is strange that you still have code after a
FATAL_ERROR
It is not my favorite language too, and I should not take later checking
of MSVC compiler as a template. Corrected it in both places.
Seems like std::regex was already always used for most recent compiler
I assume that careful replacement string to docstring will be mostly
enough.
No, we need wstring. Regular expressions (wregex) work on wchar_t.
Kornel
wchar_t can cause problems with portability (it is 4 bytes on Unix and 2
on Windows). So maybe defining docregex as basic_regex (lik
12 matches
Mail list logo
