Re: bug(?): strange behavior after ctrl-shift-left

[Juergen Spitzmueller]

Curtis Osterhoudt wrote:
 Ctrl-shift-left immediately crashes LyX (1.4.1, on a Debian machine) for
 me... so does ctrl-shift-up. I get the
 lyx: SIGSEGV signal caught [...] Sorry, you have found a bug in LyX.
 message, too.

I cannot reproduce this either (neither the cases described in the other 
mails).

Can someone of you provide a backtrace?

Jürgen

Re: bug(?): strange behavior after ctrl-shift-left

[Jose' Matos]

On Wednesday 12 July 2006 08:45, Juergen Spitzmueller wrote:

 I cannot reproduce this either (neither the cases described in the other
 mails).

  I have finally succeeded with 1.4.2svn

  I have inserted two lines with one word and pressed enter to get a third 
(empty) line.

  While in the last empty line I pressed Ctrl-Shift-Left and... I got a crash.

 Can someone of you provide a backtrace?

  Follows attached. The culprit here seems to be the empty line. I have been 
working with lyx daily and I never noticed this because I do not usually do 
this on an empty line.

 Jürgen

-- 
José Abílio
(gdb) bt
#0  0x080b3206 in ParagraphParameters::depth (this=0x3c) at 
ParagraphParameters.C:75
#1  0x081ebaa6 in (anonymous namespace)::changeDepthAllowed 
(type=LyXText::INC_DEPTH, [EMAIL PROTECTED], max_depth=0) at text2.C:373
#2  0x081ebd06 in LyXText::changeDepthAllowed (this=0xa75f71c, [EMAIL 
PROTECTED], type=LyXText::INC_DEPTH) at text2.C:393
#3  0x081f08c4 in LyXText::getStatus (this=0xa75f71c, [EMAIL PROTECTED], [EMAIL 
PROTECTED], [EMAIL PROTECTED]) at text3.C:1578
#4  0x082df899 in InsetText::getStatus (this=0xa75f6f4, [EMAIL PROTECTED], 
[EMAIL PROTECTED], [EMAIL PROTECTED]) at insettext.C:263
#5  0x08151637 in (anonymous namespace)::getStatus ([EMAIL PROTECTED], [EMAIL 
PROTECTED], [EMAIL PROTECTED]) at lyxfunc.C:169
#6  0x08154bb5 in LyXFunc::getStatus (this=0xa642340, [EMAIL PROTECTED]) at 
lyxfunc.C:616
#7  0x083be9cb in lyx::frontend::QLToolbar::update (this=0xa699768) at 
QLToolbar.C:231
#8  0x0830a9df in Toolbars::update (this=0xa641548) at Toolbars.C:150
#9  0x0830ae84 in Toolbars::update (this=0xa641548, in_math=false, 
in_table=false) at Toolbars.C:67
#10 0x08307d3a in LyXView::updateToolbars (this=0xa657898) at LyXView.C:116
#11 0x08158305 in LyXFunc::sendDispatchMessage (this=0xa642340, [EMAIL 
PROTECTED], [EMAIL PROTECTED]) at lyxfunc.C:1625
#12 0x0816080e in LyXFunc::dispatch (this=0xa642340, [EMAIL PROTECTED]) at 
lyxfunc.C:1612
#13 0x08161951 in LyXFunc::processKeySym (this=0xa642340, [EMAIL PROTECTED], 
state=5) at lyxfunc.C:328
#14 0x0806529d in BufferView::Pimpl::workAreaKeyPress (this=0xa65f290, [EMAIL 
PROTECTED], state=5) at BufferView_pimpl.C:568
#15 0x08074258 in 
boost::detail::function::void_function_obj_invoker2boost::_bi::bind_tvoid, 
boost::_mfi::mf2void, BufferView::Pimpl, boost::shared_ptrLyXKeySym, 
key_modifier::state, boost::_bi::list3boost::_bi::valueBufferView::Pimpl*, 
boost::arg1, boost::arg2  , void, boost::shared_ptrLyXKeySym, 
key_modifier::state::invoke (function_obj_ptr=
{obj_ptr = 0xa663c38, const_obj_ptr = 0xa663c38, func_ptr = 0xa663c38, data = 
8}, [EMAIL PROTECTED], a1=5) at ../boost/boost/bind/mem_fn_template.hpp:252
#16 0x08466021 in boost::function2void, boost::shared_ptrLyXKeySym, 
key_modifier::state, std::allocatorvoid ::operator() (this=0xa663c24, [EMAIL 
PROTECTED], a1=5)
at ../../../boost/boost/function/function_template.hpp:581
#17 0x0846712a in 
boost::operator++boost::signals::detail::slot_call_iteratorboost::signals::detail::call_bound2void::callerboost::shared_ptrLyXKeySym,
 key_modifier::state, boost::functionvoid ()(boost::shared_ptrLyXKeySym, 
key_modifier::state), std::allocatorvoid  , 
boost::signals::detail::named_slot_map_iterator, 
boost::signals::detail::unusable, boost::single_pass_traversal_tag, 
boost::signals::detail::unusable const, int ([EMAIL PROTECTED]) at 
../../../boost/boost/signals/signal_template.hpp:119
#18 0x0846785d in boost::signal2void, boost::shared_ptrLyXKeySym, 
key_modifier::state, boost::last_valuevoid, int, std::lessint, 
boost::functionvoid ()(boost::shared_ptrLyXKeySym, key_modifier::state), 
std::allocatorvoid  ::operator() (this=0xa65f6f4, [EMAIL PROTECTED], a2=5) 
at ../../../boost/boost/last_value.hpp:43
#19 0x084644d6 in QContentPane::keyeventTimeout (this=0xa661778) at 
QContentPane.C:292
#20 0x0846ebaa in QContentPane::qt_invoke (this=0xa661778, _id=48, 
_o=0xbf81cec8) at QContentPane_moc.C:91
#21 0x00a0735a in QObject::activate_signal () from 
/usr/lib/qt-3.3/lib/libqt-mt.so.3
#22 0x00a07ecd in QObject::activate_signal () from 
/usr/lib/qt-3.3/lib/libqt-mt.so.3
#23 0x00d93b69 in QTimer::timeout () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#24 0x00a2e9ff in QTimer::event () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#25 0x0099e82b in QApplication::internalNotify () from 
/usr/lib/qt-3.3/lib/libqt-mt.so.3
#26 0x0099fc79 in QApplication::notify () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#27 0x00992632 in QEventLoop::activateTimers () from 
/usr/lib/qt-3.3/lib/libqt-mt.so.3
#28 0x009453ef in QEventLoop::processEvents () from 
/usr/lib/qt-3.3/lib/libqt-mt.so.3
#29 0x009b7cd0 in QEventLoop::enterLoop () from 
/usr/lib/qt-3.3/lib/libqt-mt.so.3
#30 0x009b7b96 in QEventLoop::exec () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#31 0x0099e33f in QApplication::exec () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#32 0x0837aeb5 in lyx_gui::start ([EMAIL PROTECTED], [EMAIL PROTECTED]) at 
lyx_gui.C:253
#33 0x08143aff in 

Re: bug(?): strange behavior after ctrl-shift-left

[Jose' Matos]

On Wednesday 12 July 2006 01:29, Steve Harris wrote:

 Good day José,

  Good day,

 After reading your post, I tested again and this is
 not fixed in 1.4.2. It isn't much of a bug.

  After several trials I succeeded into reproducing the bug, even for 
1.4.2.svn.

 This is an example line.

 {If I type in ctrl-shift-leftarrow down here, start of a
 new paragraph, and I have entered no text, blank in other
 words, then the blue highlight reverts back to the end of

 This is an example line.(-- begins blue highlight)

 and if you type in it, then it will segfault lyx. If you have
 typed more than one paragraph with words it works normally.}

 But again, if you have typed three paragraphs and then
 type ctrl-shift-leftarrow at the beginning of a new
 paragraph which has no words (blank) then it will segfault.

  I noticed that too.

 It means that if you end a paragraph by using enter, then
 you can't change your mind with ctrl-shift-leftarrow and
 go back to the previous paragraph and type a little more
 before you start your new paragraph. You can go back with
 your mouse to the end of the previous paragraph and
 ctrl-shift-leftarrow will work normally. I am something
 of a keyboard purist, but I normally use Edit/Undo to
 reverse my last step; but Alt-e-u will Undo, take you
 back to the end of the previous paragraph (reverses enter)
 and then ctrl-shift-leftarrow will work as expected.

  Sometimes it crashes immediately.

 It may have seemed if I wrote in too much detail. But you
 reported it worked on Linux and I have the most excellent
 FC4, and it malfunctions just as reported:

 This is the first paragraph. enter

 begins the second paragraph = blank: - ctrl-shift-leftarrow

 goes back to the end of the first paragraph and freezes the
 machine. Shortly afterwards it exited with the same error
 message that I reported for Cygwin Lyx 1.4.1 and it segfaults
 in Joost's windows 1.4.2 also, but the error screen exits too
 fast to see the text. This message is from FC4/Cygwin Lyx1.4.1.

 --

 $ lyx
 LyX: Attempting to save document newfile1.lyx
   /cygdrive/c/home/newfile1.lyx.emergency
Save seems successful. Phew.

 lyx: SIGSEGV signal caught
 Sorry, you have found a bug in LyX. Please read the
 bug-reporting instructions in Help-Introduction and
 send us a bug report, if necessary. Thanks !
 Bye.
 Aborted (core dumped)

 

 Is the upgrade to FC5 *strongly recommended*?

  Nope.

 Stephen

-- 
José Abílio

Re: bug(?): strange behavior after ctrl-shift-left

[Juergen Spitzmueller]

Jose' Matos wrote:
 I have finally succeeded with 1.4.2svn

   I have inserted two lines with one word and pressed enter to get a third
 (empty) line.

   While in the last empty line I pressed Ctrl-Shift-Left and... I got a
 crash.

I see. Most certainly DEPM interferes here and we end up with an invalid 
cursor (anchor).

Attached is a patch that fixes the crash for me, but I'm not sure it produces 
the behaviour we want (delete the empty paragraph, which is inconsistent to 
what LFUN_LEFTSEL does in this case).

However, I have no idea how to get DEPM *not* to trigger in this case.

Please test.

Jürgen
Index: src/text2.C
===
--- src/text2.C	(Revision 14351)
+++ src/text2.C	(Arbeitskopie)
@@ -1274,6 +1274,8 @@ bool LyXText::deleteEmptyParagraphMechan
 cur.resetAnchor();
 			}
 		}
