Date: Mon, 13 May 2013 21:44:43 -0500
From: Daniel J Sebald <address@hidden>
To: "John W. Eaton" <address@hidden>
Cc: octave maintainers mailing list <address@hidden>
Subject: Re: Detaching from terminal and keyboard input for GUI
Message-ID: <address@hidden>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
On 05/13/2013 09:07 PM, John W. Eaton wrote:
> On 05/13/2013 09:33 PM, Ben Abbott wrote:
>
>>> I'm able to copy and paste using SHIFT-CMD-C& shift+cmd+v (Normal OSX
>>> keys are CMD-C& CMD-V). The "find files" also works for me, SHIFT-CMD-F.
>
> I think those keybindings are coming from the shortcuts assigned to
> entries in the Edit menu that is part of the main window menu bar.
>
>>> When I attempt "ls" in a directly with enough files to trigger the
>>> pager and its "-- less -- (f)orward, (b)ack, (q)uit", the command
>>> line becomes unresponsive.
>
> So the ioctl doesn't really detach the terminal. I'd guess that less
> is still trying to read from /dev/tty, or if not, that whatever it is
> trying to read from is not properly attached to the terminal widget.
>
>>> CTRL-C doesn't work for me either. I'm also unable to use the arrow
>>> keys to browse through the command history.
>>>
>>> I assume that means readline is'nt functioning.
>
> Do any other readline keybindings work? CTRL-A?
>
>>> The CMD-O works (which is normal mapping on OS X, i.e. not
>>> "SHIFT-CMD-O")
>
> That is probably coming from the keyboard shortcut that is attached to
> the open menu item in the File menu that is part of the main window
> menu bar.
>> src/m-editor/file-editor-tab.cc:30:34: fatal error:
>> Qsci/qscilexeroctave.h: No such file or directory
>
> I can look at disabling this feature if Qsci/qscilexeroctave is not
> present. But I'm not really interested in duplicating this
> functionality in Octave in the even that it is not present in
> QScintilla.
>
> jwe
Re-implementing it is a bad idea. There is then two different versions,
one from the QSci repository and one possibly from Octave repository.
Too confusing for users and when users report problems. It would be
better for someone to work with the QSci developers to keep that file up
to date (or ask them to drop it and then maintain one as part of Octave
project).
The code isn't very extensive right now:
http://code.google.com/p/openshapefactory/source/browse/Libs/QScintilla-gpl-2.5.1/Qt4/qscilexeroctave.cpp?r=eb84e57b18a318b3aa65588c66c92fca5cf71641
Is it expected to change at a rapid pace for the short term while GUID+O
is in development.
John D, I see you've done some work on the lexer for Scintilla. What
makes sense here? It appears that QScintilla octave lexer inherits
matlab lexer which inherits the generic lexer. How does the
matlab/octave lexer from scintilla fit into this picture?
Dan
The qscintilla lexer and lexlib is directly from scintilla 3.2.3 (scintilla is now 3.3.1).
I had contacted the qscintilla guys about whether there where any plans to integrate in the later versions of scintilla lexers (and in fact I event sent them a patch with the latest lexers that would still work with thier code) and got no reponse back on either whether they were planning to integrate, use the patch or anything else.
If thier lack of reponse so far is any indication ...