Re: lyx-2.3.0alpha1-1 crash

[Guillaume MM]

Le 26/05/2017 à 23:29, Guillaume MM a écrit :

Le 26/05/2017 à 23:15, PhilipPirrip a écrit :

On 05/26/2017 05:04 PM, PhilipPirrip wrote:


I think I caught this one too. I was working on a document with a few 
float figures exported from inkscape as pdf, LyX 2.3.0alpha1 crashed 
after updating (saving as pdf) one of the figures.
I was running J. Matos' version from 
https://copr.fedorainfracloud.org/coprs/jamatos/lyx-next/

Will try to reproduce.





This is how I crashed LyX now:
I had my 3000 word document open, four figure floats in it: Fig1.pdf 
to Fig4.pdf.

"/bin/cp Fig4.pdf Fig3.pdf" was enough to crash it.





Thanks, I'll have a look.




Here is a trace.


Thread 1 "lyx" received signal SIGSEGV, Segmentation fault.
0x768612ef in QFileInfo::absoluteFilePath() const ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5

#0  0x768612ef in QFileInfo::absoluteFilePath() const ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#1  0x00d3a681 in lyx::support::FileName::removeFile (
this=this@entry=0x2fd0d68) at ../../../src/support/FileName.cpp:612
#2  0x00cfbcbe in lyx::graphics::Converter::Impl::converted (
this=0x2fd0d10, retval=0) at 
../../src/graphics/GraphicsConverter.cpp:205
#3  0x00cfc28f in std::_Mem_fn_base(lyx::graphics::Converter::Impl::*)(int, int), true>::operator()(lyx::graphics::Converter::Impl*, int&&, int&&) const 
(__object=, this=)

at /usr/include/c++/5/functional:600
#4  std::_Bind 
(lyx::graphics::Converter::Impl*, std::_Placeholder<1>, 
std::_Placeholder<2>)>::__call(std::tuple&&, std::_Index_tuple<0ul, 1ul, 2ul>) 
(__args=, this=)

at /usr/include/c++/5/functional:1074
#5  std::_Bind 
(lyx::graphics::Converter::Impl*, std::_Placeholder<1>, 
std::_Placeholder<2>)>::operator()(int&&, int&&) 
(this=)

at /usr/include/c++/5/functional:1133
#6 
boost::detail::function::void_function_obj_invoker2 
(lyx::graphics::Converter::Impl*, std::_Placeholder<1>, 
std::_Placeholder<2>)>, void, int, 
int>::invoke(boost::detail::function::function_buffer&, int, int) 
(function_obj_ptr=...,

a0=, a1=)
at ../../3rdparty/boost/boost/function/function_template.hpp:159
#7  0x00d535ed in boost::function2::operator() (
a1=, a0=, this=)
at ../../../3rdparty/boost/boost/function/function_template.hpp:771
#8 
boost::signals2::detail::call_with_tuple_args::m_invoke, 0u, 1u, int&, int&>(boost::function&, 
boost::signals2::detail::unsigned_meta_array<0u, 1u>, std::tuple const&, boost::enable_if::result_type>, void>::type*) const (

args=std::tuple containing = {...}, func=..., this=)
at 
../../../3rdparty/boost/boost/signals2/detail/variadic_slot_invoker.hpp:105

[...]
#18 lyx::support::ForkedProcess::emitSignal (this=this@entry=0x2db1bf0)
at ../../../src/support/ForkedCalls.cpp:116
#19 0x00d4f28e in 
lyx::support::ForkedCallsController::handleCompletedProcesses () at 
../../../src/support/ForkedCalls.cpp:662
#20 0x00a72ba9 in 
lyx::frontend::GuiApplication::handleRegularEvents (

this=)
at ../../../../src/frontends/qt4/GuiApplication.cpp:2680

Re: Bad Citation Bug in 2.3dev

[Richard Heck]

On 05/26/2017 12:40 PM, Richard Heck wrote:
> I am seeing the following bug: If I put, e.g., "pp.\ 22" into the text after 
> field in the citation dialog, I sometimes get as output: pp.\textbackslash{} 
> 22. This does not seem to happen with every
> citation, and I cannot figure out what is causing it to happen with the ones 
> it does. This does not happen in 2.2.x.

OK, I have found the cause of the odd behavior. Some of the citations
seem to have the "literal" flag set, and some do not. It seems to be the
new citations, added recently, that don't have it set, which makes
sense, in a way, since the old ones are converted to "literal true" by
lyx2lyx.