+		if (cur.anchor().pit() == old.pit())
+			cur.resetAnchor();
 		updateCounters(old.buffer());
 		return true;
 	}

[PATCH] Re: bug(?): strange behavior after ctrl-shift-left

[Juergen Spitzmueller]

Juergen Spitzmueller wrote:
 Attached is a patch that fixes the crash for me, but I'm not sure it
 produces the behaviour we want (delete the empty paragraph, which is
 inconsistent to what LFUN_LEFTSEL does in this case).

attached is the proper fix, IMO.
selHandle has to be used, because it makes sure that the selection is properly 
set, which was not the case without that method. That's why DEPM was 
erroneously triggered.

This patch also fixes bug 2119 (Selection of text via keyboard sometimes 
fails) and bug 2259 (screen-up/down-select do not work).

Too late for 1.4.2?

Jürgen
Index: src/text3.C
===
--- src/text3.C	(Revision 14351)
+++ src/text3.C	(Arbeitskopie)
@@ -396,8 +396,7 @@ void LyXText::dispatch(LCursor  cur, Fu
 
 	case LFUN_BEGINNINGBUFSEL:
 		if (cur.depth() == 1) {
-			if (!cur.selection())
-cur.resetAnchor();
+			cur.selHandle(cmd.action == LFUN_BEGINNINGBUFSEL);
 			needsUpdate = cursorTop(cur);
 			finishChange(cur, true);
 		} else {
@@ -418,8 +417,7 @@ void LyXText::dispatch(LCursor  cur, Fu
 
 	case LFUN_ENDBUFSEL:
 		if (cur.depth() == 1) {
-			if (!cur.selection())
-cur.resetAnchor();
+			cur.selHandle(cmd.action == LFUN_ENDBUFSEL);
 			needsUpdate = cursorBottom(cur);
 			finishChange(cur, true);
 		} else {
@@ -496,8 +494,7 @@ void LyXText::dispatch(LCursor  cur, Fu
 		break;
 
 	case LFUN_UP_PARAGRAPHSEL:
-		if (!cur.selection())
-			cur.resetAnchor();
+		cur.selHandle(cmd.action == LFUN_UP_PARAGRAPHSEL);
 		cursorUpParagraph(cur);
 		finishChange(cur, true);
 		break;
@@ -510,47 +507,41 @@ void LyXText::dispatch(LCursor  cur, Fu
 		break;
 
 	case LFUN_DOWN_PARAGRAPHSEL:
-		if (!cur.selection())
-			cur.resetAnchor();
+		cur.selHandle(cmd.action == LFUN_DOWN_PARAGRAPHSEL);
 		cursorDownParagraph(cur);
 		finishChange(cur, true);
 		break;
 
 	case LFUN_PRIORSEL:
 		update(cur);
-		if (!cur.selection())
-			cur.resetAnchor();
+		cur.selHandle(cmd.action == LFUN_PRIORSEL);
 		needsUpdate = cursorPrevious(cur);
 		finishChange(cur, true);
 		break;
 
 	case LFUN_NEXTSEL:
 		update(cur);
-		if (!cur.selection())
-			cur.resetAnchor();
+		cur.selHandle(cmd.action == LFUN_NEXTSEL);
 		needsUpdate = cursorNext(cur);
 		finishChange(cur, true);
 		break;
 
 	case LFUN_HOMESEL:
 		update(cur);
-		if (!cur.selection())
-			cur.resetAnchor();
+		cur.selHandle(cmd.action == LFUN_HOMESEL);
 		needsUpdate = cursorHome(cur);
 		finishChange(cur, true);
 		break;
 
 	case LFUN_ENDSEL:
 		update(cur);
-		if (!cur.selection())
-			cur.resetAnchor();
+		cur.selHandle(cmd.action == LFUN_ENDSEL);
 		needsUpdate = cursorEnd(cur);
 		finishChange(cur, true);
 		break;
 
 	case LFUN_WORDRIGHTSEL:
-		if (!cur.selection())
-			cur.resetAnchor();
+		cur.selHandle(cmd.action == LFUN_WORDRIGHTSEL);
 		if (isRTL(cur.paragraph()))
 			cursorLeftOneWord(cur);
 		else
@@ -559,8 +550,7 @@ void LyXText::dispatch(LCursor  cur, Fu
 		break;
 
 	case LFUN_WORDLEFTSEL:
-		if (!cur.selection())
-			cur.resetAnchor();
+		cur.selHandle(cmd.action == LFUN_WORDLEFTSEL);
 		if (isRTL(cur.paragraph()))
 			cursorRightOneWord(cur);
 		else

Re: bug(?): strange behavior after ctrl-shift-left

[Juergen Spitzmueller]

Curtis Osterhoudt wrote:
 Ctrl-shift-left immediately crashes LyX (1.4.1, on a Debian machine) for
 me... so does ctrl-shift-up. I get the
 lyx: SIGSEGV signal caught [...] Sorry, you have found a bug in LyX.
 message, too.

I cannot reproduce this either (neither the cases described in the other 
mails).

Can someone of you provide a backtrace?

Jürgen

Re: bug(?): strange behavior after ctrl-shift-left

[Jose' Matos]

On Wednesday 12 July 2006 08:45, Juergen Spitzmueller wrote:

 I cannot reproduce this either (neither the cases described in the other
 mails).

  I have finally succeeded with 1.4.2svn

  I have inserted two lines with one word and pressed enter to get a third 
(empty) line.

  While in the last empty line I pressed Ctrl-Shift-Left and... I got a crash.

 Can someone of you provide a backtrace?

  Follows attached. The culprit here seems to be the empty line. I have been 
working with lyx daily and I never noticed this because I do not usually do 
this on an empty line.

 Jürgen

-- 
José Abílio
(gdb) bt
#0  0x080b3206 in ParagraphParameters::depth (this=0x3c) at 
ParagraphParameters.C:75
#1  0x081ebaa6 in (anonymous namespace)::changeDepthAllowed 
(type=LyXText::INC_DEPTH, [EMAIL PROTECTED], max_depth=0) at text2.C:373
#2  0x081ebd06 in LyXText::changeDepthAllowed (this=0xa75f71c, [EMAIL 
PROTECTED], type=LyXText::INC_DEPTH) at text2.C:393
#3  0x081f08c4 in LyXText::getStatus (this=0xa75f71c, [EMAIL PROTECTED], [EMAIL 
PROTECTED], [EMAIL PROTECTED]) at text3.C:1578
#4  0x082df899 in InsetText::getStatus (this=0xa75f6f4, [EMAIL PROTECTED], 
[EMAIL PROTECTED], [EMAIL PROTECTED]) at insettext.C:263
#5  0x08151637 in (anonymous namespace)::getStatus ([EMAIL PROTECTED], [EMAIL 
PROTECTED], [EMAIL PROTECTED]) at lyxfunc.C:169
#6  0x08154bb5 in LyXFunc::getStatus (this=0xa642340, [EMAIL PROTECTED]) at 
lyxfunc.C:616
#7  0x083be9cb in lyx::frontend::QLToolbar::update (this=0xa699768) at 
QLToolbar.C:231
#8  0x0830a9df in Toolbars::update (this=0xa641548) at Toolbars.C:150
#9  0x0830ae84 in Toolbars::update (this=0xa641548, in_math=false, 
in_table=false) at Toolbars.C:67
#10 0x08307d3a in LyXView::updateToolbars (this=0xa657898) at LyXView.C:116
#11 0x08158305 in LyXFunc::sendDispatchMessage (this=0xa642340, [EMAIL 
PROTECTED], [EMAIL PROTECTED]) at lyxfunc.C:1625
#12 0x0816080e in LyXFunc::dispatch (this=0xa642340, [EMAIL PROTECTED]) at 
lyxfunc.C:1612
#13 0x08161951 in LyXFunc::processKeySym (this=0xa642340, [EMAIL PROTECTED], 
state=5) at lyxfunc.C:328
#14 0x0806529d in BufferView::Pimpl::workAreaKeyPress (this=0xa65f290, [EMAIL 
PROTECTED], state=5) at BufferView_pimpl.C:568
#15 0x08074258 in 
boost::detail::function::void_function_obj_invoker2boost::_bi::bind_tvoid, 
boost::_mfi::mf2void, BufferView::Pimpl, boost::shared_ptrLyXKeySym, 
key_modifier::state, boost::_bi::list3boost::_bi::valueBufferView::Pimpl*, 
boost::arg1, boost::arg2  , void, boost::shared_ptrLyXKeySym, 
key_modifier::state::invoke (function_obj_ptr=
{obj_ptr = 0xa663c38, const_obj_ptr = 0xa663c38, func_ptr = 0xa663c38, data = 
8}, [EMAIL PROTECTED], a1=5) at ../boost/boost/bind/mem_fn_template.hpp:252
#16 0x08466021 in boost::function2void, boost::shared_ptrLyXKeySym, 
key_modifier::state, std::allocatorvoid ::operator() (this=0xa663c24, [EMAIL 
PROTECTED], a1=5)
at ../../../boost/boost/function/function_template.hpp:581
#17 0x0846712a in 
boost::operator++boost::signals::detail::slot_call_iteratorboost::signals::detail::call_bound2void::callerboost::shared_ptrLyXKeySym,
 key_modifier::state, boost::functionvoid ()(boost::shared_ptrLyXKeySym, 
key_modifier::state), std::allocatorvoid  , 
boost::signals::detail::named_slot_map_iterator, 
boost::signals::detail::unusable, boost::single_pass_traversal_tag, 
boost::signals::detail::unusable const, int ([EMAIL PROTECTED]) at 
../../../boost/boost/signals/signal_template.hpp:119
#18 0x0846785d in boost::signal2void, boost::shared_ptrLyXKeySym, 
key_modifier::state, boost::last_valuevoid, int, std::lessint, 
boost::functionvoid ()(boost::shared_ptrLyXKeySym, key_modifier::state), 
std::allocatorvoid  ::operator() (this=0xa65f6f4, [EMAIL PROTECTED], a2=5) 
at ../../../boost/boost/last_value.hpp:43
#19 0x084644d6 in QContentPane::keyeventTimeout (this=0xa661778) at 
QContentPane.C:292
#20 0x0846ebaa in QContentPane::qt_invoke (this=0xa661778, _id=48, 
_o=0xbf81cec8) at QContentPane_moc.C:91
#21 0x00a0735a in QObject::activate_signal () from 
/usr/lib/qt-3.3/lib/libqt-mt.so.3
#22 0x00a07ecd in QObject::activate_signal () from 
/usr/lib/qt-3.3/lib/libqt-mt.so.3
#23 0x00d93b69 in QTimer::timeout () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#24 0x00a2e9ff in QTimer::event () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#25 0x0099e82b in QApplication::internalNotify () from 
/usr/lib/qt-3.3/lib/libqt-mt.so.3
#26 0x0099fc79 in QApplication::notify () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#27 0x00992632 in QEventLoop::activateTimers () from 
/usr/lib/qt-3.3/lib/libqt-mt.so.3
#28 0x009453ef in QEventLoop::processEvents () from 
/usr/lib/qt-3.3/lib/libqt-mt.so.3
#29 0x009b7cd0 in QEventLoop::enterLoop () from 
/usr/lib/qt-3.3/lib/libqt-mt.so.3
#30 0x009b7b96 in QEventLoop::exec () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#31 0x0099e33f in QApplication::exec () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#32 0x0837aeb5 in lyx_gui::start ([EMAIL PROTECTED], [EMAIL PROTECTED]) at 
lyx_gui.C:253
#33 0x08143aff in 

