Re: SIGSEGV error

2017-06-21 Thread Jean-Marc Lasgouttes

Le 21/06/17 à 22:21, Christos Makridis a écrit :

Perfect, looking at the source pane helped diagnose the problem -- an
imbalanced space from MS word -- great suggestion! I did not know that
source pane even existed before.

(I would have added more details, like an example, but I wasn't sure
what could be causing it before. I am using the latest version of lyx on
a windows machine FYI.)

Thank you for teaching me this new trick!


I am happy for you, obviously, but nevertheless LyX should not crash in 
this situation. Can you send us an example file that exhibits the problem?


JMarc


Re: SIGSEGV error

2017-06-21 Thread Christos Makridis
Perfect, looking at the source pane helped diagnose the problem -- an
imbalanced space from MS word -- great suggestion! I did not know that
source pane even existed before.

(I would have added more details, like an example, but I wasn't sure what
could be causing it before. I am using the latest version of lyx on a
windows machine FYI.)

Thank you for teaching me this new trick!


Re: SIGSEGV error

2017-06-21 Thread Paul A. Rubin

On 06/21/2017 03:42 PM, Christos Makridis wrote:

Hey everyone,

I've googled around and there doesn't seem to be a consensus about the 
source of the problem -- some just suggest making sure the lyx is the 
latest version.


I've attached the error as a screen shot. But, the problem seems to be 
rooted in some text that I copy/pasted from a word doc. The formatting 
was different, so I first pasted into another word doc with no special 
formatting, and then into lyx. But when I try to pdf the document, it 
crashes. (Before, it would crash when I highlighted the pasted in 
text.) It seems to be "normal" now that I took that part of the text out.


Any ideas what is going wrong?

--
Christos Makridis
Ph.D. Candidate, Stanford University
Department of Management Science & Engineering
Department of Economics
www.christosmakridis.com 
A first thought is to look at the LyX document the document with the 
offending text pasted in, and use View > Source Pane to get a look at 
what the source text going to LaTeX looks like. That might let you spot 
some character that looks harmless in the GUI (and in Word) but actually 
is the Unicode character for the apocalypse or something.


Failing that, could you post a minimal example that contains just enough 
text to cause LyX to blow up at your end?


Also, it might help to know what operating system you use, what LaTeX 
system (TeXLive, MikTeX, ...) and what version/build of LyX (Help > 
About LyX).


Cheers,
Paul



SIGSEGV error

2017-06-21 Thread Christos Makridis
Hey everyone,

I've googled around and there doesn't seem to be a consensus about the
source of the problem -- some just suggest making sure the lyx is the
latest version.

I've attached the error as a screen shot. But, the problem seems to be
rooted in some text that I copy/pasted from a word doc. The formatting was
different, so I first pasted into another word doc with no special
formatting, and then into lyx. But when I try to pdf the document, it
crashes. (Before, it would crash when I highlighted the pasted in text.) It
seems to be "normal" now that I took that part of the text out.

Any ideas what is going wrong?

-- 
Christos Makridis
Ph.D. Candidate, Stanford University
Department of Management Science & Engineering
Department of Economics
www.christosmakridis.com


Re: Is "Citation Style" menu tweakable?

2017-06-21 Thread David Pesetsky
Thanks for your continued help!  I have solved the problem, with the help of 
(the presuppositions of) your questions and this: 
https://tex.stackexchange.com/questions/56525/natbib-setcitestyle-causes-undefined-control-sequence-error?rq=1.

Early in my exploring of Lyx a few weeks ago, I took advantage of the 
information offered by Maria Gouskova, who is in my field, at 
https://www.gouskova.com/resources/.  That includes a link to her texmf 
directory with field-specific stuff in it, with an invitation to copy that into 
one's own texmf directory, which I did.  That turns out to have included an 
out-of-date version of natbib.sty, which was the cause of my error messsages.  
Removing it solved the problem.

Thanks again,
David

On Jun 20, 2017, at 11:23 PM, Richard Heck 
> wrote:

On 06/20/2017 06:25 PM, David Pesetsky wrote:
Thank you for your detailed reply (and hello)!  Your suggestion to add "comma" 
to [...]Class Options>Custom works very well, thank you!

But no matter what I put after \setcitestyle (or where I locate the command in 
the document -- preamble, body), I get an error message from Lyx — for example:

\setcitestyle
{notesep={: }}
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.

It's not worth chasing down this problem to the ends of the earth, but if you 
have any troubleshooting suggestions, I'd be happy to try them.

Very odd. The \setcitestyle command is defined by natbib.sty, and you said you 
were using natbib, yes?  (It did not exist before version 8 of natbib, but that 
was about a decade ago.) What OS are you using? Do you know what LaTeX 
distribution you have? Actually, maybe a better questin is: What document class 
are you using?

If you could produce as small a file as possible that causes this to happen and 
post that, then it will help debug the issue.

Richard


--
David Pesetsky [pese...@mit.edu]
Head, Department of Linguistics and Philosophy
32-D818 Massachusetts Institute of Technology
77 Massachusetts Avenue
Cambridge, MA 02139 USA
(617) 253-0957 office   (617) 253-5017 fax
http://web.mit.edu/linguistics/www/pesetsky.home.html