So, question: Shouldn't there be some way to set "literal true" as
default? Or shouldn't this setting be remembered? It's annoying to have
to set it every time.

Richard

Re: lyx-2.3.0alpha1-1 crash

[Guillaume MM]

Le 26/05/2017 à 23:15, PhilipPirrip a écrit :

On 05/26/2017 05:04 PM, PhilipPirrip wrote:


I think I caught this one too. I was working on a document with a few 
float figures exported from inkscape as pdf, LyX 2.3.0alpha1 crashed 
after updating (saving as pdf) one of the figures.
I was running J. Matos' version from 
https://copr.fedorainfracloud.org/coprs/jamatos/lyx-next/

Will try to reproduce.





This is how I crashed LyX now:
I had my 3000 word document open, four figure floats in it: Fig1.pdf to 
Fig4.pdf.

"/bin/cp Fig4.pdf Fig3.pdf" was enough to crash it.





Thanks, I'll have a look.


Guillaume

Re: lyx-2.3.0alpha1-1 crash

[PhilipPirrip]

On 05/26/2017 05:04 PM, PhilipPirrip wrote:


I think I caught this one too. I was working on a document with a few 
float figures exported from inkscape as pdf, LyX 2.3.0alpha1 crashed 
after updating (saving as pdf) one of the figures.
I was running J. Matos' version from 
https://copr.fedorainfracloud.org/coprs/jamatos/lyx-next/

Will try to reproduce.





This is how I crashed LyX now:
I had my 3000 word document open, four figure floats in it: Fig1.pdf to 
Fig4.pdf.

"/bin/cp Fig4.pdf Fig3.pdf" was enough to crash it.





lyx: SIGSEGV signal caught!
Sorry, you have found a bug in LyX, hope you have not lost any data.
Please read the bug-reporting instructions in 'Help->Introduction' and 
send us a bug report, if necessary. Thanks!

Bye.
Error: LyX crashed!

SIGSEGV signal caught!
Sorry, you have found a bug in LyX, hope you have not lost any data.
Please read the bug-reporting instructions in 'Help->Introduction' and 
send us a bug report, if necessary. Thanks!

Bye.
(  1) lyx-devel: lyx-devel(+0x5d5298) [0x55a4cb8fa298]
(  2) lyx-devel: lyx-devel(+0x639f9e) [0x55a4cb95ef9e]
(  3) lyx-devel: lyx-devel(+0x5d4560) [0x55a4cb8f9560]
(  4) lyx-devel: lyx-devel(+0x28b02b) [0x55a4cb5b002b]
(  5) /lib64/libc.so.6: /lib64/libc.so.6(+0x35990) [0x7f12b5379990]
(  6) /lib64/libQt5Core.so.5: QFileInfo::absoluteFilePath() const
(  7) lyx-devel: lyx-devel(+0x81760e) [0x55a4cbb3c60e]
(  8) lyx-devel: lyx-devel(+0x7f0848) [0x55a4cbb15848]
(  9) lyx-devel: lyx-devel(+0x82c5aa) [0x55a4cbb515aa]
( 10) lyx-devel: lyx-devel(+0x8288fa) [0x55a4cbb4d8fa]
( 11) /lib64/libQt5Core.so.5: QMetaObject::activate(QObject*, int, int, 
void**)

( 12) /lib64/libQt5Core.so.5: QTimer::timerEvent(QTimerEvent*)
( 13) /lib64/libQt5Core.so.5: QObject::event(QEvent*)
( 14) /lib64/libQt5Widgets.so.5: 
QApplicationPrivate::notify_helper(QObject*, QEvent*)

( 15) /lib64/libQt5Widgets.so.5: QApplication::notify(QObject*, QEvent*)
( 16) lyx-devel: lyx-devel(+0x5e647c) [0x55a4cb90b47c]
( 17) /lib64/libQt5Core.so.5: 
QCoreApplication::notifyInternal2(QObject*, QEvent*)

( 18) /lib64/libQt5Core.so.5: QTimerInfoList::activateTimers()
( 19) /lib64/libQt5Core.so.5: /lib64/libQt5Core.so.5(+0x294279) 
[0x7f12b668c279]
( 20) /lib64/libglib-2.0.so.0: 
/lib64/libglib-2.0.so.0(g_main_context_dispatch+0x162) [0x7f12b7a8be52]
( 21) /lib64/libglib-2.0.so.0: /lib64/libglib-2.0.so.0(+0x4a1d0) 
[0x7f12b7a8c1d0]
( 22) /lib64/libglib-2.0.so.0: 
/lib64/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7f12b7a8c27c]
( 23) /lib64/libQt5Core.so.5: 
QEventDispatcherGlib::processEvents(QFlags)
( 24) /lib64/libQt5Core.so.5: 
QEventLoop::exec(QFlags)