Re: bug(?): strange behavior after ctrl-shift-left

[Jose' Matos]

On Wednesday 12 July 2006 01:29, Steve Harris wrote:

 Good day José,

  Good day,

 After reading your post, I tested again and this is
 not fixed in 1.4.2. It isn't much of a bug.

  After several trials I succeeded into reproducing the bug, even for 
1.4.2.svn.

 This is an example line.

 {If I type in ctrl-shift-leftarrow down here, start of a
 new paragraph, and I have entered no text, blank in other
 words, then the blue highlight reverts back to the end of

 This is an example line.(-- begins blue highlight)

 and if you type in it, then it will segfault lyx. If you have
 typed more than one paragraph with words it works normally.}

 But again, if you have typed three paragraphs and then
 type ctrl-shift-leftarrow at the beginning of a new
 paragraph which has no words (blank) then it will segfault.

  I noticed that too.

 It means that if you end a paragraph by using enter, then
 you can't change your mind with ctrl-shift-leftarrow and
 go back to the previous paragraph and type a little more
 before you start your new paragraph. You can go back with
 your mouse to the end of the previous paragraph and
 ctrl-shift-leftarrow will work normally. I am something
 of a keyboard purist, but I normally use Edit/Undo to
 reverse my last step; but Alt-e-u will Undo, take you
 back to the end of the previous paragraph (reverses enter)
 and then ctrl-shift-leftarrow will work as expected.

  Sometimes it crashes immediately.

 It may have seemed if I wrote in too much detail. But you
 reported it worked on Linux and I have the most excellent
 FC4, and it malfunctions just as reported:

 This is the first paragraph. enter

 begins the second paragraph = blank: - ctrl-shift-leftarrow

 goes back to the end of the first paragraph and freezes the
 machine. Shortly afterwards it exited with the same error
 message that I reported for Cygwin Lyx 1.4.1 and it segfaults
 in Joost's windows 1.4.2 also, but the error screen exits too
 fast to see the text. This message is from FC4/Cygwin Lyx1.4.1.

 --

 $ lyx
 LyX: Attempting to save document newfile1.lyx
   /cygdrive/c/home/newfile1.lyx.emergency
Save seems successful. Phew.

 lyx: SIGSEGV signal caught
 Sorry, you have found a bug in LyX. Please read the
 bug-reporting instructions in Help-Introduction and
 send us a bug report, if necessary. Thanks !
 Bye.
 Aborted (core dumped)

 

 Is the upgrade to FC5 *strongly recommended*?

  Nope.

 Stephen

-- 
José Abílio

Re: bug(?): strange behavior after ctrl-shift-left

[Juergen Spitzmueller]

Jose' Matos wrote:
 I have finally succeeded with 1.4.2svn

   I have inserted two lines with one word and pressed enter to get a third
 (empty) line.

   While in the last empty line I pressed Ctrl-Shift-Left and... I got a
 crash.

I see. Most certainly DEPM interferes here and we end up with an invalid 
cursor (anchor).

Attached is a patch that fixes the crash for me, but I'm not sure it produces 
the behaviour we want (delete the empty paragraph, which is inconsistent to 
what LFUN_LEFTSEL does in this case).

However, I have no idea how to get DEPM *not* to trigger in this case.

Please test.

Jürgen
Index: src/text2.C
===
--- src/text2.C	(Revision 14351)
+++ src/text2.C	(Arbeitskopie)
@@ -1274,6 +1274,8 @@ bool LyXText::deleteEmptyParagraphMechan
 cur.resetAnchor();
 			}
 		}
+		if (cur.anchor().pit() == old.pit())
+			cur.resetAnchor();
 		updateCounters(old.buffer());
 		return true;
 	}

[PATCH] Re: bug(?): strange behavior after ctrl-shift-left

[Juergen Spitzmueller]

Juergen Spitzmueller wrote:
 Attached is a patch that fixes the crash for me, but I'm not sure it
 produces the behaviour we want (delete the empty paragraph, which is
 inconsistent to what LFUN_LEFTSEL does in this case).

attached is the proper fix, IMO.
selHandle has to be used, because it makes sure that the selection is properly 
set, which was not the case without that method. That's why DEPM was 
erroneously triggered.

This patch also fixes bug 2119 (Selection of text via keyboard sometimes 
fails) and bug 2259 (screen-up/down-select do not work).

Too late for 1.4.2?

