Dear lyx developer,
I would like to continue Bahasa Indonesia menu translation of id.po
Could you please send me the latest id.po
Best regards,
Waluyo Adi Siswanto
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
Since commit 2ec243 (28/10) cmake builds defaults apparently to --std=c++17.
Building with Xcode (11.3) on macos (10.14.6) then fails with message
"call to 'make_unique' is ambiguous"
make_unique() is in lyx/.../support/unique_ptr.h and in Xcode.app/.../memory
This is the full error message:
On Thu, Nov 12, 2020 at 09:32:16AM -0500, Richard Kimberly Heck wrote:
> Can someone give me a quick tutorial on how to use some profiler or
> other? I'm starting to understand the updateMacros code well enough that
> that will be useful.
https://wiki.lyx.org/FAQ/AllPages#profile
Not in wiki (yet
Can someone give me a quick tutorial on how to use some profiler or
other? I'm starting to understand the updateMacros code well enough that
that will be useful.
Riki
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mailman/listinfo/lyx-devel
On 11/11/20 1:22 PM, Jean-Marc Lasgouttes wrote:
> Le 11/11/2020 à 19:16, Richard Kimberly Heck a écrit :
>>> I really think that we should reduce our use of codes as much as
>>> possible. Isn't it possible to use a virtual method here that would
>>> be implemented by each inset? t is bad to have t
On Thu, Nov 12, 2020 at 08:57:42PM +1300, Sam Crawley wrote:
> In that case, I'll add a different parameter to the LFUN to differentiate
> between case (ii) and (iii). So instead of passing "run" (and the two file
> names), you will pass "run-sync" to indicate that you want it to block for
> the
Le 12/11/2020 à 13:21, Yuriy Skalko a écrit :
Not a problem. Good naming can make code really intuitive and easy to
understand. It is worth to spend some time on this.
I've committed the updated patch.
Thanks.
JMarc
--
lyx-devel mailing list
lyx-devel@lists.lyx.org
http://lists.lyx.org/mail
I still prefer noChange() or nullChange() to changeNone(), but we would have to
ask a native English speaker.
I proposed `changeNone` to have consistent naming for all
change`Something` functions. But noChange is also good. If there will be
any comments from native speakers, it can be renamed
