F1 works differently in ODE and Ride
Pressing F1 in this
=≠
with the cursor positioned between the = and the ≠ has different results in the ODE and Ride:
- The ODE shows the help page for
= - Ride shows the help page for
≠
Now change your prefs to use a block cursor and you will understand why.
I think you may still argue it should show the help for the character to the left, but it isn't as obvious.
I am not arguing with any of this. As long as the two behave the same;)
On 12 June 2018 at 15:44, Gilgamesh Athoraya [email protected] wrote:
Now change your prefs to use a block cursor and you will understand why.
I think you may still argue it should show the help for the character to the left, but it isn't as obvious.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Dyalog/ride/issues/449#issuecomment-396615650, or mute the thread https://github.com/notifications/unsubscribe-auth/APt0nb7FSLqSBqHSkoAWIW6H3xTDnhpDks5t79PTgaJpZM4UkPi6 .
and your preference?
No pref at all.
On 12 June 2018 at 15:49, Gilgamesh Athoraya [email protected] wrote:
and your preference?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Dyalog/ride/issues/449#issuecomment-396617560, or mute the thread https://github.com/notifications/unsubscribe-auth/APt0nVDqu5Fmx8En0WiXplZ4E5-1uAb-ks5t79UJgaJpZM4UkPi6 .
The ODE has a "destructive" edit mode (instead of "insert") whereby placing the cursor between two characters and typing a third overwrites the second with the third rather than insert it between the first and second. When in this mode the cursor changes to an underscore yet F1 help gives help for the character to the left of the character the cursor is flashing underneath. I think, therefore, that if it's a straight choice between showing the character to the left or the right, we have good precedence for left even with a block cursor.
However, there is good cause, I think, to ask the following questions:
- Although established behaviour, should we consider "fixing" the ODE? It seems very odd that if I have
⍳⍴
with a flashing underscore cursor underneath the ⍴, F1 help gives help for ⍳.
- Should RIDE have an option to select a block cursor? It would be useful to have that available for a destructive edit mode.
“should we consider "fixing" the ODE”
No.
I would argue that almost no-one has insert mode turned off for more than a few moments if ever; either because they’re attempting to create an overstrike, or because they’ve “hit” the insert toggle by mistake.
A
From: Richard Smith [email protected] Sent: 13 June 2018 13:13 To: Dyalog/ride [email protected] Cc: Subscribed [email protected] Subject: Re: [Dyalog/ride] F1 works differently in ODE and Ride (#449)
The ODE has a "destructive" edit mode (instead of "insert") whereby placing the cursor between two characters and typing a third overwrites the second with the third rather than insert it between the first and second. When in this mode the cursor changes to an underscore yet F1 help gives help for the character to the left of the character the cursor is flashing underneath. I think, therefore, that if it's a straight choice between showing the character to the left or the right, we have good precedence for left even with a block cursor.
However, there is good cause, I think, to ask the following questions:
- Although established behaviour, should we consider "fixing" the ODE? It seems very odd that if I have
⍳⍴
with a flashing underscore cursor underneath the ⍴, F1 help gives help for ⍳.
- Should RIDE have an option to select a block cursor? It would be useful to have that available for a destructive edit mode.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/Dyalog/ride/issues/449#issuecomment-396915889 , or mute the thread https://github.com/notifications/unsubscribe-auth/AKkCEg3qFI_sqbC_s1uwL5ZPI_50yXi9ks5t8QHlgaJpZM4UkPi6 .
I fully agree with Andy: overwrite does not matter these days. I don't do overstrikes; that makes 99% of my destructive modes accidents.
When we get to this, let's have a look at what other editors do.
Can't repro