Jürgen
Index: src/text3.C
===
--- src/text3.C	(Revision 14351)
+++ src/text3.C	(Arbeitskopie)
@@ -396,8 +396,7 @@ void LyXText::dispatch(LCursor  cur, Fu
 
 	case LFUN_BEGINNINGBUFSEL:
 		if (cur.depth() == 1) {
-			if (!cur.selection())
-cur.resetAnchor();
+			cur.selHandle(cmd.action == LFUN_BEGINNINGBUFSEL);
 			needsUpdate = cursorTop(cur);
 			finishChange(cur, true);
 		} else {
@@ -418,8 +417,7 @@ void LyXText::dispatch(LCursor  cur, Fu
 
 	case LFUN_ENDBUFSEL:
 		if (cur.depth() == 1) {
-			if (!cur.selection())
-cur.resetAnchor();
+			cur.selHandle(cmd.action == LFUN_ENDBUFSEL);
 			needsUpdate = cursorBottom(cur);
 			finishChange(cur, true);
 		} else {
@@ -496,8 +494,7 @@ void LyXText::dispatch(LCursor  cur, Fu
 		break;
 
 	case LFUN_UP_PARAGRAPHSEL:
-		if (!cur.selection())
-			cur.resetAnchor();
+		cur.selHandle(cmd.action == LFUN_UP_PARAGRAPHSEL);
 		cursorUpParagraph(cur);
 		finishChange(cur, true);
 		break;
@@ -510,47 +507,41 @@ void LyXText::dispatch(LCursor  cur, Fu
 		break;
 
 	case LFUN_DOWN_PARAGRAPHSEL:
-		if (!cur.selection())
-			cur.resetAnchor();
+		cur.selHandle(cmd.action == LFUN_DOWN_PARAGRAPHSEL);
 		cursorDownParagraph(cur);
 		finishChange(cur, true);
 		break;
 
 	case LFUN_PRIORSEL:
 		update(cur);
-		if (!cur.selection())
-			cur.resetAnchor();
+		cur.selHandle(cmd.action == LFUN_PRIORSEL);
 		needsUpdate = cursorPrevious(cur);
 		finishChange(cur, true);
 		break;
 
 	case LFUN_NEXTSEL:
 		update(cur);
-		if (!cur.selection())
-			cur.resetAnchor();
+		cur.selHandle(cmd.action == LFUN_NEXTSEL);
 		needsUpdate = cursorNext(cur);
 		finishChange(cur, true);
 		break;
 
 	case LFUN_HOMESEL:
 		update(cur);
-		if (!cur.selection())
-			cur.resetAnchor();
+		cur.selHandle(cmd.action == LFUN_HOMESEL);
 		needsUpdate = cursorHome(cur);
 		finishChange(cur, true);
 		break;
 
 	case LFUN_ENDSEL:
 		update(cur);
-		if (!cur.selection())
-			cur.resetAnchor();
+		cur.selHandle(cmd.action == LFUN_ENDSEL);
 		needsUpdate = cursorEnd(cur);
 		finishChange(cur, true);
 		break;
 
 	case LFUN_WORDRIGHTSEL:
-		if (!cur.selection())
-			cur.resetAnchor();
+		cur.selHandle(cmd.action == LFUN_WORDRIGHTSEL);
 		if (isRTL(cur.paragraph()))
 			cursorLeftOneWord(cur);
 		else
@@ -559,8 +550,7 @@ void LyXText::dispatch(LCursor  cur, Fu
 		break;
 
 	case LFUN_WORDLEFTSEL:
-		if (!cur.selection())
-			cur.resetAnchor();
+		cur.selHandle(cmd.action == LFUN_WORDLEFTSEL);
 		if (isRTL(cur.paragraph()))
 			cursorRightOneWord(cur);
 		else

Re: bug(?): strange behavior after ctrl-shift-left

[Juergen Spitzmueller]

Curtis Osterhoudt wrote:
> Ctrl-shift-left immediately crashes LyX (1.4.1, on a Debian machine) for
> me... so does ctrl-shift-up. I get the
> "lyx: SIGSEGV signal caught [...] Sorry, you have found a bug in LyX."
> message, too.

I cannot reproduce this either (neither the cases described in the other 
mails).

Can someone of you provide a backtrace?

Jürgen

Re: bug(?): strange behavior after ctrl-shift-left

[Jose' Matos]

On Wednesday 12 July 2006 08:45, Juergen Spitzmueller wrote:
>
> I cannot reproduce this either (neither the cases described in the other
> mails).

  I have finally succeeded with 1.4.2svn

  I have inserted two lines with one word and pressed enter to get a third 
(empty) line.

  While in the last empty line I pressed Ctrl-Shift-Left and... I got a crash.

> Can someone of you provide a backtrace?

  Follows attached. The culprit here seems to be the empty line. I have been 
working with lyx daily and I never noticed this because I do not usually do 
this on an empty line.

> Jürgen

-- 
José Abílio
(gdb) bt
#0  0x080b3206 in ParagraphParameters::depth (this=0x3c) at 
ParagraphParameters.C:75
#1  0x081ebaa6 in (anonymous namespace)::changeDepthAllowed 
(type=LyXText::INC_DEPTH, [EMAIL PROTECTED], max_depth=0) at text2.C:373
#2  0x081ebd06 in LyXText::changeDepthAllowed (this=0xa75f71c, [EMAIL 
PROTECTED], type=LyXText::INC_DEPTH) at text2.C:393
#3  0x081f08c4 in LyXText::getStatus (this=0xa75f71c, [EMAIL PROTECTED], [EMAIL 
PROTECTED], [EMAIL PROTECTED]) at text3.C:1578
#4  0x082df899 in InsetText::getStatus (this=0xa75f6f4, [EMAIL PROTECTED], 
[EMAIL PROTECTED], [EMAIL PROTECTED]) at insettext.C:263
#5  0x08151637 in (anonymous namespace)::getStatus ([EMAIL PROTECTED], [EMAIL 
PROTECTED], [EMAIL PROTECTED]) at lyxfunc.C:169
#6  0x08154bb5 in LyXFunc::getStatus (this=0xa642340, [EMAIL PROTECTED]) at 
lyxfunc.C:616
#7  0x083be9cb in lyx::frontend::QLToolbar::update (this=0xa699768) at 
QLToolbar.C:231
#8  0x0830a9df in Toolbars::update (this=0xa641548) at Toolbars.C:150
#9  0x0830ae84 in Toolbars::update (this=0xa641548, in_math=false, 
in_table=false) at Toolbars.C:67
#10 0x08307d3a in LyXView::updateToolbars (this=0xa657898) at LyXView.C:116
#11 0x08158305 in LyXFunc::sendDispatchMessage (this=0xa642340, [EMAIL 
PROTECTED], [EMAIL PROTECTED]) at lyxfunc.C:1625
#12 0x0816080e in LyXFunc::dispatch (this=0xa642340, [EMAIL PROTECTED]) at 
lyxfunc.C:1612
#13 0x08161951 in LyXFunc::processKeySym (this=0xa642340, [EMAIL PROTECTED], 
state=5) at lyxfunc.C:328
#14 0x0806529d in BufferView::Pimpl::workAreaKeyPress (this=0xa65f290, [EMAIL 
PROTECTED], state=5) at BufferView_pimpl.C:568
#15 0x08074258 in 
boost::detail::function::void_function_obj_invoker2, boost::_bi::list3, 
boost::arg<1>, boost::arg<2> > >, void, boost::shared_ptr, 
key_modifier::state>::invoke (function_obj_ptr=
{obj_ptr = 0xa663c38, const_obj_ptr = 0xa663c38, func_ptr = 0xa663c38, data = 
"8"}, [EMAIL PROTECTED], a1=5) at ../boost/boost/bind/mem_fn_template.hpp:252
#16 0x08466021 in boost::function2::operator() (this=0xa663c24, [EMAIL 
PROTECTED], a1=5)
at ../../../boost/boost/function/function_template.hpp:581
#17 0x0846712a in 
boost::operator++ >, 
boost::signals::detail::named_slot_map_iterator>, 
boost::signals::detail::unusable, boost::single_pass_traversal_tag, 
boost::signals::detail::unusable const&, int> ([EMAIL PROTECTED]) at 
../../../boost/boost/signals/signal_template.hpp:119
#18 0x0846785d in boost::signal2 >::operator() (this=0xa65f6f4, [EMAIL PROTECTED], a2=5) 
at ../../../boost/boost/last_value.hpp:43
#19 0x084644d6 in QContentPane::keyeventTimeout (this=0xa661778) at 
QContentPane.C:292
#20 0x0846ebaa in QContentPane::qt_invoke (this=0xa661778, _id=48, 
_o=0xbf81cec8) at QContentPane_moc.C:91
#21 0x00a0735a in QObject::activate_signal () from 
/usr/lib/qt-3.3/lib/libqt-mt.so.3
#22 0x00a07ecd in QObject::activate_signal () from 
/usr/lib/qt-3.3/lib/libqt-mt.so.3
#23 0x00d93b69 in QTimer::timeout () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#24 0x00a2e9ff in QTimer::event () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#25 0x0099e82b in QApplication::internalNotify () from 
/usr/lib/qt-3.3/lib/libqt-mt.so.3
#26 0x0099fc79 in QApplication::notify () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#27 0x00992632 in QEventLoop::activateTimers () from 
/usr/lib/qt-3.3/lib/libqt-mt.so.3
#28 0x009453ef in QEventLoop::processEvents () from 
/usr/lib/qt-3.3/lib/libqt-mt.so.3
#29 0x009b7cd0 in QEventLoop::enterLoop () from 
/usr/lib/qt-3.3/lib/libqt-mt.so.3
#30 0x009b7b96 in QEventLoop::exec () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#31 0x0099e33f in QApplication::exec () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#32 0x0837aeb5 in lyx_gui::start ([EMAIL PROTECTED], [EMAIL PROTECTED]) at 
lyx_gui.C:253
#33 0x08143aff in LyX::exec2 (this=0xa592900, [EMAIL PROTECTED], 
argv=0xbf81d714) at lyx_main.C:298
#34 0x0837ba9a in 

Re: bug(?): strange behavior after ctrl-shift-left

