|
Post by drbob54 on Jun 16, 2015 9:27:49 GMT -5
George
In spflite the cursor is returned to the command line after paste with A or B in the the "line command area" or the "sequence number area". In ISPF the cursor is returned to the "line command area" or the "sequence number area" of the first row inserted.
Over the years I have gotten used to the way ISPF works.
|
|
|
Post by George on Jun 16, 2015 10:44:25 GMT -5
drbob54: Robert: Yes, the 'where does the cursor go' problem is a tough one to solve. Especially when an interaction can contain several line commands along with possibly multiple stacked primary commands. Each of those functions has their own idea about where the cursor should be placed, often conflicting with each other.
SPFLite uses a priority system which assigns a 'pecking order' to each of the various cursor setting calls. It then uses the highest priority setting, and if duplicate priority calls, the 1st one issued.
Given that, the PASTE command problem here does seem to be more than likely a simple bug as it's the only function invoked. I will give it a look, but since I have only just pushed out a new version, it might be a while for it to see the light of day. Or I could always make a temp version available.
George
[Update]
Yes, just simple code errors. PASTE had problems with some of it's other 'flavors' as well, so I pushed them all back into order. If you'd like a temp fix version, let me know.
George
|
|
|
Post by drbob54 on Jun 16, 2015 23:56:58 GMT -5
George Leave it as is. The current paste behaviour is consistent and probably not worth the effort to change given that a much better and more flexible solution is provided via keymap and keyboard primitives. Thanks George/Robert for pointing me in this direction ... the list of keyboard primitives is impressive.
The last question on PASTE.
There does not appear to be a way to paste text into the command line. I am working in a Linux environment at the moment and some of the path names are longish and case is important. I would prefer to 'copy' the path names into the command line for FIND CHANGE operations Am I missing something
|
|
|
Post by drbob54 on Jun 17, 2015 1:25:11 GMT -5
Thanks again Robert
[PASTE] rather than (paste)
(paste) works just fine
|
|