( 25) /lib64/libQt5Core.so.5: QCoreApplication::exec()
( 26) lyx-devel: lyx-devel(+0x293fbd) [0x55a4cb5b8fbd]
( 27) lyx-devel: lyx-devel(+0x124dd6) [0x55a4cb449dd6]
( 28) /lib64/libc.so.6: /lib64/libc.so.6(__libc_start_main+0xf1) 
[0x7f12b5364401]

( 29) lyx-devel: lyx-devel(+0x12ddca) [0x55a4cb452dca]
Aborted (core dumped)

Re: dashes and line-breaks (#10543)

[Scott Kostyshak]

On Fri, May 19, 2017 at 09:12:27AM -0400, Scott Kostyshak wrote:
> Günter has written a lot about what to do regarding em- and en-dashes.
> For more information, see:
> 
>   http://www.lyx.org/trac/ticket/10543
> 
> Does anyone else have feedback on what should be done on this for 2.3.0?

If no one has any feedback by Tuesday, then I suppose we should let
Günter do what he thinks is best on this topic.

Scott


signature.asc
Description: PGP signature

Bad Citation Bug in 2.3dev

[Richard Heck]

I am seeing the following bug: If I put, e.g., "pp.\ 22" into the text
after field in the citation dialog, I sometimes get as output:
pp.\textbackslash{} 22". This does not seem to happen with every
citation, and I cannot figure out what is causing it to happen with the
ones it does. This does not happen in 2.2.x.

Richard

Re: Update: polyglossia in 2.2.3

[Jürgen Spitzmüller]

Am Freitag, den 26.05.2017, 14:40 +0200 schrieb N. Andrew Walsh:
> Hi Jürgen,
> 
> thanks for getting back to me.
> 
> The relevant settings are as follows:
> 
> Language Package: [none]
> Command Start: \begin{$$lang}
> Command End: \end{$$lang}

OK, please create a bug report where you upload your example file and
give these informations. This is not the default setting, but it should
nevertheless work.

In the meantime, reverting to the defaults will probably fix the issue
for you. That is

Command Start: \selectlanguage{$$lang}
Command End: [nothing]

HTH
Jürgen

signature.asc
Description: This is a digitally signed message part

Re: Update: polyglossia in 2.2.3

[N. Andrew Walsh]

Hi Jürgen,

thanks for getting back to me.

The relevant settings are as follows:

Language Package: [none]
Command Start: \begin{$$lang}
Command End: \end{$$lang}

All four options below the "Default length unit" dropdown are checked, and
cursor movement is set to "logical."

It's possible that these are settings I put in earlier, when using
polyglossia, biblatex, biber, and xetex caused issues.

Anyway, thanks for the help.

Cheers,

Andrew

Re: Update: polyglossia in 2.2.3

[Jürgen Spitzmüller]

Am Freitag, den 26.05.2017, 13:50 +0200 schrieb N. Andrew Walsh:
> ach, whoops. I forgot to add that. Thanks for the reminder. Here
> attached is the (XeTeX-produced) LaTeX output from 2.2.3.

Thanks. Interesting. I see the problem, but cannot reproduce here. I
would have thought that this was fixed for LyX 2.2.3 (bug 9633). Do you
have any specific settings in Tools > Preferences > Language Settings >
Language? Particularly, what are your settings for

* Language Package

* Command start

* Command end

Best,
Jürgen

> 
> Cheers,
> 
> Andrew

signature.asc
Description: This is a digitally signed message part

Re: Update: polyglossia in 2.2.3

[N. Andrew Walsh]

Hi Jürgen,

ach, whoops. I forgot to add that. Thanks for the reminder. Here attached
is the (XeTeX-produced) LaTeX output from 2.2.3.

Cheers,

Andrew


polyglossiabreaker2.tex
Description: TeX document

Re: Update: polyglossia in 2.2.3

[Jürgen Spitzmüller]

Am Freitag, den 26.05.2017, 12:55 +0200 schrieb N. Andrew Walsh:
> thanks again. Yes, this is version 2.2.3, as released by gentoo Linux
> (if latest stable is already 2.2.4, then they seem to be a bit behind
> with their versions; or has 2.2.4 not yet been officially released?).

No. 2.2.4 will be the next release (we have just started to work on
that version).

> In any case, is this something for which I should submit a bug
> report?

If it's already fixed, this is not needed. However, I fail to see where
this would have been fixed since 2.2.3. So please can you post the
LaTeX export, as already asked?

Jürgen

signature.asc
Description: This is a digitally signed message part

Re: Update: polyglossia in 2.2.3

[N. Andrew Walsh]

Hi Jürgen,

thanks again. Yes, this is version 2.2.3, as released by gentoo Linux (if
latest stable is already 2.2.4, then they seem to be a bit behind with
their versions; or has 2.2.4 not yet been officially released?).

In any case, is this something for which I should submit a bug report?

Cheers,

Andrew

Re: Alt+A 0

[Scott Kostyshak]

On Fri, May 26, 2017 at 09:14:29AM +0200, Jürgen Spitzmüller wrote:
> Am Freitag, den 26.05.2017, 15:58 +1200 schrieb Andrew Parsloe:
> > The main reason for using a post argument is to avoid confusion with 
> > other optional arguments. The only real-life example I can give is
> > from 
> > my own work, the calculyx package 
> > (http://wiki.lyx.org/Examples/Calculyx).
> 
> Furthermore, post arguments are useful for commands with two mandatory
> arguments where you want to have the first to be what is entered in the
> main work area. For instance memoir's epigraph command
> (\epigraph{}{}). It would be rather odd if the source
> would be in the main work area and you'd would have to type the text in
> an inset. Actually, all of the current usages of post in the LyX
> distribution are of this kind.

Thanks for the explanations, Jürgen and Andrew.

Scott


signature.asc
Description: PGP signature

Re: Update: polyglossia in 2.2.3

[Jürgen Spitzmüller]

Am Freitag, den 26.05.2017, 12:23 +0200 schrieb N. Andrew Walsh:
> Hi Jürgen,
> 
> thanks for getting back to me. I'm attaching two files: the MWE
> polyglossiabreaker2.lyx, and the necessary bibtex file. Put both in
> the same directory, and it should work. 

Thanks.

> Or rather, the file will compile with 2.2.2, but not with 2.2.3
> (giving back the error about deleting a closing bracket as previously
> described).

You mean 2.2.3 not 2.3alpha, right? In any case, the file compiles fine
for me both with recent stable (what will become 2.2.4) and master
(what will become 2.3.0).

Could you also post the LaTeX export (to LaTeX (XeTeX)) of this MWE?

Jürgen

> 
> Thanks for your help,
> 
> Andrew

signature.asc
Description: This is a digitally signed message part

Re: Update: polyglossia in 2.2.3

[N. Andrew Walsh]

Hi Jürgen,

thanks for getting back to me. I'm attaching two files: the MWE
polyglossiabreaker2.lyx, and the necessary bibtex file. Put both in the
same directory, and it should work.

Or rather, the file will compile with 2.2.2, but not with 2.2.3 (giving
back the error about deleting a closing bracket as previously described).

Thanks for your help,

Andrew


polyglossiabreaker2.lyx
Description: application/lyx
@Book{butcher1917poetics,
  Title= {The {P}oetics of {A}ristotle},
  Author   = {Butcher, Samuel H.},
  Publisher= {Macmillan},
  Year = {1917},

  Address  = {London}
}

Re: \noun, \emph or any other text style change of a \href inset

[Jürgen Spitzmüller]

Am Donnerstag, den 25.05.2017, 14:42 -0400 schrieb PhilipPirrip:
> This used to work fine until LyX 2.3:
> 
> insert a hyperlink
> select, toggle noun
> 
> you'll get
> \noun{}\href{http://www.lyx.org}{lyx}
> 
> instead of
> \noun{\href{http://www.lyx.org}{lyx}}
> 
> 
> Is this intended behavior?

Fixed by JMarc in recent master (as of 0516af0c99e33).

Jürgen


signature.asc
Description: This is a digitally signed message part

Re: Alt+A 0

[Andrew Parsloe]

On 26/05/2017 7:40 p.m., Jürgen Spitzmüller wrote:

Am Donnerstag, den 25.05.2017, 12:51 +1200 schrieb Andrew Parsloe:

Given the arrangement of keys on a
keyboard, there seems a certain naturalness to assigning Alt+A 0 to
the
first post argument.


Done.

Jürgen


Thank you Jürgen!

Andrew

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

Re: No toolbar menu and no toolbar icon-size in menu

[racoon]

On 26.05.2017 09:35, racoon wrote:

On 25.05.2017 02:37, Andrew Parsloe wrote:

On 25/05/2017 11:10 a.m., Guillaume MM wrote:

Le 24/05/2017 à 08:30, racoon a écrit :

On 24.05.2017 08:21, racoon wrote:

On 22.05.2017 18:55, racoon wrote:

With LyX 2.2.3 on Win7 I have no toolbar menu (just "No Action
Defined!") and no toolbar icon-size in menu. Can someone else verify?


On alpha1-1 the toolbar menu works as expected but in the normal menu
the icon size is missing.


Same in master. I think the patch in question is coming from here
http://www.lyx.org/trac/ticket/10428.




It works fine here. Uwe, Andrew, can you reproduce on Windows?


I wasn't sure exactly what Daniel was referring to which is why I 
haven't answered, but if it is as in the attached png, then my system, 
alpha1-1 on windows 7, does display it.


Thanks for testing. There must be something wrong with my custom inc 
files...


So the problem was that I had old modified stdcontext.inc and 
stdmenus.inc files in my user directory. Might be a good idea for next 
time to have in mind that changes to the menu can break custom 
configured menus.


One work around in this case could have been

1) to show a default context menu on the toolbar in case the new

Menu "context-toolbars"

is not defined, and

2) to put the icon-sizes directly in the "Toolbars" menu so that the old

Menu "toolbars"
Toolbars
End

still shows everything correctly. But maybe I am the only one who tweaks 
his menus. :)


Daniel

Re: Alt+A 0

[Jürgen Spitzmüller]

Am Donnerstag, den 25.05.2017, 12:51 +1200 schrieb Andrew Parsloe:
> Given the arrangement of keys on a 
> keyboard, there seems a certain naturalness to assigning Alt+A 0 to
> the 
> first post argument.

Done.

Jürgen

signature.asc
Description: This is a digitally signed message part

Re: No toolbar menu and no toolbar icon-size in menu

[racoon]

On 25.05.2017 02:37, Andrew Parsloe wrote:

On 25/05/2017 11:10 a.m., Guillaume MM wrote:

Le 24/05/2017 à 08:30, racoon a écrit :

On 24.05.2017 08:21, racoon wrote:

On 22.05.2017 18:55, racoon wrote:

With LyX 2.2.3 on Win7 I have no toolbar menu (just "No Action
Defined!") and no toolbar icon-size in menu. Can someone else verify?


On alpha1-1 the toolbar menu works as expected but in the normal menu
the icon size is missing.


Same in master. I think the patch in question is coming from here
http://www.lyx.org/trac/ticket/10428.




It works fine here. Uwe, Andrew, can you reproduce on Windows?


I wasn't sure exactly what Daniel was referring to which is why I 
haven't answered, but if it is as in the attached png, then my system, 
alpha1-1 on windows 7, does display it.


Thanks for testing. There must be something wrong with my custom inc 
files...


Daniel

Re: Alt+A 0

[Jürgen Spitzmüller]

Am Freitag, den 26.05.2017, 15:58 +1200 schrieb Andrew Parsloe:
> The main reason for using a post argument is to avoid confusion with 
> other optional arguments. The only real-life example I can give is
> from 
> my own work, the calculyx package 
> (http://wiki.lyx.org/Examples/Calculyx).

Furthermore, post arguments are useful for commands with two mandatory
arguments where you want to have the first to be what is entered in the
main work area. For instance memoir's epigraph command
(\epigraph{}{}). It would be rather odd if the source
would be in the main work area and you'd would have to type the text in
an inset. Actually, all of the current usages of post in the LyX
distribution are of this kind.

Jürgen

signature.asc
Description: This is a digitally signed message part

Re: Insert Citation Dialog Kudos

[Jürgen Spitzmüller]

Am Donnerstag, den 25.05.2017, 21:58 -0600 schrieb Joel Kulesza:
> After some time working with it, my thanks to Jürgen for reworking
> the Insert -> Citation dialog.  I find this **much** more pleasant to
> use than previously.

Thank you. Glad to hear that.

Jürgen

> 
> - Joel

signature.asc
Description: This is a digitally signed message part