[Jose' Matos]

On Wednesday 12 July 2006 01:29, Steve Harris wrote:
>
> Good day José,

  Good day,

> After reading your post, I tested again and this is
> not fixed in 1.4.2. It isn't much of a bug.

  After several trials I succeeded into reproducing the bug, even for 
1.4.2.svn.

> This is an example line.
>
> {If I type in ctrl-shift-leftarrow down here, start of a
> new paragraph, and I have entered no text, blank in other
> words, then the blue highlight reverts back to the end of
>
> This is an example line.(<-- begins blue highlight)
>
> and if you type in it, then it will segfault lyx. If you have
> typed more than one paragraph with words it works normally.}
>
> But again, if you have typed three paragraphs and then
> type "ctrl-shift-leftarrow" at the beginning of a new
> paragraph which has no words (blank) then it will segfault.

  I noticed that too.

> It means that if you end a paragraph by using enter, then
> you can't change your mind with "ctrl-shift-leftarrow" and
> go back to the previous paragraph and type a little more
> before you start your new paragraph. You can go back with
> your mouse to the end of the previous paragraph and
> "ctrl-shift-leftarrow" will work normally. I am something
> of a keyboard purist, but I normally use Edit/Undo to
> reverse my last step; but Alt-e-u will Undo, take you
> back to the end of the previous paragraph (reverses enter)
> and then "ctrl-shift-leftarrow" will work as expected.

  Sometimes it crashes immediately.

> It may have seemed if I wrote in too much detail. But you
> reported it worked on Linux and I have the most excellent
> FC4, and it malfunctions just as reported:
>
> This is the first paragraph. 
>
> begins the second paragraph = blank: -> ctrl-shift-leftarrow
>
> goes back to the end of the first paragraph and freezes the
> machine. Shortly afterwards it exited with the same error
> message that I reported for Cygwin Lyx 1.4.1 and it segfaults
> in Joost's windows 1.4.2 also, but the error screen exits too
> fast to see the text. This message is from FC4/Cygwin Lyx1.4.1.
>
> --
>
> $ lyx
> LyX: Attempting to save document newfile1.lyx
>   /cygdrive/c/home/newfile1.lyx.emergency
>Save seems successful. Phew.
>
> lyx: SIGSEGV signal caught
> Sorry, you have found a bug in LyX. Please read the
> bug-reporting instructions in Help->Introduction and
> send us a bug report, if necessary. Thanks !
> Bye.
> Aborted (core dumped)
>
> 
>
> Is the upgrade to FC5 *strongly recommended*?

  Nope.

> Stephen

-- 
José Abílio

Re: bug(?): strange behavior after ctrl-shift-left

[Juergen Spitzmueller]

Jose' Matos wrote:
> I have finally succeeded with 1.4.2svn
>
>   I have inserted two lines with one word and pressed enter to get a third
> (empty) line.
>
>   While in the last empty line I pressed Ctrl-Shift-Left and... I got a
> crash.

I see. Most certainly DEPM interferes here and we end up with an invalid 
cursor (anchor).

Attached is a patch that fixes the crash for me, but I'm not sure it produces 
the behaviour we want (delete the empty paragraph, which is inconsistent to 
what LFUN_LEFTSEL does in this case).

However, I have no idea how to get DEPM *not* to trigger in this case.

Please test.

Jürgen
Index: src/text2.C
===
--- src/text2.C	(Revision 14351)
+++ src/text2.C	(Arbeitskopie)
@@ -1274,6 +1274,8 @@ bool LyXText::deleteEmptyParagraphMechan
 cur.resetAnchor();
 			}
 		}
+		if (cur.anchor().pit() == old.pit())
+			cur.resetAnchor();
 		updateCounters(old.buffer());
 		return true;
 	}

[PATCH] Re: bug(?): strange behavior after ctrl-shift-left

[Juergen Spitzmueller]

Juergen Spitzmueller wrote:
> Attached is a patch that fixes the crash for me, but I'm not sure it
> produces the behaviour we want (delete the empty paragraph, which is
> inconsistent to what LFUN_LEFTSEL does in this case).

attached is the proper fix, IMO.
selHandle has to be used, because it makes sure that the selection is properly 
set, which was not the case without that method. That's why DEPM was 
erroneously triggered.

This patch also fixes bug 2119 (Selection of text via keyboard sometimes 
fails) and bug 2259 (screen-up/down-select do not work).

Too late for 1.4.2?

Jürgen
Index: src/text3.C
===
--- src/text3.C	(Revision 14351)
+++ src/text3.C	(Arbeitskopie)
@@ -396,8 +396,7 @@ void LyXText::dispatch(LCursor & cur, Fu
 
 	case LFUN_BEGINNINGBUFSEL:
 		if (cur.depth() == 1) {
-			if (!cur.selection())
-cur.resetAnchor();
+			cur.selHandle(cmd.action == LFUN_BEGINNINGBUFSEL);
 			needsUpdate = cursorTop(cur);
 			finishChange(cur, true);
 		} else {
@@ -418,8 +417,7 @@ void LyXText::dispatch(LCursor & cur, Fu
 
 	case LFUN_ENDBUFSEL:
 		if (cur.depth() == 1) {
-			if (!cur.selection())
-cur.resetAnchor();
+			cur.selHandle(cmd.action == LFUN_ENDBUFSEL);
 			needsUpdate = cursorBottom(cur);
 			finishChange(cur, true);
 		} else {
@@ -496,8 +494,7 @@ void LyXText::dispatch(LCursor & cur, Fu
 		break;
 
 	case LFUN_UP_PARAGRAPHSEL:
-		if (!cur.selection())
-			cur.resetAnchor();
+		cur.selHandle(cmd.action == LFUN_UP_PARAGRAPHSEL);
 		cursorUpParagraph(cur);
 		finishChange(cur, true);
 		break;
@@ -510,47 +507,41 @@ void LyXText::dispatch(LCursor & cur, Fu
 		break;
 
 	case LFUN_DOWN_PARAGRAPHSEL:
-		if (!cur.selection())
-			cur.resetAnchor();
+		cur.selHandle(cmd.action == LFUN_DOWN_PARAGRAPHSEL);
 		cursorDownParagraph(cur);
 		finishChange(cur, true);
 		break;
 
 	case LFUN_PRIORSEL:
 		update(cur);
-		if (!cur.selection())
-			cur.resetAnchor();
+		cur.selHandle(cmd.action == LFUN_PRIORSEL);
 		needsUpdate = cursorPrevious(cur);
 		finishChange(cur, true);
 		break;
 
 	case LFUN_NEXTSEL:
 		update(cur);
-		if (!cur.selection())
-			cur.resetAnchor();
+		cur.selHandle(cmd.action == LFUN_NEXTSEL);
 		needsUpdate = cursorNext(cur);
 		finishChange(cur, true);
 		break;
 
 	case LFUN_HOMESEL:
 		update(cur);
-		if (!cur.selection())
-			cur.resetAnchor();
+		cur.selHandle(cmd.action == LFUN_HOMESEL);
 		needsUpdate = cursorHome(cur);
 		finishChange(cur, true);
 		break;
 
 	case LFUN_ENDSEL:
 		update(cur);
-		if (!cur.selection())
-			cur.resetAnchor();
+		cur.selHandle(cmd.action == LFUN_ENDSEL);
 		needsUpdate = cursorEnd(cur);
 		finishChange(cur, true);
 		break;
 
 	case LFUN_WORDRIGHTSEL:
-		if (!cur.selection())
-			cur.resetAnchor();
+		cur.selHandle(cmd.action == LFUN_WORDRIGHTSEL);
 		if (isRTL(cur.paragraph()))
 			cursorLeftOneWord(cur);
 		else
@@ -559,8 +550,7 @@ void LyXText::dispatch(LCursor & cur, Fu
 		break;
 
 	case LFUN_WORDLEFTSEL:
-		if (!cur.selection())
-			cur.resetAnchor();
+		cur.selHandle(cmd.action == LFUN_WORDLEFTSEL);
 		if (isRTL(cur.paragraph()))
 			cursorRightOneWord(cur);
 		else

bug(?): strange behavior after ctrl-shift-left

[Sven Schreiber]

To reproduce:
1. open new document
2. type something and start a new paragraph (hit return)
3. hit control-shift-arrowleft

For me the keyboard is not responding in lyx anymore after that. Can
anybody confirm this? Is it known?

Ctrl-shift-left may be stupid to use, but I was just following a hunch...

this is 1.4.1 on windows with official installer

thanks,
sven

Re: bug(?): strange behavior after ctrl-shift-left

[Jose' Matos]

On Tuesday 11 July 2006 20:50, Sven Schreiber wrote:
 For me the keyboard is not responding in lyx anymore after that. Can
 anybody confirm this? Is it known?

  I do not remember such bug report. :-(
  I would like to hear from other windows users. If the bug is not there it 
should be filled in bugzilla to be fixed in 1.4.2.

 Ctrl-shift-left may be stupid to use, but I was just following a hunch...

  Not stupid at all, it selects text from your current position to left. I 
guess that this was your hunch.

 this is 1.4.1 on windows with official installer

  It works on linux, I have been using it all day. :-)

 thanks,
 sven

-- 
José Abílio

Re: bug(?): strange behavior after ctrl-shift-left

[Steve Harris]

Sven Schreiber wrote:

To reproduce:
1. open new document
2. type something and start a new paragraph (hit return)
3. hit control-shift-arrowleft

For me the keyboard is not responding in lyx anymore after that. Can
anybody confirm this? Is it known?

Ctrl-shift-left may be stupid to use, but I was just following a hunch...

this is 1.4.1 on windows with official installer

thanks,
sven



I have 1.4.1 installed under Cygwin which
produced:

--

$ lyx
LyX: Attempting to save document newfile1.lyx
 /cygdrive/c/home/newfile1.lyx.emergency
  Save seems successful. Phew.

lyx: SIGSEGV signal caught
Sorry, you have found a bug in LyX. Please read the
bug-reporting instructions in Help-Introduction and
send us a bug report, if necessary. Thanks !
Bye.
Aborted (core dumped)



But under the Joost Windows 1.4.2, it seems to work
normally. To undo the freeze I think you can go to
Edit - import lines, and clicking on that will
undo that frozen blue tableau.

It appears to be fixed in 1.4.2 which is near release
so you could see if it is fixed then on your machine.

Regards,
Stephen

Re: bug(?): strange behavior after ctrl-shift-left

[Curtis Osterhoudt]

From: Jose' Matos [EMAIL PROTECTED]
To: lyx-users@lists.lyx.org
Subject: Re: bug(?): strange behavior after ctrl-shift-left
Date: Tue, 11 Jul 2006 23:18:36 +0100

On Tuesday 11 July 2006 20:50, Sven Schreiber wrote:
 For me the keyboard is not responding in lyx anymore after that. Can
 anybody confirm this? Is it known?

  I do not remember such bug report. :-(
  I would like to hear from other windows users. If the bug is not there 
it

should be filled in bugzilla to be fixed in 1.4.2.

 Ctrl-shift-left may be stupid to use, but I was just following a 
hunch...


  Not stupid at all, it selects text from your current position to left. I
guess that this was your hunch.

 this is 1.4.1 on windows with official installer

  It works on linux, I have been using it all day. :-)

 thanks,
 sven

--
José Abílio



Ctrl-shift-left immediately crashes LyX (1.4.1, on a Debian machine) for 
me... so does ctrl-shift-up. I get the
lyx: SIGSEGV signal caught [...] Sorry, you have found a bug in LyX. 
message, too.

Re: bug(?): strange behavior after ctrl-shift-left

[Steve Harris]

Jose' Matos wrote:

On Tuesday 11 July 2006 20:50, Sven Schreiber wrote:

For me the keyboard is not responding in lyx anymore after that. Can
anybody confirm this? Is it known?


  I do not remember such bug report. :-(
  I would like to hear from other windows users. If the bug is not there it 
should be filled in bugzilla to be fixed in 1.4.2.



Ctrl-shift-left may be stupid to use, but I was just following a hunch...


  Not stupid at all, it selects text from your current position to left. I 
guess that this was your hunch.



this is 1.4.1 on windows with official installer


  It works on linux, I have been using it all day. :-)


thanks,
sven





Good day José,

After reading your post, I tested again and this is
not fixed in 1.4.2. It isn't much of a bug.

This is an example line.

{If I type in ctrl-shift-leftarrow down here, start of a
new paragraph, and I have entered no text, blank in other
words, then the blue highlight reverts back to the end of

This is an example line.(-- begins blue highlight)

and if you type in it, then it will segfault lyx. If you have
typed more than one paragraph with words it works normally.}

But again, if you have typed three paragraphs and then
type ctrl-shift-leftarrow at the beginning of a new
paragraph which has no words (blank) then it will segfault.

It means that if you end a paragraph by using enter, then
you can't change your mind with ctrl-shift-leftarrow and
go back to the previous paragraph and type a little more
before you start your new paragraph. You can go back with
your mouse to the end of the previous paragraph and
ctrl-shift-leftarrow will work normally. I am something
of a keyboard purist, but I normally use Edit/Undo to
reverse my last step; but Alt-e-u will Undo, take you
back to the end of the previous paragraph (reverses enter)
and then ctrl-shift-leftarrow will work as expected.

It may have seemed if I wrote in too much detail. But you
reported it worked on Linux and I have the most excellent
FC4, and it malfunctions just as reported:

This is the first paragraph. enter

begins the second paragraph = blank: - ctrl-shift-leftarrow

goes back to the end of the first paragraph and freezes the
machine. Shortly afterwards it exited with the same error
message that I reported for Cygwin Lyx 1.4.1 and it segfaults
in Joost's windows 1.4.2 also, but the error screen exits too
fast to see the text. This message is from FC4/Cygwin Lyx1.4.1.

--

$ lyx
LyX: Attempting to save document newfile1.lyx
 /cygdrive/c/home/newfile1.lyx.emergency
  Save seems successful. Phew.

lyx: SIGSEGV signal caught
Sorry, you have found a bug in LyX. Please read the
bug-reporting instructions in Help-Introduction and
send us a bug report, if necessary. Thanks !
Bye.
Aborted (core dumped)



Is the upgrade to FC5 *strongly recommended*?
Stephen

Re: bug(?): strange behavior after ctrl-shift-left

[Paul A. Rubin]

Jose' Matos wrote:

  I would like to hear from other windows users. If the bug is not there it 
should be filled in bugzilla to be fixed in 1.4.2.


I can reproduce it (LyX 1.4.1, WinXP).  If I follow Sven's instructions 
and then type the letter 'a', the keyboard is locked out (but the mouse 
still works), the 'a' never shows up on screen, and here's what the 
debug output looks like (from the point immediately after ctrl-shift-left):


Setting key to 65, a
KeySym is a
isOK is 1
isMod is 0
encoding is iso8859-1
Using codec ISO 8859-1
ISOEncoded returning value 97
void LyXFunc::processKeySym(boost::shared_ptrLyXKeySym, 
key_modifier::state)

ction first set to [86]
void LyXFunc::processKeySym(boost::shared_ptrLyXKeySym, 
key_modifier::state)a

tion now set to [86]
void LyXFunc::processKeySym(boost::shared_ptrLyXKeySym, 
key_modifier::state)

ey [action=86][A]
LyXFunc::dispatch: cmd:  action: 86 arg: 'a' x: 0 y: 0
void LCursor::dispatch(const FuncRequest) cmd:  action: 86 arg: 'a' x: 
0 y: 0


 cursor:| anchor:
 inset: 0x1102eac idx: 0 par: 0 pos: 8 | inset: 0x1102eac idx: 0 par: 1 
pos: 0

 selection: 1 x_target: 113

LCursor::dispatch: cmd:  action: 86 arg: 'a' x: 0 y: 0

 cursor:| anchor:
 inset: 0x1102eac idx: 0 par: 0 pos: 8 | inset: 0x1102eac idx: 0 par: 1 
pos: 0

 selection: 1 x_target: 113

virtual void InsetText::doDispatch(LCursor, FuncRequest) [ cmd.action 
= 86]

LyXText::dispatch: cmd:  action: 86 arg: 'a' x: 0 y: 0

Hopefully someone can read that (I can't, other than I get that it's 
reporting my having typed 'a' near the top).


Incidentally, if the first thing you do after ctrl-shift-left is to 
click someplace in the document, or hit the left arrow key, the keyboard 
remains responsive.  (Hitting up, down or right arrow does not avoid the 
problem but also does not cause the keyboard to lock out -- they have no 
effect at all.)  Also, when the keyboard lockout occurs, LyX is 
hammering the CPU (close to 100% load) for a few seconds.  Then it goes 
back to a light load, and the mouse works.


One other odd thing -- the keyboard works for issuing menu commands 
(alt-F x to exit, for instance).


/Paul

Re: bug(?): strange behavior after ctrl-shift-left

[Steve Harris]

Jose' Matos wrote:

On Tuesday 11 July 2006 20:50, Sven Schreiber wrote:

For me the keyboard is not responding in lyx anymore after that. Can
anybody confirm this? Is it known?


  I do not remember such bug report. :-(
  I would like to hear from other windows users. If the bug is not there it 
should be filled in bugzilla to be fixed in 1.4.2.



Ctrl-shift-left may be stupid to use, but I was just following a hunch...


  Not stupid at all, it selects text from your current position to left. I 
guess that this was your hunch.



this is 1.4.1 on windows with official installer


  It works on linux, I have been using it all day. :-)


thanks,
sven




I tested this on lyx1.3.7ver3 for Windows and the bug is not there.

This is a test. enter
ctrl-shift-left_key

will return to the space just afer test. in the previous
paragraph. If you use ctrl-shift=left_key again, then
it will highlight in blue, test. (from This is a test.)

Also the spell-checking error of starting to check only the
second misspelled word is not present in lyx1.3.7ver3 either.

--

Stephen
Once you eliminate the impossible, whatever remains, no matter
how improbable, must be the truth. SH: Sherlock Holmes (Doyle)

bug(?): strange behavior after ctrl-shift-left

[Sven Schreiber]

To reproduce:
1. open new document
2. type something and start a new paragraph (hit return)
3. hit control-shift-arrowleft

For me the keyboard is not responding in lyx anymore after that. Can
anybody confirm this? Is it known?

Ctrl-shift-left may be stupid to use, but I was just following a hunch...

this is 1.4.1 on windows with official installer

thanks,
sven

Re: bug(?): strange behavior after ctrl-shift-left

[Jose' Matos]

On Tuesday 11 July 2006 20:50, Sven Schreiber wrote:
 For me the keyboard is not responding in lyx anymore after that. Can
 anybody confirm this? Is it known?

  I do not remember such bug report. :-(
  I would like to hear from other windows users. If the bug is not there it 
should be filled in bugzilla to be fixed in 1.4.2.

 Ctrl-shift-left may be stupid to use, but I was just following a hunch...

  Not stupid at all, it selects text from your current position to left. I 
guess that this was your hunch.

 this is 1.4.1 on windows with official installer

  It works on linux, I have been using it all day. :-)

 thanks,
 sven

-- 
José Abílio

Re: bug(?): strange behavior after ctrl-shift-left

[Steve Harris]

Sven Schreiber wrote:

To reproduce:
1. open new document
2. type something and start a new paragraph (hit return)
3. hit control-shift-arrowleft

For me the keyboard is not responding in lyx anymore after that. Can
anybody confirm this? Is it known?

Ctrl-shift-left may be stupid to use, but I was just following a hunch...

this is 1.4.1 on windows with official installer

thanks,
sven



I have 1.4.1 installed under Cygwin which
produced:

--

$ lyx
LyX: Attempting to save document newfile1.lyx
 /cygdrive/c/home/newfile1.lyx.emergency
  Save seems successful. Phew.

lyx: SIGSEGV signal caught
Sorry, you have found a bug in LyX. Please read the
bug-reporting instructions in Help-Introduction and
send us a bug report, if necessary. Thanks !
Bye.
Aborted (core dumped)



But under the Joost Windows 1.4.2, it seems to work
normally. To undo the freeze I think you can go to
Edit - import lines, and clicking on that will
undo that frozen blue tableau.

It appears to be fixed in 1.4.2 which is near release
so you could see if it is fixed then on your machine.

Regards,
Stephen

Re: bug(?): strange behavior after ctrl-shift-left

[Curtis Osterhoudt]

From: Jose' Matos [EMAIL PROTECTED]
To: lyx-users@lists.lyx.org
Subject: Re: bug(?): strange behavior after ctrl-shift-left
Date: Tue, 11 Jul 2006 23:18:36 +0100

On Tuesday 11 July 2006 20:50, Sven Schreiber wrote:
 For me the keyboard is not responding in lyx anymore after that. Can
 anybody confirm this? Is it known?

  I do not remember such bug report. :-(
  I would like to hear from other windows users. If the bug is not there 
it

should be filled in bugzilla to be fixed in 1.4.2.

 Ctrl-shift-left may be stupid to use, but I was just following a 
hunch...


  Not stupid at all, it selects text from your current position to left. I
guess that this was your hunch.

 this is 1.4.1 on windows with official installer

  It works on linux, I have been using it all day. :-)

 thanks,
 sven

--
José Abílio



Ctrl-shift-left immediately crashes LyX (1.4.1, on a Debian machine) for 
me... so does ctrl-shift-up. I get the
lyx: SIGSEGV signal caught [...] Sorry, you have found a bug in LyX. 
message, too.

Re: bug(?): strange behavior after ctrl-shift-left

[Steve Harris]

Jose' Matos wrote:

On Tuesday 11 July 2006 20:50, Sven Schreiber wrote:

For me the keyboard is not responding in lyx anymore after that. Can
anybody confirm this? Is it known?


  I do not remember such bug report. :-(
  I would like to hear from other windows users. If the bug is not there it 
should be filled in bugzilla to be fixed in 1.4.2.



Ctrl-shift-left may be stupid to use, but I was just following a hunch...


  Not stupid at all, it selects text from your current position to left. I 
guess that this was your hunch.



this is 1.4.1 on windows with official installer


  It works on linux, I have been using it all day. :-)


thanks,
sven





Good day José,

After reading your post, I tested again and this is
not fixed in 1.4.2. It isn't much of a bug.

This is an example line.

{If I type in ctrl-shift-leftarrow down here, start of a
new paragraph, and I have entered no text, blank in other
words, then the blue highlight reverts back to the end of

This is an example line.(-- begins blue highlight)

and if you type in it, then it will segfault lyx. If you have
typed more than one paragraph with words it works normally.}

But again, if you have typed three paragraphs and then
type ctrl-shift-leftarrow at the beginning of a new
paragraph which has no words (blank) then it will segfault.

It means that if you end a paragraph by using enter, then
you can't change your mind with ctrl-shift-leftarrow and
go back to the previous paragraph and type a little more
before you start your new paragraph. You can go back with
your mouse to the end of the previous paragraph and
ctrl-shift-leftarrow will work normally. I am something
of a keyboard purist, but I normally use Edit/Undo to
reverse my last step; but Alt-e-u will Undo, take you
back to the end of the previous paragraph (reverses enter)
and then ctrl-shift-leftarrow will work as expected.

It may have seemed if I wrote in too much detail. But you
reported it worked on Linux and I have the most excellent
FC4, and it malfunctions just as reported:

This is the first paragraph. enter

begins the second paragraph = blank: - ctrl-shift-leftarrow

goes back to the end of the first paragraph and freezes the
machine. Shortly afterwards it exited with the same error
message that I reported for Cygwin Lyx 1.4.1 and it segfaults
in Joost's windows 1.4.2 also, but the error screen exits too
fast to see the text. This message is from FC4/Cygwin Lyx1.4.1.

--

$ lyx
LyX: Attempting to save document newfile1.lyx
 /cygdrive/c/home/newfile1.lyx.emergency
  Save seems successful. Phew.

lyx: SIGSEGV signal caught
Sorry, you have found a bug in LyX. Please read the
bug-reporting instructions in Help-Introduction and
send us a bug report, if necessary. Thanks !
Bye.
Aborted (core dumped)



Is the upgrade to FC5 *strongly recommended*?
Stephen

Re: bug(?): strange behavior after ctrl-shift-left

[Paul A. Rubin]

Jose' Matos wrote:

  I would like to hear from other windows users. If the bug is not there it 
should be filled in bugzilla to be fixed in 1.4.2.


I can reproduce it (LyX 1.4.1, WinXP).  If I follow Sven's instructions 
and then type the letter 'a', the keyboard is locked out (but the mouse 
still works), the 'a' never shows up on screen, and here's what the 
debug output looks like (from the point immediately after ctrl-shift-left):


Setting key to 65, a
KeySym is a
isOK is 1
isMod is 0
encoding is iso8859-1
Using codec ISO 8859-1
ISOEncoded returning value 97
void LyXFunc::processKeySym(boost::shared_ptrLyXKeySym, 
key_modifier::state)

ction first set to [86]
void LyXFunc::processKeySym(boost::shared_ptrLyXKeySym, 
key_modifier::state)a

tion now set to [86]
void LyXFunc::processKeySym(boost::shared_ptrLyXKeySym, 
key_modifier::state)

ey [action=86][A]
LyXFunc::dispatch: cmd:  action: 86 arg: 'a' x: 0 y: 0
void LCursor::dispatch(const FuncRequest) cmd:  action: 86 arg: 'a' x: 
0 y: 0


 cursor:| anchor:
 inset: 0x1102eac idx: 0 par: 0 pos: 8 | inset: 0x1102eac idx: 0 par: 1 
pos: 0

 selection: 1 x_target: 113

LCursor::dispatch: cmd:  action: 86 arg: 'a' x: 0 y: 0

 cursor:| anchor:
 inset: 0x1102eac idx: 0 par: 0 pos: 8 | inset: 0x1102eac idx: 0 par: 1 
pos: 0

 selection: 1 x_target: 113

virtual void InsetText::doDispatch(LCursor, FuncRequest) [ cmd.action 
= 86]

LyXText::dispatch: cmd:  action: 86 arg: 'a' x: 0 y: 0

Hopefully someone can read that (I can't, other than I get that it's 
reporting my having typed 'a' near the top).


Incidentally, if the first thing you do after ctrl-shift-left is to 
click someplace in the document, or hit the left arrow key, the keyboard 
remains responsive.  (Hitting up, down or right arrow does not avoid the 
problem but also does not cause the keyboard to lock out -- they have no 
effect at all.)  Also, when the keyboard lockout occurs, LyX is 
hammering the CPU (close to 100% load) for a few seconds.  Then it goes 
back to a light load, and the mouse works.


One other odd thing -- the keyboard works for issuing menu commands 
(alt-F x to exit, for instance).


/Paul

Re: bug(?): strange behavior after ctrl-shift-left

[Steve Harris]

Jose' Matos wrote:

On Tuesday 11 July 2006 20:50, Sven Schreiber wrote:

For me the keyboard is not responding in lyx anymore after that. Can
anybody confirm this? Is it known?


  I do not remember such bug report. :-(
  I would like to hear from other windows users. If the bug is not there it 
should be filled in bugzilla to be fixed in 1.4.2.



Ctrl-shift-left may be stupid to use, but I was just following a hunch...


  Not stupid at all, it selects text from your current position to left. I 
guess that this was your hunch.



this is 1.4.1 on windows with official installer


  It works on linux, I have been using it all day. :-)


thanks,
sven




I tested this on lyx1.3.7ver3 for Windows and the bug is not there.

This is a test. enter
ctrl-shift-left_key

will return to the space just afer test. in the previous
paragraph. If you use ctrl-shift=left_key again, then
it will highlight in blue, test. (from This is a test.)

Also the spell-checking error of starting to check only the
second misspelled word is not present in lyx1.3.7ver3 either.

--

Stephen
Once you eliminate the impossible, whatever remains, no matter
how improbable, must be the truth. SH: Sherlock Holmes (Doyle)

bug(?): strange behavior after ctrl-shift-left

[Sven Schreiber]

To reproduce:
1. open new document
2. type something and start a new paragraph (hit return)
3. hit control-shift-arrowleft

For me the keyboard is not responding in lyx anymore after that. Can
anybody confirm this? Is it known?

Ctrl-shift-left may be stupid to use, but I was just following a hunch...

this is 1.4.1 on windows with official installer

thanks,
sven

Re: bug(?): strange behavior after ctrl-shift-left

[Jose' Matos]

On Tuesday 11 July 2006 20:50, Sven Schreiber wrote:
> For me the keyboard is not responding in lyx anymore after that. Can
> anybody confirm this? Is it known?

  I do not remember such bug report. :-(
  I would like to hear from other windows users. If the bug is not there it 
should be filled in bugzilla to be fixed in 1.4.2.

> Ctrl-shift-left may be stupid to use, but I was just following a hunch...

  Not stupid at all, it selects text from your current position to left. I 
guess that this was your hunch.

> this is 1.4.1 on windows with official installer

  It works on linux, I have been using it all day. :-)

> thanks,
> sven

-- 
José Abílio

Re: bug(?): strange behavior after ctrl-shift-left

[Steve Harris]

Sven Schreiber wrote:

To reproduce:
1. open new document
2. type something and start a new paragraph (hit return)
3. hit control-shift-arrowleft

For me the keyboard is not responding in lyx anymore after that. Can
anybody confirm this? Is it known?

Ctrl-shift-left may be stupid to use, but I was just following a hunch...

this is 1.4.1 on windows with official installer

thanks,
sven



I have 1.4.1 installed under Cygwin which
produced:

--

$ lyx
LyX: Attempting to save document newfile1.lyx
 /cygdrive/c/home/newfile1.lyx.emergency
  Save seems successful. Phew.

lyx: SIGSEGV signal caught
Sorry, you have found a bug in LyX. Please read the
bug-reporting instructions in Help->Introduction and
send us a bug report, if necessary. Thanks !
Bye.
Aborted (core dumped)



But under the Joost Windows 1.4.2, it seems to work
normally. To undo the freeze I think you can go to
Edit -> import lines, and clicking on that will
undo that frozen blue tableau.

It appears to be fixed in 1.4.2 which is near release
so you could see if it is fixed then on your machine.

Regards,
Stephen

Re: bug(?): strange behavior after ctrl-shift-left

[Curtis Osterhoudt]

From: Jose' Matos <[EMAIL PROTECTED]>
To: lyx-users@lists.lyx.org
Subject: Re: bug(?): strange behavior after ctrl-shift-left
Date: Tue, 11 Jul 2006 23:18:36 +0100

On Tuesday 11 July 2006 20:50, Sven Schreiber wrote:
> For me the keyboard is not responding in lyx anymore after that. Can
> anybody confirm this? Is it known?

  I do not remember such bug report. :-(
  I would like to hear from other windows users. If the bug is not there 
it

should be filled in bugzilla to be fixed in 1.4.2.

> Ctrl-shift-left may be stupid to use, but I was just following a 
hunch...


  Not stupid at all, it selects text from your current position to left. I
guess that this was your hunch.

> this is 1.4.1 on windows with official installer

  It works on linux, I have been using it all day. :-)

> thanks,
> sven

--
José Abílio



Ctrl-shift-left immediately crashes LyX (1.4.1, on a Debian machine) for 
me... so does ctrl-shift-up. I get the
"lyx: SIGSEGV signal caught [...] Sorry, you have found a bug in LyX." 
message, too.

Re: bug(?): strange behavior after ctrl-shift-left

[Steve Harris]

Jose' Matos wrote:

On Tuesday 11 July 2006 20:50, Sven Schreiber wrote:

For me the keyboard is not responding in lyx anymore after that. Can
anybody confirm this? Is it known?


  I do not remember such bug report. :-(
  I would like to hear from other windows users. If the bug is not there it 
should be filled in bugzilla to be fixed in 1.4.2.



Ctrl-shift-left may be stupid to use, but I was just following a hunch...


  Not stupid at all, it selects text from your current position to left. I 
guess that this was your hunch.



this is 1.4.1 on windows with official installer


  It works on linux, I have been using it all day. :-)


thanks,
sven





Good day José,

After reading your post, I tested again and this is
not fixed in 1.4.2. It isn't much of a bug.

This is an example line.

{If I type in ctrl-shift-leftarrow down here, start of a
new paragraph, and I have entered no text, blank in other
words, then the blue highlight reverts back to the end of

This is an example line.(<-- begins blue highlight)

and if you type in it, then it will segfault lyx. If you have
typed more than one paragraph with words it works normally.}

But again, if you have typed three paragraphs and then
type "ctrl-shift-leftarrow" at the beginning of a new
paragraph which has no words (blank) then it will segfault.

It means that if you end a paragraph by using enter, then
you can't change your mind with "ctrl-shift-leftarrow" and
go back to the previous paragraph and type a little more
before you start your new paragraph. You can go back with
your mouse to the end of the previous paragraph and
"ctrl-shift-leftarrow" will work normally. I am something
of a keyboard purist, but I normally use Edit/Undo to
reverse my last step; but Alt-e-u will Undo, take you
back to the end of the previous paragraph (reverses enter)
and then "ctrl-shift-leftarrow" will work as expected.

It may have seemed if I wrote in too much detail. But you
reported it worked on Linux and I have the most excellent
FC4, and it malfunctions just as reported:

This is the first paragraph. 

begins the second paragraph = blank: -> ctrl-shift-leftarrow

goes back to the end of the first paragraph and freezes the
machine. Shortly afterwards it exited with the same error
message that I reported for Cygwin Lyx 1.4.1 and it segfaults
in Joost's windows 1.4.2 also, but the error screen exits too
fast to see the text. This message is from FC4/Cygwin Lyx1.4.1.

--

$ lyx
LyX: Attempting to save document newfile1.lyx
 /cygdrive/c/home/newfile1.lyx.emergency
  Save seems successful. Phew.

lyx: SIGSEGV signal caught
Sorry, you have found a bug in LyX. Please read the
bug-reporting instructions in Help->Introduction and
send us a bug report, if necessary. Thanks !
Bye.
Aborted (core dumped)



Is the upgrade to FC5 *strongly recommended*?
Stephen

Re: bug(?): strange behavior after ctrl-shift-left

[Paul A. Rubin]

Jose' Matos wrote:

  I would like to hear from other windows users. If the bug is not there it 
should be filled in bugzilla to be fixed in 1.4.2.


I can reproduce it (LyX 1.4.1, WinXP).  If I follow Sven's instructions 
and then type the letter 'a', the keyboard is locked out (but the mouse 
still works), the 'a' never shows up on screen, and here's what the 
debug output looks like (from the point immediately after ctrl-shift-left):


Setting key to 65, a
KeySym is a
isOK is 1
isMod is 0
encoding is iso8859-1
Using codec ISO 8859-1
ISOEncoded returning value 97
void LyXFunc::processKeySym(boost::shared_ptr, 
key_modifier::state)

ction first set to [86]
void LyXFunc::processKeySym(boost::shared_ptr, 
key_modifier::state)a

tion now set to [86]
void LyXFunc::processKeySym(boost::shared_ptr, 
key_modifier::state)

ey [action=86][A]
LyXFunc::dispatch: cmd:  action: 86 arg: 'a' x: 0 y: 0
void LCursor::dispatch(const FuncRequest&) cmd:  action: 86 arg: 'a' x: 
0 y: 0


 cursor:| anchor:
 inset: 0x1102eac idx: 0 par: 0 pos: 8 | inset: 0x1102eac idx: 0 par: 1 
pos: 0

 selection: 1 x_target: 113

LCursor::dispatch: cmd:  action: 86 arg: 'a' x: 0 y: 0

 cursor:| anchor:
 inset: 0x1102eac idx: 0 par: 0 pos: 8 | inset: 0x1102eac idx: 0 par: 1 
pos: 0

 selection: 1 x_target: 113

virtual void InsetText::doDispatch(LCursor&, FuncRequest&) [ cmd.action 
= 86]

LyXText::dispatch: cmd:  action: 86 arg: 'a' x: 0 y: 0

Hopefully someone can read that (I can't, other than I get that it's 
reporting my having typed 'a' near the top).


Incidentally, if the first thing you do after ctrl-shift-left is to 
click someplace in the document, or hit the left arrow key, the keyboard 
remains responsive.  (Hitting up, down or right arrow does not avoid the 
problem but also does not cause the keyboard to lock out -- they have no 
effect at all.)  Also, when the keyboard lockout occurs, LyX is 
hammering the CPU (close to 100% load) for a few seconds.  Then it goes 
back to a light load, and the mouse works.


One other odd thing -- the keyboard works for issuing menu commands 
(alt-F x to exit, for instance).


/Paul

Re: bug(?): strange behavior after ctrl-shift-left

[Steve Harris]

Jose' Matos wrote:

On Tuesday 11 July 2006 20:50, Sven Schreiber wrote:

For me the keyboard is not responding in lyx anymore after that. Can
anybody confirm this? Is it known?


  I do not remember such bug report. :-(
  I would like to hear from other windows users. If the bug is not there it 
should be filled in bugzilla to be fixed in 1.4.2.



Ctrl-shift-left may be stupid to use, but I was just following a hunch...


  Not stupid at all, it selects text from your current position to left. I 
guess that this was your hunch.



this is 1.4.1 on windows with official installer


  It works on linux, I have been using it all day. :-)


thanks,
sven




I tested this on lyx1.3.7ver3 for Windows and the bug is not there.

This is a test. 
ctrl-shift-left_key

will return to the space just afer "test." in the previous
paragraph. If you use ctrl-shift=left_key again, then
it will highlight in blue, "test." (from "This is a test.")

Also the spell-checking error of starting to check only the
second misspelled word is not present in lyx1.3.7ver3 either.

--

Stephen
"Once you eliminate the impossible, whatever remains, no matter
how improbable, must be the truth." SH: Sherlock Holmes (Doyle)